From: Vaidyanathan Srinivasan <svaidy@linux.ibm.com>
To: Pratik Rajesh Sampat <psampat@linux.ibm.com>
Cc: ego@linux.vnet.ibm.com, mikey@neuling.org,
pratik.r.sampat@gmail.com, linux-kernel@vger.kernel.org,
npiggin@gmail.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Revert "powerpc/powernv/idle: Replace CPU feature check with PVR check"
Date: Wed, 26 Aug 2020 15:10:09 +0530 [thread overview]
Message-ID: <20200826094009.GC48285@drishya.in.ibm.com> (raw)
In-Reply-To: <20200826082918.89306-1-psampat@linux.ibm.com>
* Pratik Rajesh Sampat <psampat@linux.ibm.com> [2020-08-26 13:59:18]:
> Cpuidle stop state implementation has minor optimizations for P10
> where hardware preserves more SPR registers compared to P9.
> The current P9 driver works for P10, although does few extra
> save-restores. P9 driver can provide the required power management
> features like SMT thread folding and core level power savings
> on a P10 platform.
>
> Until the P10 stop driver is available, revert the commit which
> allows for only P9 systems to utilize cpuidle and blocks all
> idle stop states for P10.
> Cpu idle states are enabled and tested on the P10 platform
> with this fix.
>
> This reverts commit 8747bf36f312356f8a295a0c39ff092d65ce75ae.
>
> Fixes: 8747bf36f312 ("powerpc/powernv/idle: Replace CPU feature check with PVR check")
> Signed-off-by: Pratik Rajesh Sampat <psampat@linux.ibm.com>
Reviewed-by: Vaidyanathan Srinivasan <svaidy@linux.ibm.com>
> ---
> @mpe: This revert would resolve a staging issue wherein the P10 stop
> driver is not yet ready while cpuidle stop states need not be blocked
> on 5.9 for Power10 systems which could cause SMT folding related
> performance issues.
>
> The P10 stop driver is in the works here:
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216773.html
>
> arch/powerpc/platforms/powernv/idle.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/platforms/powernv/idle.c b/arch/powerpc/platforms/powernv/idle.c
> index 77513a80cef9..345ab062b21a 100644
> --- a/arch/powerpc/platforms/powernv/idle.c
> +++ b/arch/powerpc/platforms/powernv/idle.c
> @@ -1223,7 +1223,7 @@ static void __init pnv_probe_idle_states(void)
> return;
> }
>
> - if (pvr_version_is(PVR_POWER9))
> + if (cpu_has_feature(CPU_FTR_ARCH_300))
> pnv_power9_idle_init();
>
> for (i = 0; i < nr_pnv_idle_states; i++)
This revert solves the stated problem and makes kernel v5.9 work
reasonable well on P10 with stop states which are required for SMT
mode changes.
Complete P10 driver has been in the works and will build on this fix
and complete the required platform support and optimizations.
--Vaidy
next prev parent reply other threads:[~2020-08-26 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 8:29 [PATCH] Revert "powerpc/powernv/idle: Replace CPU feature check with PVR check" Pratik Rajesh Sampat
2020-08-26 8:37 ` Christophe Leroy
2020-08-26 9:14 ` Pratik Sampat
2020-08-27 6:07 ` Michael Ellerman
2020-08-26 9:40 ` Vaidyanathan Srinivasan [this message]
2020-08-27 7:46 ` Michael Ellerman
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=20200826094009.GC48285@drishya.in.ibm.com \
--to=svaidy@linux.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=pratik.r.sampat@gmail.com \
--cc=psampat@linux.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).