WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] mem_sharing: fix race condition of nominate and

To: tinnycloud <tinnycloud@xxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] mem_sharing: fix race condition of nominate and unshare
From: Jui-Hao Chiang <juihaochiang@xxxxxxxxx>
Date: Fri, 7 Jan 2011 14:45:01 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Delivery-date: Thu, 06 Jan 2011 22:45:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Uc2hGvkx+A3vQt9dGZkDOckmySfKknEm4muEOhfBuDI=; b=V7wWdoVL0D5v08CIpIhC3qldZs6IiCMP421WSyI5MMGqu+N2EHc/LP51Kg/N4d6GBL UIfVGJgTisTcyGkE7oVwBUWPnXE1VCHg6i4zgq+0pvhcuUrMaR7LhW3LB+Fkyyw3D4bt AHop1PFjDFiHLCYm5X+J2wgCgGbJKqqYwxarE=
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=Vm9CAyJwpvvPm9mkyoZQcPD1OU2xR5Iqt/qkzV7nTJvhm7XHG4JFq1jgo/54S6ToZq +C9yz1RgJw80FEEVUfv1S2rL7j/+eUaOg5TTVPFYbUv4kaPK/DRqYrTU7cP9NTCtgJCf Ii39EQB/CYL3/npTfaRmF9146UjUBh1L5Rlok=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BLU157-ds19B9B6B10F800B74320CFEDA0B0@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinMp1v1zex2BfcUuszotPuxJFWZQNUp40gu_gxL@xxxxxxxxxxxxxx> <BLU157-ds19B9B6B10F800B74320CFEDA0B0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, tinnycloud:

(XEN) mm.c:859:d0 Error getting mfn 2df6a8 (pfn fffffffffffffffe) from L1 entry 80000002df6a8627 for l1e_owner=0, pg_owner=2

(XEN) mm.c:859:d0 Error getting mfn 2df6a9 (pfn fffffffffffffffe) from L1 entry 80000002df6a9627 for l1e_owner=0, pg_owner=2


Could you use dump_execution_state() in mm.c:859?
And in the unshare() function, could you move the printk outside the (!p2m_is_shared(p2mt)) checking?
If you put inside it, we never know if the unshare() is being done or not (please also print out the mfn, p2mt, gfn, domain_id).

Just out of curiosity, are you running stubdom? your HVM guest id =2 is pretty weird.

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