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

RE: [Xen-devel] interrupt delivery to VCPU

To: "Shan, Haitao" <haitao.shan@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] interrupt delivery to VCPU
From: "Agarwal, Lomesh" <lomesh.agarwal@xxxxxxxxx>
Date: Mon, 22 Oct 2007 15:33:32 -0700
Delivery-date: Mon, 22 Oct 2007 15:39:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <823A93EED437D048963A3697DB0E35DED10031@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/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: <A3258B497F1C1441AD36A2E8B45FD628D745C5@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><C33ED6D2.172AD%Keir.Fraser@xxxxxxxxxxxx> <A3258B497F1C1441AD36A2E8B45FD628D74679@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <823A93EED437D048963A3697DB0E35DED10031@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgSi+tzKdwUE35/EdymXwAX8io7RQAA9fSAAAAxY7QAAA8zsAAALeXnAACPmCAAOo5TkABfVhPg
Thread-topic: [Xen-devel] interrupt delivery to VCPU
Does it make sense to change interrupt delivery to VCPU which is going to be 
runnable next so that interrupt latency can be minimized for HVM guest?

-----Original Message-----
From: Shan, Haitao 
Sent: Saturday, October 20, 2007 6:05 PM
To: Agarwal, Lomesh; Keir Fraser; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] interrupt delivery to VCPU

Maybe windows uses IPI for forwarding interrupt to another processor?
>From my observation, SMP Windows XP handles RTC timer interrupt this way.

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Agarwal, Lomesh
Sent: 2007年10月20日 5:51
To: Keir Fraser; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] interrupt delivery to VCPU

Does anybody know how windows rebalances irqs among processors?

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Friday, October 19, 2007 1:49 PM
To: Agarwal, Lomesh; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] interrupt delivery to VCPU

I don't know about the VT-d support. I doubt that's been optimised so
much.
I only know about physical IRQ delivery to PV guests. For Linux, a
daemon
(irqbalanced) usually periodically rebalances irqs by writing affinity
info
to /proc/irq/#/affinity.

 -- Keir


On 19/10/07 21:45, "Agarwal, Lomesh" <lomesh.agarwal@xxxxxxxxx> wrote:

> What happens for windows HVM guest?
> Also for PV Linux guest do you know how does Linux setup irq affinity?
> 
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> Sent: Friday, October 19, 2007 1:42 PM
> To: Agarwal, Lomesh; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] interrupt delivery to VCPU
> 
> The guest can choose which VCPU gets any particular interrupt. This is
> tied
> into Linux's normal irq affinity logic, for example.
> 
>  -- Keir
> 
> On 19/10/07 21:39, "Agarwal, Lomesh" <lomesh.agarwal@xxxxxxxxx> wrote:
> 
>> How does Xen deliver an interrupt to VCPU? If there are 2 VCPUs for a
>> guest and there is no interrupt affinity set which VCPU will get the
>> interrupt? is it round robin?
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel



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

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

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

<Prev in Thread] Current Thread [Next in Thread>