From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: NR_PIRQS vs. NR_IRQS
Date: Fri, 14 Nov 2008 11:27:10 -0800
Message-ID: <491DD10E.6060007@goop.org>
References: <C542E0A5.1F377%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C542E0A5.1F377%keir.fraser@eu.citrix.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: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Keir Fraser wrote:
> Is fixing this actually any harder than just bumping NR_IRQS/NR_PIRQS in Xen
> and NR_PIRQS in Linux? Have IRQS and VECTORS got somehow accidentally tied
> together in Xen?
>   

The pvops dom0 kernel allocates all irqs dynamically without having 
reserved ranges for particular classes of irq, so I think it all comes 
down to whether Xen can handle it.

    J