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] [PATCH] Fix legacy irq allocation issue

To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix legacy irq allocation issue
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 19 Jun 2009 09:26:45 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 19 Jun 2009 01:27:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E2263E4A5B2284449EEBD0AAB751098402CBA344F2@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnwsWEtNbzCmHBmQZS8O4wHAi1N3gAASjCAAAFJFRQ=
Thread-topic: [Xen-devel] [PATCH] Fix legacy irq allocation issue
User-agent: Microsoft-Entourage/12.19.0.090515
On 19/06/2009 09:13, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

>> If this is really needed, then why not simply exchange the following
>> uses of IO_APIC_VECTOR() to irq_to_vector(), which already properly
>> considers legacy vectors?
> 
> Aha, yes. I should use that.

A patch to apply on top of the old patch then, please.

 K.

> This is needed if dom0 try to assign a vector to legacy irq. I find this when
> help debugging one system. I don't have the broken system, so I have no idea
> why dom0 will try to assign vector to legacy irq. But from API point of view,
> I think this check is needed.



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