Traditionally there is an actual interrupt wire that runs from the device to the interrupt controller, when it is high (or low, or on an edge) an interrupt is generated and the CPU starts executing the interrupt handler.
Up vote 1 down vote favorite share g+ share fb share tw.
If IRQ is shared by multiple devices, how the kernel identifies the which device caused the interrupt. /Ganesh linux linux-kernel interrupt interrupt-handling link|improve this question edited Dec 10 '10 at 11:06 asked Dec 10 '10 at 7:52Ganesh Kundapur1506 78% accept rate.
I'm interested in your question, but I'll need to warn you: you're being a little vague on "how the hardware/driver raises an interrupt. " Simply put, the HW executes the code at a given interrupt vector. That's how it's done.
I'm guessing you want something more specific. – San Jacinto Dec 10 '10 at 13:16 I mean whenever peripheral hardware needs CPU attention, it raises an interrupt, isn't it? CPU executes the interrupt handler for that interrupt.
Now my question how the hardware raises an interrupt(By executing some instruction or ...) – Ganesh Kundapur Dec 10 '10 at 19:28.
Traditionally there is an actual interrupt wire that runs from the device to the interrupt controller, when it is high (or low, or on an edge) an interrupt is generated and the CPU starts executing the interrupt handler. On modern systems interrupts tend to be messages on a bus which are sent to the interrupt controller (or there may be several). In terms of more detail you'll need to be more specific, the details vary depending on what sort of hardware you're talking about.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.