All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Colp <pjcolp@cs.ubc.ca>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com,
	Andrew Peace <Andrew.Peace@eu.citrix.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Jan Beulich <JBeulich@novell.com>,
	Grzegorz Milos <gm281@cam.ac.uk>
Subject: Re: [PATCH] Paging and memory sharing for HVM  guests
Date: Fri, 18 Dec 2009 10:54:15 -0800	[thread overview]
Message-ID: <4B2BCFD7.7030903@cs.ubc.ca> (raw)
In-Reply-To: <20091218183634.GA26650@phenom.dumpdata.com>

Konrad Rzeszutek Wilk wrote:
>> A new ioctl seems like the reasonable approach. And as you, say if we're  
>> going to have a new ioctl, then let's do it right. When calling  
>> xc_map_foreign_batch(), is there any requirement that the pfns you pass 
>> in are contiguous (ordering incrementally)? If not, then I think 
>> completely over-writing the MFNs is probably the wrong thing to do, as it 
>> requires callers to keep two copies of the array to find out which pages 
>> didn't map. I would be more in favour of returning a bit vector. As far 
> 
> I would suggest you look in xen_exchange_memory in the linux kernel. One
> of its customers is xen_create_contiguous_region which replaces MFNs
> with ones underneath the 4GB.
> 
> There is a requirement in making the PFNs contigous but that is b/c
> the Xen side loops over it assuming incremental order.

If we know that the PFNs have to be contiguous (and we're happy having this 
be a requirement), then completely overwriting the MFNs is probably easier 
than returning a bit vector (and wouldn't require extra support in libxc).


Patrick

  reply	other threads:[~2009-12-18 18:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 23:14 [PATCH] Paging and memory sharing for HVM guests Grzegorz Milos
2009-12-16 23:52 ` Dan Magenheimer
2009-12-17  0:00   ` Patrick Colp
2009-12-17  0:15     ` Dan Magenheimer
2009-12-17  8:47 ` Jan Beulich
2009-12-17 13:08   ` Grzegorz Milos
2009-12-17 15:11     ` Patrick Colp
2009-12-17 11:19 ` Jan Beulich
2009-12-17 15:59   ` Keir Fraser
2009-12-17 18:34     ` Jeremy Fitzhardinge
2009-12-17 16:19 ` Dan Magenheimer
2009-12-18 18:05   ` Dan Magenheimer
2009-12-18 18:51     ` Patrick Colp
2009-12-20 15:04     ` Grzegorz Milos
2009-12-21 16:52       ` Dan Magenheimer
2009-12-17 16:38 ` Konrad Rzeszutek Wilk
2009-12-17 16:59   ` Jan Beulich
2009-12-17 17:05     ` Patrick Colp
2009-12-18  8:08       ` Jan Beulich
2009-12-18 17:29         ` Patrick Colp
2009-12-18 18:36           ` Konrad Rzeszutek Wilk
2009-12-18 18:54             ` Patrick Colp [this message]
2009-12-17 18:27     ` Konrad Rzeszutek Wilk
2009-12-17 17:02   ` Patrick Colp
2009-12-17 17:26     ` Patrick Colp
2009-12-17 19:47 ` Jeremy Fitzhardinge
2009-12-17 20:08   ` Patrick Colp
2009-12-17 20:15     ` Jeremy Fitzhardinge
2009-12-17 20:16       ` Jeremy Fitzhardinge
2009-12-17 20:22         ` Patrick Colp
2009-12-18 16:00 ` Jan Beulich
2009-12-18 17:16   ` Patrick Colp
2009-12-22 10:49 ` Jan Beulich
2009-12-22 11:34   ` Keir Fraser
2009-12-22 12:56     ` Jan Beulich
2009-12-22 13:35       ` Keir Fraser
2010-01-04 14:14 ` Jan Beulich
2010-01-04 15:32   ` Keir Fraser
2010-01-04 16:30     ` Jan Beulich
2010-01-05  7:51       ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2BCFD7.7030903@cs.ubc.ca \
    --to=pjcolp@cs.ubc.ca \
    --cc=Andrew.Peace@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=gm281@cam.ac.uk \
    --cc=keir.fraser@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.