From: Mohan Kumar M <mohan@in.ibm.com>
To: linuxppc-dev@ozlabs.org
Subject: Clearing the interrupt
Date: Tue, 6 Mar 2007 23:09:41 +0530 [thread overview]
Message-ID: <20070306173941.GE7476@in.ibm.com> (raw)
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.
next reply other threads:[~2007-03-06 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 17:39 Mohan Kumar M [this message]
2007-03-06 21:04 ` Clearing the interrupt Benjamin Herrenschmidt
2007-03-07 5:08 ` Mohan Kumar M
2007-03-07 6:52 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070306173941.GE7476@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).