[lkml]   [2007]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: What are the real ioapic rte programming constraints?
Zwane Mwaikambo <> writes:

> On Sun, 11 Feb 2007, Eric W. Biederman wrote:
>> > 2.15.2 PCI Express* Legacy INTx Support and Boot Interrupt
>> >
>> Ouch. And this kind of thing isn't exactly uncommon.
>> However if we have the irqs also disabled in the i8259 we should
>> be safe from actually receiving this interrupt (even if it generates
>> bus traffic), and when we enable the irq since it is level triggered
>> we should still get an interrupt message.
>> It isn't immediately obvious where the i8259 irq enable/disable
>> happens. So i"m having trouble auditing that bit of code.
>> Plus we can get very strange things like the irq number changing
>> and the sharing rules being different when going through the i8259.
>> So irqN may be irqM when going through the i8259.
>> As long as we aren't using anything on the i8259 including the timer
>> in ExtINT mode we can disable every interrupt pin and not worry about
>> interrupts from that source.
> We do the 8259 mask in setup_IO_APIC_irq. does anyone have access to an
> E7520/E7320 system for testing?

I think I do, I need to double check.

The thing is this logic is different in that it uses INTx instead of pins
but otherwise is quite standard for chipsets and their IOAPICs. I'm not
at all certain this behavior is what the original concern was about.
The description is enough different you may have found a completely
different set of behavior we have to worry about.

Since the legacy/non legacy behavior is common invoked by the ioapic
mask bit working with just about any recent chipset should get a taste
of that. But I will still try and dig up an E7520 and see what

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-02-12 05:55    [W:0.145 / U:0.460 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site