From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] linux: prevent invalid or unsupportable
	PIRQsfrom being used
Date: Wed, 05 Nov 2008 15:26:32 +0000
Message-ID: <C5376BA8.28C48%keir.fraser@eu.citrix.com>
References: <4911C7E5.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4911C7E5.76E4.0078.0@novell.com>
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: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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).

 -- Keir