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


[Xen-devel] Re: 0/4 Xen Scheduling Groups

To: <ncmike@xxxxxxxxxx>
Subject: [Xen-devel] Re: 0/4 Xen Scheduling Groups
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 12 May 2007 08:43:27 +0100
Cc: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 12 May 2007 00:40:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070512001614.GB13507@xxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceUaToQeHjSFQBcEdySywAWy6hiGQ==
Thread-topic: 0/4 Xen Scheduling Groups
User-agent: Microsoft-Entourage/
On 12/5/07 01:16, "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 thought we decoded the instruction to be emulated in Xen (in the context
of the HVM domain, so current==hvm-domain) then packaged it up in a
shared-memory page and notified qemu-dm in dom0 via an event channel. To my
knowledge there's no special treatment of this event channel or of dom0: the
notification is treated just like any wake-up of any arbitrary domain.

 -- Keir

Xen-devel mailing list