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/
Home Products Support Community News


Re: [Xen-devel] Why have an idle domain? (Was: IDLE domain is scheduled

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Why have an idle domain? (Was: IDLE domain is scheduled more than dom0)
From: Rob Gardner <rob.gardner@xxxxxx>
Date: Tue, 12 Jul 2005 13:40:56 -0600
Delivery-date: Tue, 12 Jul 2005 19:39:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD54FA6D4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD54FA6D4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Magenheimer, Dan (HP Labs Fort Collins) wrote:

What I propose is that domain0 become the idle domain.  Special
casing code would be added to the schedulers so that domain0
is always runnable and thus will absorb any "idle" cycles.

This is admittedly not a grave concern, but doing what you propose will screw up performance accounting, since we won't know for sure how much cpu time dom0 is really using. And there is reason to believe that dom0 cpu usage should be closely monitored.

Rob Gardner

Xen-devel mailing list