From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: "Gautham R. Shenoy" <ego@linux.vnet.ibm.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>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/5] powernv:idle: Define idle init function for power8
Date: Fri, 7 Jul 2017 18:13:02 +0530 [thread overview]
Message-ID: <20170707124302.GC8913@in.ibm.com> (raw)
In-Reply-To: <20170707010646.0157d251@roar.ozlabs.ibm.com>
Hi Nicholas,
On Fri, Jul 07, 2017 at 01:06:46AM +1000, Nicholas Piggin wrote:
> On Wed, 5 Jul 2017 22:08:14 +0530
> "Gautham R. Shenoy" <ego@linux.vnet.ibm.com> wrote:
>
> > From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
> >
> > In this patch we define a new function named pnv_power8_idle_init().
> >
> > We move the following code from pnv_init_idle_states() into this newly
> > defined function.
> > a) That patches out pnv_fastsleep_workaround_at_entry/exit when
> > no states with OPAL_PM_SLEEP_ENABLED_ER1 are present.
> > b) Creating a sysfs control to choose how the workaround has to be
> > applied when a OPAL_PM_SLEEP_ENABLED_ER1 state is present.
> > c) Set ppc_md.power_save to power7_idle when OPAL_PM_NAP_ENABLED is
> > present.
> >
> > With this, all the power8 specific initializations are in one place.
> >
> > Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> > ---
> > arch/powerpc/platforms/powernv/idle.c | 59 ++++++++++++++++++++++++-----------
> > 1 file changed, 40 insertions(+), 19 deletions(-)
> >
> > diff --git a/arch/powerpc/platforms/powernv/idle.c b/arch/powerpc/platforms/powernv/idle.c
> > index a5990d9..c400ff9 100644
> > --- a/arch/powerpc/platforms/powernv/idle.c
> > +++ b/arch/powerpc/platforms/powernv/idle.c
> > @@ -564,6 +564,44 @@ static void __init pnv_power9_idle_init(void)
> > pnv_first_deep_stop_state);
> > }
> >
> > +
> > +static void __init pnv_power8_idle_init(void)
> > +{
> > + int i;
> > + bool has_nap = false;
> > + bool has_sleep_er1 = false;
> > + int dt_idle_states = pnv_idle.nr_states;
> > +
> > + for (i = 0; i < dt_idle_states; i++) {
> > + struct pnv_idle_state *state = &pnv_idle.states[i];
> > +
> > + if (state->flags & OPAL_PM_NAP_ENABLED)
> > + has_nap = true;
> > + if (state->flags & OPAL_PM_SLEEP_ENABLED_ER1)
> > + has_sleep_er1 = true;
> > + }
> > +
> > + if (!has_sleep_er1) {
> > + patch_instruction(
> > + (unsigned int *)pnv_fastsleep_workaround_at_entry,
> > + PPC_INST_NOP);
> > + patch_instruction(
> > + (unsigned int *)pnv_fastsleep_workaround_at_exit,
> > + PPC_INST_NOP);
> > + } else {
> > + /*
> > + * OPAL_PM_SLEEP_ENABLED_ER1 is set. It indicates that
> > + * workaround is needed to use fastsleep. Provide sysfs
> > + * control to choose how this workaround has to be applied.
> > + */
> > + device_create_file(cpu_subsys.dev_root,
> > + &dev_attr_fastsleep_workaround_applyonce);
> > + }
> > +
> > + if (has_nap)
> > + ppc_md.power_save = power7_idle;
> > +}
> > +
> > /*
> > * Returns 0 if prop1_len == prop2_len. Else returns -1
> > */
> > @@ -837,6 +875,8 @@ static int __init pnv_probe_idle_states(void)
> >
> > if (cpu_has_feature(CPU_FTR_ARCH_300))
> > pnv_power9_idle_init();
> > + else
> > + pnv_power8_idle_init();
> >
> > for (i = 0; i < dt_idle_states; i++) {
> > if (!pnv_idle.states[i].valid)
> > @@ -858,22 +898,6 @@ static int __init pnv_init_idle_states(void)
> > if (pnv_probe_idle_states())
> > goto out;
> >
> > - if (!(supported_cpuidle_states & OPAL_PM_SLEEP_ENABLED_ER1)) {
> > - patch_instruction(
> > - (unsigned int *)pnv_fastsleep_workaround_at_entry,
> > - PPC_INST_NOP);
> > - patch_instruction(
> > - (unsigned int *)pnv_fastsleep_workaround_at_exit,
> > - PPC_INST_NOP);
>
> So previously this would run on POWER9 and patch out those branches.
> But POWER9 never runs that code, so no problem. Good cleanup.
And that's what I thought, but on checking the assembly code, I found
that pnv_fastsleep_workaround_at_exit is executed on POWER9. Will fix
this!
>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
>
--
Thanks and Regards
gautham.
next prev parent reply other threads:[~2017-07-07 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:38 [PATCH 0/5] powernv:idle: Cleanup idle states initialization Gautham R. Shenoy
2017-07-05 16:38 ` [PATCH 1/5] powernv:idle: Move device-tree parsing to one place Gautham R. Shenoy
2017-07-06 14:53 ` Nicholas Piggin
2017-07-07 11:25 ` Gautham R Shenoy
2017-07-08 8:42 ` Nicholas Piggin
2017-07-05 16:38 ` [PATCH 2/5] powernv:idle: Change return type of pnv_probe_idle_states to int Gautham R. Shenoy
2017-07-06 15:01 ` Nicholas Piggin
2017-07-07 12:26 ` Gautham R Shenoy
2017-07-05 16:38 ` [PATCH 3/5] powernv:idle: Define idle init function for power8 Gautham R. Shenoy
2017-07-06 15:06 ` Nicholas Piggin
2017-07-07 12:43 ` Gautham R Shenoy [this message]
2017-07-05 16:38 ` [PATCH 4/5] powernv:idle: Move initialization of sibling pacas to pnv_alloc_idle_core_states Gautham R. Shenoy
2017-07-06 15:16 ` Nicholas Piggin
2017-07-07 15:04 ` Gautham R Shenoy
2017-07-08 9:00 ` Nicholas Piggin
2017-07-10 4:34 ` Michael Ellerman
2017-07-05 16:38 ` [PATCH 5/5] powernv:idle: Disable LOSE_FULL_CONTEXT states when stop-api fails Gautham R. Shenoy
2017-07-06 15:29 ` Nicholas Piggin
2017-07-07 17:37 ` Gautham R Shenoy
2017-07-08 9:05 ` Nicholas Piggin
2017-07-11 5:04 ` 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=20170707124302.GC8913@in.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rafael@kernel.org \
--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).