From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH 6/8] sched,idle: Avoid spurious wakeup IPIs
Date: Fri, 9 May 2014 15:40:34 +0100 [thread overview]
Message-ID: <20140509144034.GF7950@arm.com> (raw)
In-Reply-To: <20140509141520.GV2844@laptop.programming.kicks-ass.net>
Hi Peter,
On Fri, May 09, 2014 at 03:15:20PM +0100, Peter Zijlstra wrote:
> On Fri, May 09, 2014 at 02:37:27PM +0100, James Hogan wrote:
> > On 11 April 2014 14:42, Peter Zijlstra <peterz@infradead.org> wrote:
> > > + return !(fetch_or(&ti->flags, _TIF_NEED_RESCHED) & _TIF_POLLING_NRFLAG);
> >
> > This breaks the build on metag, and I suspect arm64 too:
>
> Yep, I just got a patch for arm64.
[...]
> Any SMP arch that has a polling idle function of any kind (including the
> default cpu_idle_poll()).
>
> That said, even if that's true, not having TIF_POLLING_NRFLAG isn't
> fatal, just sub-optimal in that we'll send an unconditional IPI to wake
> the CPU even though its polling TIF_NEED_RESCHED and doesn't need
> anything other than that write to wake up.
>
> Most archs have (x86) hlt or (arm) wfi like idle instructions, and if
> that is your only possible idle function, you'll require the interrupt
> to wake up and there's really no point to having the POLLING bit.
I wonder why we still need TIF_POLLING_NRFLAG for arm64. It was on arm
until commit 16a8016372c42c7628eb (sanitize tsk_is_polling()). On arm64
we use wfi for idle or a firmware call but in both cases the assumption
is that we need an interrupt for waking up.
So I think we should remove this macro for arm64.
--
Catalin
next prev parent reply other threads:[~2014-05-09 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140411134243.160989490@infradead.org>
[not found] ` <20140411135218.478299389@infradead.org>
2014-05-09 13:37 ` [RFC][PATCH 6/8] sched,idle: Avoid spurious wakeup IPIs James Hogan
2014-05-09 14:15 ` Peter Zijlstra
2014-05-09 14:40 ` Catalin Marinas [this message]
2014-05-09 14:50 ` Peter Zijlstra
2014-05-09 14:57 ` Catalin Marinas
2014-05-09 17:02 ` Peter Zijlstra
2014-05-09 17:06 ` Peter Zijlstra
2014-05-09 17:09 ` Catalin Marinas
2014-05-09 17:20 ` Peter Zijlstra
2014-05-09 14:51 ` James Hogan
2014-05-15 9:17 ` James Hogan
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=20140509144034.GF7950@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).