Messages in this thread |  | | | Date | Sat, 4 Jun 2005 19:13:06 +0530 | | From | Dipankar Sarma <> | | Subject | Re: [Fastboot] Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel |
| |
On Sat, Jun 04, 2005 at 04:18:24PM +0300, Denis Vlasenko wrote: > On Friday 03 June 2005 21:36, Eric W. Biederman wrote: > > > > As I recall the drivers were not getting the interrupts but the interrupts > > were happening. To stop being spammed the kernel disables the irq line, > > at the interrupt controller. Then when the driver registered the > > interrupt it would never receive the interrupt. > > Shouldn't kernel keep all interrupt lines initially disabled > (sans platform-specific magic), and enable each like only when > a device driver requests IRQ? This sounds simpler to do...
This doesn't help kdump folks. Interrupt pending from a device from the first boot can flood the system when another driver sharing the irq gets enabled in the second boot (kdump boot). The disabling of interrupts need to be done on a per-device basis for kdump to avoid this problem.
That said, I am not sure what is the issue with the console drivers. What good is the irq for the console driver if it hasn't requested for it ? Why should disabling it affect consoles ? The interrupt will get enabled as soon as the driver requests for it as per Vivek's patch. Am I missing something here ?
Thanks Dipankar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |