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: 0/4 Xen Scheduling Groups

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: 0/4 Xen Scheduling Groups
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Fri, 11 May 2007 20:16:14 -0400
Cc: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 11 May 2007 17:14:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C26A9A89.7413%Keir.Fraser@xxxxxxxxxxxx>
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>
Organization: IBM Linux Technology Center
References: <20070511194131.GA13507@xxxxxxxxxxxxxxxxxxxxxx> <C26A9A89.7413%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: ncmike@xxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On 11/05/07 22:11 +0100, Keir Fraser wrote:
On 11/5/07 20:41, "Mike D. Day" <ncmike@xxxxxxxxxx> wrote:

After these first patches get accepted I plan on implementing a
feature where one domain can tell the scheduler it would like to run
*after* a different domain in the same group.

Xen already does this for dom0

Does it?

When an hvm domain does an emulated io, xen creates an event which is
delivered to the idle domain (xen), which in turn triggers a soft
interrupt on domain 0. In effect dom0 is immediately scheduled. Dom 0
then emulates the io while the hvm domain is sleeping. I assume the
same holds for other i/o events to domain zero, although I haven't
looked at that code. This is the kind of scheduling effect that would
be nice to have for a stub domain in relation to an hvm domian. But
the stub domain doesn't have any special status that schedules it to run
immediately.

--
Mike D. Day
IBM LTC
Cell: 919 412-3900
Sametime: ncmike@xxxxxxxxxx AIM: ncmikeday  Yahoo: ultra.runner
PGP key: http://www.ncultra.org/ncmike/pubkey.asc

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