From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Souvik Chakravarty <Souvik.Chakravarty@arm.com>,
Thanu.Rangarajan@arm.com, Sudeep Holla <Sudeep.Holla@arm.com>,
Hanjun Guo <guohanjun@huawei.com>,
John Garry <john.garry@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] add SW BOOST support for CPPC
Date: Fri, 5 Jun 2020 14:22:25 +0200 [thread overview]
Message-ID: <CAJZ5v0harpqoN9=jPyuD-P9B1jvRcBShUZT5=8J-uymqEKyCyg@mail.gmail.com> (raw)
In-Reply-To: <20200602051609.ahot4qv2nlb6yh3t@vireshk-i7>
On Tue, Jun 2, 2020 at 7:16 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 30-05-20, 10:08, Xiongfeng Wang wrote:
> > ACPI spec 6.2 section 8.4.7.1 provide the following two CPC registers.
> >
> > "Highest performance is the absolute maximum performance an individual
> > processor may reach, assuming ideal conditions. This performance level
> > may not be sustainable for long durations, and may only be achievable if
> > other platform components are in a specific state; for example, it may
> > require other processors be in an idle state.
> >
> > Nominal Performance is the maximum sustained performance level of the
> > processor, assuming ideal operating conditions. In absence of an
> > external constraint (power, thermal, etc.) this is the performance level
> > the platform is expected to be able to maintain continuously. All
> > processors are expected to be able to sustain their nominal performance
> > state simultaneously."
> >
> > We can use Highest Performance as the max performance in boost mode and
> > Nomial Performance as the max performance in non-boost mode. If the
> > Highest Performance is greater than the Nominal Performance, we assume
> > SW BOOST is supported.
> >
> > Changelog:
> >
> > v4 -> v5:
> > add 'cpu_hotplug_lock' before calling '.set_boost'
> > v3 -> v4:
> > run 'boost_set_msr_each' for each CPU in the policy rather than
> > each CPU in the system for 'acpi-cpufreq'
> > add 'Suggested-by'
> >
> > Xiongfeng Wang (2):
> > cpufreq: change '.set_boost' to act on only one policy
> > CPPC: add support for SW BOOST
> >
> > drivers/cpufreq/acpi-cpufreq.c | 14 ++++++-----
> > drivers/cpufreq/cppc_cpufreq.c | 39 +++++++++++++++++++++++++++--
> > drivers/cpufreq/cpufreq.c | 57 +++++++++++++++++++++++-------------------
> > include/linux/cpufreq.h | 2 +-
> > 4 files changed, 77 insertions(+), 35 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Both patches have been applied as 5.8-rc material with slightly
modified subjects and the changelog of patch [1/2] has been updated.
Thanks!
prev parent reply other threads:[~2020-06-05 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 2:08 [PATCH v5 0/2] add SW BOOST support for CPPC Xiongfeng Wang
2020-05-30 2:08 ` [PATCH v5 1/2] cpufreq: change '.set_boost' to act on only one policy Xiongfeng Wang
2020-05-30 2:08 ` [PATCH v5 2/2] CPPC: add support for SW BOOST Xiongfeng Wang
2020-06-02 5:16 ` [PATCH v5 0/2] add SW BOOST support for CPPC Viresh Kumar
2020-06-05 12:22 ` Rafael J. Wysocki [this message]
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='CAJZ5v0harpqoN9=jPyuD-P9B1jvRcBShUZT5=8J-uymqEKyCyg@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=Souvik.Chakravarty@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=Thanu.Rangarajan@arm.com \
--cc=guohanjun@huawei.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=wangxiongfeng2@huawei.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).