Clearing the interrupt

4 messages, 2 authors, 2007-03-07 · open the first message on its own page

Clearing the interrupt

From: Mohan Kumar M <hidden>
Date: 2007-03-06 17:41:51

Hi,

I would like to get some suggestions to implement the interrupt clearing
methods in kdump kernel.

After a panic situation, first kernel goes through each irq_desc
structure and if any interrupt is in progress, it calls eoi handler for
that interrupt. eoi handler is called from the crashing cpu context.

	for_each_irq(irq) {
		struct irq_desc *desc = irq_desc + irq;

		if (desc->status & IRQ_INPROGRESS)
			desc->chip->eoi(irq);

		if (!(desc->status & IRQ_DISABLED))
			desc->chip->disable(irq);
	}


But initially some another cpu might have acknowledged the interrupt and
started processing the interrupt. But eoi handler may not be called by
the cpu which acknowledged the interrupt.

Is there any problem with the above approach? Is there any restriction
such that a cpu which acknowledged the interrupt only should send the eoi
signal?

Regards,
Mohan.

Re: Clearing the interrupt

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2007-03-06 21:04:57

Is there any problem with the above approach? Is there any restriction
such that a cpu which acknowledged the interrupt only should send the eoi
signal?
While I don't think there -should- be any restriction, I also seem to
remember that the xics "emulation" done by the firmware on things like
JS20 requires the eoi to be done from the CPU where the interrupt
originated.

Ben.

Re: Clearing the interrupt

From: Mohan Kumar M <hidden>
Date: 2007-03-07 05:08:23

On Tue, Mar 06, 2007 at 10:04:47PM +0100, Benjamin Herrenschmidt wrote:
quoted
Is there any problem with the above approach? Is there any restriction
such that a cpu which acknowledged the interrupt only should send the eoi
signal?
While I don't think there -should- be any restriction, I also seem to
remember that the xics "emulation" done by the firmware on things like
JS20 requires the eoi to be done from the CPU where the interrupt
originated.
Thanks Ben.

If thats the case, is it okay to call eoi handler from all cpus so that
above case will be satisfied?

Regards,
Mohan.

Re: Clearing the interrupt

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2007-03-07 06:52:27

On Wed, 2007-03-07 at 10:38 +0530, Mohan Kumar M wrote:
On Tue, Mar 06, 2007 at 10:04:47PM +0100, Benjamin Herrenschmidt wrote:
quoted
quoted
Is there any problem with the above approach? Is there any restriction
such that a cpu which acknowledged the interrupt only should send the eoi
signal?
While I don't think there -should- be any restriction, I also seem to
remember that the xics "emulation" done by the firmware on things like
JS20 requires the eoi to be done from the CPU where the interrupt
originated.
Thanks Ben.

If thats the case, is it okay to call eoi handler from all cpus so that
above case will be satisfied?
I suppose so.

Ben.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help