[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] mem_sharing: summarized problems when domain is dying


  • To: Jui-Hao Chiang <juihaochiang@xxxxxxxxx>
  • From: George Dunlap <dunlapg@xxxxxxxxx>
  • Date: Fri, 21 Jan 2011 16:32:34 +0000
  • Cc: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
  • Delivery-date: Fri, 21 Jan 2011 08:33:10 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=kTtzqniFcJ7KLOLiWAGboa3UT7dfGTQTpL3hvFDcmGDetRE2t8ehuHUbKpyV3cXz3F KT+BsQpcaaZfoDGDY7BiqPpSWftgqDO9MO9OwWFvMnTbHUYJ8gHdvN+9JMcW9PjupToL VTMgG3it/4cnwzXHmF44lj8RIH0+ulzXW/Y9E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

[sorry, accidentally sent too early]

On Fri, Jan 21, 2011 at 4:29 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
> I'm not sure the exact rationale behind the "cannot fail" flag; but it
> looks like in grant_table.c, both callers of gfn_to_mfn_unshare()
> handle the case where the returned p2m entry is just

...invalid.  I wonder if "unsharing" the page, but marking the entry
invalid during death would help.

I suppose the problem there is that if you're keeping the VM around
but paused for analysis, you'll have holes in your address space.  But
just returning an invalid entry to the callers who try to unshare
pages might work.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.