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:57:45 +0100 [thread overview]
Message-ID: <20140509145745.GI7950@arm.com> (raw)
In-Reply-To: <20140509145002.GW2844@laptop.programming.kicks-ass.net>
On Fri, May 09, 2014 at 03:50:02PM +0100, Peter Zijlstra wrote:
> On Fri, May 09, 2014 at 03:40:34PM +0100, Catalin Marinas wrote:
>
> > 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.
>
> Does ARM64 support idle=poll? If so, you could keep it for that,
> otherwise it does indeed appear to be pointless.
We don't support idle=poll either.
> As to 32bit ARM, are there SMP chips which do not have WFI?
No. WFI is even used for the secondary booting protocol (we need to send
an IPI to get them going).
--
Catalin
next prev parent reply other threads:[~2014-05-09 14:57 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
2014-05-09 14:50 ` Peter Zijlstra
2014-05-09 14:57 ` Catalin Marinas [this message]
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=20140509145745.GI7950@arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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