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

Re: [Xen-devel] Unplugging a dom0 vcpu and domain destruction

To: George Dunlap <dunlapg@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Unplugging a dom0 vcpu and domain destruction
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 20 Feb 2009 21:17:50 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 20 Feb 2009 13:18:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <de76405a0902201059v6c98fac2gedf6a4fe87ed0c9@xxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmTjVSIAHWiAhVSQcCFxcsGSW8IRAAE1qoL
Thread-topic: [Xen-devel] Unplugging a dom0 vcpu and domain destruction
User-agent: Microsoft-Entourage/12.15.0.081119
On 20/02/2009 18:59, "George Dunlap" <dunlapg@xxxxxxxxx> wrote:

>> In the pvops kernels we also keep a reference to the vcpu info structure,
>> since we place it the kernel's memory rather than keeping it in the shared
>> info structure.  For a while that had bugs that left zombie domains lying
>> around, but I don't think anyone backported that stuff to 2.6.18.
> 
> Hmm, I'll take a look tomorrow and see if I can work out what those
> two pages that were being kept are.

Jeremy's hunch might be worth following up -- that the offline vcpu holds
onto an mm, which doesn't get dropped until the vcpu comes back (at which
point unmap_vmas() would happen). It seems likely it'll be something silly
like that.

 -- Keir



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