From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: [PATCH] linux: prevent invalid or
	unsupportablePIRQsfrom being used
Date: Wed, 05 Nov 2008 15:30:23 +0000
Message-ID: <4911CA1F.76E4.0078.0@novell.com>
References: <4911C7E5.76E4.0078.0@novell.com>
	<C5376BA8.28C48%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C5376BA8.28C48%keir.fraser@eu.citrix.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>>> Keir Fraser <keir.fraser@eu.citrix.com> 05.11.08 16:26 >>>
>On 5/11/08 15:20, "Jan Beulich" <jbeulich@novell.com> 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