[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-24 Thread Isaku Yamahata
On Wed, Apr 23, 2008 at 04:03:58PM +0200, Jes Sorensen wrote: Isaku Yamahata wrote: I'd rather have PARAVIRT_NR_IRQ set from Kconfig if possible given that all of these are constants anyway. If we cannot do that, then it would be better to do the #if FOO_NR_IRQ PARAVIRT_NR_IRQ in the various

[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-23 Thread Jes Sorensen
Isaku Yamahata wrote: I'd rather have PARAVIRT_NR_IRQ set from Kconfig if possible given that all of these are constants anyway. If we cannot do that, then it would be better to do the #if FOO_NR_IRQ PARAVIRT_NR_IRQ in the various header files for Xen/KVM/lguest so we don't get the clutter in

[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-22 Thread Jes Sorensen
Make NR_IRQ overridable by each pv instances. Pv instance may need each own number of irqs so that NR_IRQS should be the maximum number of nr_irqs each pv instances need. This really looks dodgy. +#ifdef CONFIG_PARAVIRT + +/* Determine the maximal NR_IRQ which each pv instances require. + *

[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-22 Thread Isaku Yamahata
On Tue, Apr 22, 2008 at 05:08:22AM -0400, Jes Sorensen wrote: Make NR_IRQ overridable by each pv instances. Pv instance may need each own number of irqs so that NR_IRQS should be the maximum number of nr_irqs each pv instances need. This really looks dodgy. +#ifdef CONFIG_PARAVIRT

[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-22 Thread Jes Sorensen
Isaku Yamahata wrote: I'm willing to introduce something like PARAVIRT_NR_IRQS, but I don't see how PARAVIRT_NR_IRQS solves the issues. What I want here is to define by cpp #define PARAVIRT_NR_IRQS\ max(

[Xen-ia64-devel] Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS

2008-04-22 Thread Isaku Yamahata
On Tue, Apr 22, 2008 at 02:05:59PM +0200, Jes Sorensen wrote: Isaku Yamahata wrote: I'm willing to introduce something like PARAVIRT_NR_IRQS, but I don't see how PARAVIRT_NR_IRQS solves the issues. What I want here is to define by cpp #define PARAVIRT_NR_IRQS