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: One question to IST stack for PV guest

To: "Kleen, Andi" <andi.kleen@xxxxxxxxx>
Subject: [Xen-devel] Re: One question to IST stack for PV guest
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 18 Dec 2009 13:50:53 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 18 Dec 2009 13:51:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2E9E6F5F5978EF44A8590E339E888CF90163515DCF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <C8EDE645B81E5141A8C6B2F73FD9265105AE092F76@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B2BF269.5040608@xxxxxxxx> <2E9E6F5F5978EF44A8590E339E888CF90163515DCF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0
On 12/18/2009 01:43 PM, Kleen, Andi wrote:

What are the requirements here?  Are these events delivered to dom0 to
indicate that something needs attention on the machine, or are they
delivered synchronously to whatever domain is currently running to say
that something bad needs immediate attention?
Both can happen (and also some more like "something happened somewhere, Just 
They are all distingushed by different status bits.

If they're not synchronous, then why not use a normal virq event channel?


Xen-devel mailing list