Kdump: Disabling PCI interrupts in capture kernel
Quoting Grant Grundler <[email protected]>:
Quoted 9 lines · Vivek Goyal
Quoted 1 line
So even if interrupts are disabled on PCI-PCI bridge, interrupts
generated
Quoted 1 line
by PCI devices on secondary bus are not blocked and I hope device
should
Quoted 1 line
be working fine.
How did you plan on disabling interrupts?
Did you see the MSI discussion that going on now in linux-pci mailing list?
I am following the discussion now. Thanks.
I am planning to disable only leagacy shared interrupts (irq pin assertion/INTx emulation) because shared interrupts are a problem. MSI are
not shared but I am not sure can they lead to any other problem.
Quoted 9 lines
Quoted 3 lines
But at the same time kdump kernels are not supposed to do a great deal except capture and save the dump.
I'd think you want to stop DMA for all devices. Just to prevent them from messing more with memory that you want to dump - ie get a consistent snapshot. Leaving VGA devices alone should be safe.
May be at some point of time.
Quoted 6 lines
Quoted 1 line
Disabling interrupts at PCI level should increase the reliability of
capturing
Quoted 1 line
the dump on newer machines with hardware compliant with PCI 2.3 or higher.
*lots* of PCI devices predate PCI2.3. Possibly even the majority.
Ya, Some other solution is needed for hardware predating PCI2.3. May be Eric's suggestion of polling the hardware.
Thanks
Vivek