From: julien.thierry@arm.com (Julien Thierry)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] WFE for long delays
Date: Fri, 13 Oct 2017 14:32:54 +0100 [thread overview]
Message-ID: <1507901576-34641-1-git-send-email-julien.thierry@arm.com> (raw)
It was pointed out that there are some windows where the event stream might not
be configured, meaning we cannot safely use WFE (e.g. when using PSCI
CPU_SUSPEND for idle, PSCI might reset CPU state).
The first patch provide a function to check whether the task is in state where
it can expect events from the event stream.
Second patch actually makes use of WFE in delays.
Changes since v1:
* Keep track of event stream state
* Do not use WFE when event stream might be misconfigured
Changes since v2:
* Use cpumask to track event stream state instead of percpu variable
* Tidy a bit code in arm64/lib/delay
* Do not factor asm-generic/delay code
Changes since v3:
* Use static initialiser for event stream cpumask
* Remove double negation when checking steam availability
* Use raw_smp_processor_id instead of smp_processor_id
* Fix typo
* Change macro argument to lower case
Cheers,
Julien Thierry (2):
arm_arch_timer: Expose event stream status
arm64: use WFE for long delays
arch/arm/include/asm/arch_timer.h | 1 +
arch/arm64/include/asm/arch_timer.h | 1 +
arch/arm64/lib/delay.c | 23 +++++++++++++++++++----
drivers/clocksource/arm_arch_timer.c | 25 ++++++++++++++++++++++---
include/clocksource/arm_arch_timer.h | 10 +++++++++-
5 files changed, 52 insertions(+), 8 deletions(-)
--
1.9.1
next reply other threads:[~2017-10-13 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 13:32 Julien Thierry [this message]
2017-10-13 13:32 ` [PATCH v4 1/2] arm_arch_timer: Expose event stream status Julien Thierry
2017-10-13 17:51 ` Mark Rutland
2017-10-13 13:32 ` [PATCH v4 2/2] arm64: use WFE for long delays Julien Thierry
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=1507901576-34641-1-git-send-email-julien.thierry@arm.com \
--to=julien.thierry@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