From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
Subject: [PATCH 0/6] Enable support for deep-stop states on POWER9
Date: Tue, 16 May 2017 14:19:42 +0530 [thread overview]
Message-ID: <cover.1494585671.git.ego@linux.vnet.ibm.com> (raw)
From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
Hi,
This patch series contains some of the fixes required for enabling
support for deep stop states such as STOP4 and STOP11 via CPU-Hotplug.
These fixes mainly ensure that some of the hypervisor resources which
are lost during the deep stop state are correctly restored on a
wakeup.
There are 6 patches in the series.
Patch 1 correctly initializes the core_idle_state_ptr based on the
threads_per_core. core_idle_state_ptr is used to determine if a thread
is the last thread entering a deep stop state or a first thread waking
up from deep stop state in order to save/restore per-core resources.
Patch 2 decouples restoring timebase from restoring hypervisor
resources, as there are stop states which lose hypervisor state but
not the timebase.
Patch 3 saves the LPCR value before executing deep stop and restores
it back to the saved value on the wakeup from stop.
Patch 4 programs the restoration of some of one-time initialized SPRs
via the stop-api.
Patch 5 provides a workaround for a hardware issue on POWER9 DD1 chips
where the PLS value cannot be relied upon on a wakeup from deep stop.
Patch 6 fixes the cpuidle-powernv initialization code to allow deep
states that don't lose timebase.
These patches are based on the Linux upstream and have been tested
with the corresponding skiboot patches in
https://lists.ozlabs.org/pipermail/skiboot/2017-May/007183.html to get
STOP4 working via CPU-Hotplug.
Akshay Adiga (1):
powernv:idle: Restore SPRs for deep idle states via stop API.
Gautham R. Shenoy (5):
powernv:idle: Correctly initialize core_idle_state_ptr
powernv:idle: Decouple Timebase restore & Per-core SPRs restore
powernv:idle: Restore LPCR on wakeup from deep-stop
powernv:idle: Use Requested Level for restoring state on P9 DD1
cpuidle-powernv: Allow Deep stop states that don't stop time
arch/powerpc/include/asm/paca.h | 2 +
arch/powerpc/kernel/asm-offsets.c | 1 +
arch/powerpc/kernel/idle_book3s.S | 33 +++++++---
arch/powerpc/platforms/powernv/idle.c | 112 +++++++++++++++++++++-------------
drivers/cpuidle/cpuidle-powernv.c | 16 +++--
5 files changed, 110 insertions(+), 54 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-05-16 8:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 8:49 Gautham R. Shenoy [this message]
2017-05-16 8:49 ` [PATCH 1/6] powernv:idle: Correctly initialize core_idle_state_ptr Gautham R. Shenoy
2017-05-30 5:56 ` Nicholas Piggin
2017-05-30 10:23 ` Gautham R Shenoy
2017-05-30 9:11 ` [1/6] " Michael Ellerman
2017-05-16 8:49 ` [PATCH 2/6] powernv:idle: Decouple Timebase restore & Per-core SPRs restore Gautham R. Shenoy
2017-05-30 6:12 ` Nicholas Piggin
2017-05-30 10:28 ` Gautham R Shenoy
2017-05-16 8:49 ` [PATCH 3/6] powernv:idle: Restore LPCR on wakeup from deep-stop Gautham R. Shenoy
2017-05-30 6:17 ` Nicholas Piggin
2017-05-30 10:35 ` Gautham R Shenoy
2017-05-16 8:49 ` [PATCH 4/6] powernv:idle: Restore SPRs for deep idle states via stop API Gautham R. Shenoy
2017-05-16 8:49 ` [PATCH 5/6] powernv:idle: Use Requested Level for restoring state on P9 DD1 Gautham R. Shenoy
2017-05-30 6:27 ` Nicholas Piggin
2017-05-16 8:49 ` [PATCH 6/6] cpuidle-powernv: Allow Deep stop states that don't stop time Gautham R. Shenoy
2017-05-30 7:13 ` Nicholas Piggin
2017-05-30 10:50 ` Gautham R Shenoy
2017-05-30 11:10 ` Nicholas Piggin
2017-05-31 8:39 ` Gautham R Shenoy
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=cover.1494585671.git.ego@linux.vnet.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.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).