On Tue, 26 Apr 2005, Grant Grundler wrote:
> Agreed - but this is a different problem than "shutting down IRQs".
> My point was arch specific code knows how to mask all IRQs.
> irq_disable() is expected to work regardless of what state the
> driver is in. On kexec "reboot", kernel drivers can unmask IRQs
> as they normally would during initialization. No?
One has to be careful when talking about enabling/disable IRQs, because
there are (at least) two choke points: one on the device and one on the
computer's interrupt controller. Masking IRQs takes place on the
controller, but I was talking about stopping interrupt requests at their
source on the device. It's the only way to avoid problems when IRQ lines
are shared.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
