All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaidyanathan Srinivasan <svaidy@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: "Gautham R . Shenoy" <ego@linux.vnet.ibm.com>,
	Michael Neuling <mikey@neuling.org>,
	linuxppc-dev@lists.ozlabs.org,
	Pratik Rajesh Sampat <psampat@linux.ibm.com>,
	Ryan P Grimm <rgrimm@us.ibm.com>
Subject: Re: [PATCH] powerpc/powernv/idle: add a basic stop 0-3 driver for POWER10
Date: Wed, 19 Aug 2020 23:02:02 +0530	[thread overview]
Message-ID: <20200819173202.GA48285@drishya.in.ibm.com> (raw)
In-Reply-To: <20200819094700.493399-1-npiggin@gmail.com>

* Nicholas Piggin <npiggin@gmail.com> [2020-08-19 19:47:00]:

> This driver does not restore stop > 3 state, so it limits itself
> to states which do not lose full state or TB.
> 
> The POWER10 SPRs are sufficiently different from P9 that it seems
> easier to split out the P10 code. The POWER10 deep sleep code
> (e.g., the BHRB restore) has been taken out, but it can be re-added
> when stop > 3 support is added.
> 
> Cc: Ryan P Grimm <rgrimm@us.ibm.com>
> Cc: Michael Neuling <mikey@neuling.org>
> Cc: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> Cc: Pratik Rajesh Sampat <psampat@linux.ibm.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>


Tested-by: Vaidyanathan Srinivasan <svaidy@linux.ibm.com>

This patch series was tested on P9 and P10. Correct set of
stop states were discovered and enabled in the platform.

Further the SPRs saved and restored by this code has also been
tested along with cpuidle state tests and cpu offline/online tests.

Thank for patch.

--Vaidy


  reply	other threads:[~2020-08-19 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  9:47 [PATCH] powerpc/powernv/idle: add a basic stop 0-3 driver for POWER10 Nicholas Piggin
2020-08-19 17:32 ` Vaidyanathan Srinivasan [this message]
2020-08-19 17:36 ` Gautham R Shenoy
2020-08-19 17:40 ` Pratik Sampat
2020-08-19 19:08 ` Pratik Sampat
2020-09-17 11:27 ` 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=20200819173202.GA48285@drishya.in.ibm.com \
    --to=svaidy@linux.ibm.com \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=npiggin@gmail.com \
    --cc=psampat@linux.ibm.com \
    --cc=rgrimm@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.