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

Re: [Xen-devel] Could the page sharing inside domain? (memory_sharing on xen)


  • To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
  • From: Jui-Hao Chiang <juihaochiang@xxxxxxxxx>
  • Date: Thu, 6 Jan 2011 22:16:15 +0800
  • Cc: tinnycloud <tinnycloud@xxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 06 Jan 2011 06:16:52 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=u77E7n7SGuX9dR2ho5KOFVa13vjpx1rnF/7ZIq9f5m0LKwaCtpyy/ZCsC5NJoqM4CQ GY7/JBBeYhG5mEvEYy/JLyJnHJVPexGeqNyUApXQ1H1VgLsRUAAuSeGrJZEk51gLGOxP 6WNaVgUvYUrXiWTij0J0yRl5NiS3TNAsFeYHk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

The error messages you see above are from dom0 trying to map dom4's
memory and finding a shared page (i.e. owned by dom_cow).  Either
there's a missing unshare operation on the path that called
get_page_from_l1e(), or a race where a page got re-shared before the
mapping could be completed, or possibly the unshare operation doesn't
work properly when a domain has two copies of a shared page.

Tim.



That's exactly what we have found during yesterday.
It is because the code doesn't update/check p2m type with the shr_lock, which causes either incorrect share operation or race-condition in unshare operation.
We will submit our current fix as a patch soon.

Bests,
Jui-Hao
_______________________________________________
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®.