From: Nicholas Piggin <npiggin@gmail•com>
To: linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>,
Michael Ellerman <mpe@ellerman•id.au>,
Vaidyanathan Srinivasan <svaidy@linux•vnet.ibm.com>,
"Gautham R . Shenoy" <ego@linux•vnet.ibm.com>,
"Rafael J . Wysocki" <rjw@rjwysocki•net>,
Daniel Lezcano <daniel.lezcano@linaro•org>,
linux-pm@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: [PATCH 0/3] powerpc (powernv and pseries) cpuidle driver improvmeents
Date: Wed, 14 Jun 2017 23:02:38 +1000 [thread overview]
Message-ID: <20170614130241.19865-1-npiggin@gmail.com> (raw)
Hi,
These are a few small improvements that came from doing an
optimisation pass over powerpc cpu idle paths.
Michael reminded me to cc the cpuidle maintainers. I think he
will take the patches through the powerpc tree, but any suggestion
or ack or nack would be welcome.
Thanks,
Nick
Nicholas Piggin (3):
cpuidle: powerpc: cpuidle set polling before enabling irqs
cpuidle: powerpc: read mostly for common globals
cpuidle: powerpc: no memory barrier after break from idle
drivers/cpuidle/cpuidle-powernv.c | 25 +++++++++++++++++--------
drivers/cpuidle/cpuidle-pseries.c | 22 +++++++++++++++-------
2 files changed, 32 insertions(+), 15 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-14 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:02 Nicholas Piggin [this message]
2017-06-14 13:02 ` [PATCH 1/3] cpuidle: powerpc: cpuidle set polling before enabling irqs Nicholas Piggin
2017-06-29 12:21 ` [1/3] " Michael Ellerman
2017-06-29 20:38 ` Rafael J. Wysocki
2017-06-30 3:45 ` Michael Ellerman
2017-06-30 12:51 ` Rafael J. Wysocki
2017-07-04 2:59 ` Michael Ellerman
2017-06-14 13:02 ` [PATCH 2/3] cpuidle: powerpc: read mostly for common globals Nicholas Piggin
2017-06-14 13:02 ` [PATCH 3/3] cpuidle: powerpc: no memory barrier after break from idle Nicholas Piggin
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=20170614130241.19865-1-npiggin@gmail.com \
--to=npiggin@gmail$(echo .)com \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=ego@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=rjw@rjwysocki$(echo .)net \
--cc=svaidy@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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