From: Mohan Kumar M <mohan@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Clearing the interrupt
Date: Wed, 7 Mar 2007 10:38:00 +0530 [thread overview]
Message-ID: <20070307050800.GI7476@in.ibm.com> (raw)
In-Reply-To: <1173215087.9349.17.camel@localhost.localdomain>
On Tue, Mar 06, 2007 at 10:04:47PM +0100, Benjamin Herrenschmidt wrote:
> > 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.
next prev parent reply other threads:[~2007-03-07 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 17:39 Clearing the interrupt Mohan Kumar M
2007-03-06 21:04 ` Benjamin Herrenschmidt
2007-03-07 5:08 ` Mohan Kumar M [this message]
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=20070307050800.GI7476@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=benh@kernel.crashing.org \
--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).