All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: Steven Smith <Steven.Smith@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Gianluca Guida <Gianluca.Guida@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Balloons, crash-dumps, populate-on-demand, and shared zero pages
Date: Thu, 20 Aug 2009 11:56:05 +0100	[thread overview]
Message-ID: <4A8D2BC5.5060408@citrix.com> (raw)
In-Reply-To: <20090820103921.GA30044@weybridge.uk.xensource.com>

Steven Smith wrote:
> That would make things marginally easier on the drivers, but it's at
> the expense of potentially more subtle errors when something goes
> wrong.  At the moment, if the balloon driver tries to deflate the
> balloon too far, the populate hypercall fails and it's very obvious
> what's gone wrong, whereas with an implicit re-populate it'll look
> like everything's working fine for some time afterwards, until the
> guest touches too many pages and PoD kills it.
> 

If the balloon driver deflated too far, that would be a bug in the 
balloon driver, and if Windows doesn't scrub the memory when it's freed 
we could do that ourselves so at least PoD would kill the guest at the 
right juncture.

   Paul

-- 
===============================
Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

===============================

  reply	other threads:[~2009-08-20 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 10:18 Balloons, crash-dumps, populate-on-demand, and shared zero pages George Dunlap
2009-08-20 10:39 ` Steven Smith
2009-08-20 10:56   ` Paul Durrant [this message]
2009-08-20 12:49     ` George Dunlap

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=4A8D2BC5.5060408@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Gianluca.Guida@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Steven.Smith@eu.citrix.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.