From: Paul Durrant <paul.durrant@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Xiaohui Xin <Xiaohui.xin@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@eu.citrix.com>,
Xin Li <xin.b.li@intel.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: Re: [PATCH] EPT: Only sync pcpus on which a domain's vcpus might be running
Date: Fri, 18 Sep 2009 17:51:38 +0100 [thread overview]
Message-ID: <4AB3BA9A.6080004@citrix.com> (raw)
In-Reply-To: <de76405a0909180755tb58ad92w3f8c0ae57d0b5717@mail.gmail.com>
George Dunlap wrote:
>
> In theory, the memory handed back by the balloon driver shouldn't be
> touched by the OS. I think it would be OK if guess accesses to that
> gfn space didn't fail for the guest giving up the pages; however, we
> can't give the memory to another guest until we know for sure that the
> first guest can't possibly access it anymore. I think we should be
> able to modify the balloon driver to "batch" some number of updates;
> say, 1024 at a time. Paul, any thoughts on this?
>
The decrease_reservation op is called with however many PFNs can fit
into the Windows MDL structure (8184 for a 32-bit VM) so we already do
things in pretty big batches.
Paul
--
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
TEL: x35957 (+44 1223 225957)
===============================
next prev parent reply other threads:[~2009-09-18 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 17:51 [PATCH] EPT: Only sync pcpus on which a domain's vcpus might be running George Dunlap
2009-09-18 7:43 ` Keir Fraser
2009-09-18 9:09 ` George Dunlap
2009-09-18 13:21 ` Keir Fraser
2009-09-18 14:55 ` George Dunlap
2009-09-18 16:51 ` Paul Durrant [this message]
2009-09-18 17:06 ` Dan Magenheimer
2009-09-19 10:34 ` Keir Fraser
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=4AB3BA9A.6080004@citrix.com \
--to=paul.durrant@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=Xiaohui.xin@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.b.li@intel.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.