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] Unplugging a dom0 vcpu and domain destruction

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Unplugging a dom0 vcpu and domain destruction
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Tue, 17 Feb 2009 17:30:03 +0000
Delivery-date: Tue, 17 Feb 2009 09:30:26 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=UGZ/qxh/vBthomBtl4yTZKz22kvT3OCABvBiyZZUWLA=; b=g38AKt833x6xrkHcgYL2km7yLNrExPcp+JME3zPHo7X2sbY2NP/FrVJuXi3BZ3TwVk 3/ao0RTfD0W7Oh7jv7f6SPPSPOYrfyAV3wuWKd4QJzKms5TZJ8BWCvDI675X8ot6WLlS Xxi6Js1FJtr5xwgSHHfQhePCKOFJ6s890zvf4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=JeB1ItZMy4eL45wevsgBU6LVtC975kgJmjZiMrSWIusDrP6CEsIfqj0xVAOh2hhl4g wYhEIg+4/8CmFIZQ+4XaZNq5qOe86/z3mF89yQoTi+tPKf8wnRIYwM8BN9d9V/Z1IHQD 5OnwWvrQs3awG7ov/C2fFxqfhSFr9gQN1b4p0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
In the course of developing the new scheduler, I noticed something
rather strange.

If I bring dom0's second cpu offline (echo "0" >
/sys/devices/system/cpu/cpu1/online), and then create and destroy a
number of domains, xen/common/domain.c:domain_destroy() is not called
(nor vcpu_destroy, and the scheduler domain destruction
functionality).  If I bring the cpu back online (echo 1 > ...), the
domains are destroyed almost immediately.

domain_destroy() is only called from put_domain(), so presumably
there's somehow reference counts held somewhere which aren't released
when the second cpu is offline.

I've duplicated this using the standard credit scheduler on
xen-unstable tip.  I'm using a Debian dom0 filesystem, and a
linux-2.6.18-xen0 build from a month ago.

My box has 2 cores, so dom0 has only 2 cpus; disabling the second
causes it to switch to UP primitives.

I'm looking into it, but I thought it might ring some bells with someone...

 -George

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