From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Paul Clarke <pc@us.ibm.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc: re-enable dynticks
Date: Mon, 23 Feb 2015 09:30:12 +1100 [thread overview]
Message-ID: <1424644212.4980.14.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAFTL4hw_caOPUPwkgDst=gwtT1wh_DUmL-djF43DJC5at=7+Jg@mail.gmail.com>
On Sun, 2015-02-22 at 23:13 +0100, Frederic Weisbecker wrote:
> Yes that should work. After all "self-IPI" is an oxymoron. One would
> expect an IPI to be triggered by an irq controller but if such
> operation isn't supported with the current CPU being both source and
> destination, anything triggering the desired callback in an interrupt
> context in a reasonable amount of time ahead does the job here.
We could do self-IPI on platforms that have an SMP-capable interrupt
controller too but it would probably have higher overhead and would
require verifying that the code for each of our different interrupt
controllers is safe to be called from NMIs (hint: ioremap space isn't
safe to access from NMIs for us on some CPU families...).
We might be able to do better than using the decrementer on some CPUs by
using local doorbells, but for now this will do.
> I thought well that's what powerpc was doing for irq work but I wasn't
> sure I understood the code correctly. I should have pinged people
> about that, sorry.
No worries,
Cheers,
Ben.
next prev parent reply other threads:[~2015-02-22 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 19:38 [PATCH] powerpc: re-enable dynticks Paul Clarke
2015-02-13 20:42 ` Paul E. McKenney
2015-02-16 0:08 ` Michael Ellerman
2015-02-16 4:06 ` Benjamin Herrenschmidt
2015-02-22 22:13 ` Frederic Weisbecker
2015-02-22 22:30 ` Benjamin Herrenschmidt [this message]
2015-02-20 17:08 ` [PATCH v2] " Paul Clarke
2015-02-20 17:13 ` Paul Clarke
2015-02-21 5:18 ` Paul E. McKenney
2015-02-27 13:27 ` Paul Clarke
-- strict thread matches above, loose matches on Subject: below --
2015-04-13 4:37 [PATCH] powerpc: Re-enable dynticks Michael Ellerman
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=1424644212.4980.14.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pc@us.ibm.com \
/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).