On Tue, Aug 19, 2008 at 11:32 AM, Alex Nixon <alex.nixon@xxxxxxxxxx> wrote:Yinghai Lu wrote:On Tue, Aug 19, 2008 at 11:13 AM, Alex Nixon (Intern)Sorry I should have mentioned originally - the bug occurs both with
<Alex.Nixon@xxxxxxxxxx> wrote:
Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:can you try !CONFIG_HAVE_SPARSE_IRQ and CONFIG_HAVE_SPARSE_IRQ ?On Tue, Aug 19, 2008 at 9:55 AM, Alex Nixon <alex.nixon@xxxxxxxxxx>I'm not sure about the general case, but Xen does not (Jeremy correct me
wrote:
If the number of discovered IRQs is suspiciously low, this patch causesif only one ioapic, nr will be 24<<1, you will get 48. Does pv has io
the number reported to default to NR_IRQS, rather than 32. NR_IRQS has
already been defined to be a >sensible value for the current system (in
particular, at least 224 when paravirtualisation is involved).
apic
?
YH
if
I'm wrong).
Unless I'm missing something (which I may well be; I'm new to this area
of
code), it seems more logical anyway to default back to the calculated
system-specific value (NR_IRQS), instead of 32, which seems rather
arbitrary.
YH
CONFIG_HAVE_SPARSE_IRQ enabled, and disabled.
maybe we need special probe_nr_irqs for PV or not call that in
setup_arch for xen -- it will leave nr_irqs == NR_IRQS
YH