[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440808211656o20f9a22dv34e3ac8e8e84b4e1@mail.gmail.com>
Date: Thu, 21 Aug 2008 16:56:36 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Jeremy Fitzhardinge" <jeremy@...p.org>
Cc: "Ingo Molnar" <mingo@...e.hu>,
"Thomas Gleixner" <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, "Alex Nixon" <alex.nixon@...rix.com>
Subject: Re: [PATCH] x86: fix probe_nr_irqs for xen
On Thu, Aug 21, 2008 at 4:52 PM, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> Yinghai Lu wrote:
>> On Thu, Aug 21, 2008 at 4:33 PM, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>>
>>> Yinghai Lu wrote:
>>>
>>>> otherwise Xen is _completely_ unusable with 5 or more VCPUs.
>>>> ( when !CONFIG_HAVE_SPARSE_IRQ)
>>>>
>>>> based on Alex's patch
>>>>
>>>> also add +1 offset after redir_entries
>>>>
>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>
>>>> Cc: Alex Nixon <alex.nixon@...rix.com>
>>>>
>>>>
>>> Looks good to me. We can fix this in a better way later.
>>>
>>
>> later could set CONFIG_HAVE_SPARSE_IRQ to true by default.
>>
>
> Well, perhaps. But we can use vectors rather than IRQs for Xen event
> channel mappings, which will save us from having to allocate lots of
> per-cpu irqs.
like system vectors with smp-ipi etc?
>
> Also, implementing probe_nr_irqs() in a more generic (rather than
> io_apic-specific) way. Using some interface that queries each irq chip
> for how many irqs it supports, or something.
hope we can kill nr_irqs/NR_IRQS
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists