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] linux: prevent invalid or unsupportablePIRQsfrom

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] linux: prevent invalid or unsupportablePIRQsfrom being used
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 05 Nov 2008 15:30:23 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Nov 2008 07:30:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5376BA8.28C48%keir.fraser@xxxxxxxxxxxxx>
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: <4911C7E5.76E4.0078.0@xxxxxxxxxx> <C5376BA8.28C48%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 05.11.08 16:26 >>>
>On 5/11/08 15:20, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>
>> Clearly, growing NR_IRQS will be necessary here, perhaps based on
>> Linux' x86-64 scheme of assigning IRQs and their vectors on a per-CPU
>> basis. Are there any plans in that direction?
>
>Not for 2.6.18. Perhaps for pv_ops, if latest kernels don't have such
>functionality already. Remember we're obsoleting the 2.6.18 tree before Xen
>3.4, assuming Jeremy gets the dom0 stuff worked out by then (and there's no
>reason to think he won't).

Oh, I meant NR_IRQS in Xen, not in Linux. I referred to Linux only because
it already has a solution that likely could be leveraged.

Jan


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