From: Huang Rui <ray.huang@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Yuan, Perry" <Perry.Yuan@amd.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Huang, Shimmer" <Shimmer.Huang@amd.com>,
"Du, Xiaojian" <Xiaojian.Du@amd.com>,
"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 0/8] AMD Pstate Fixes And Enhancements
Date: Tue, 19 Mar 2024 13:37:53 +0800 [thread overview]
Message-ID: <ZfkksfgB9cIUkWlu@amd.com> (raw)
In-Reply-To: <CAJZ5v0iQnJCVX0kHNxtOWLcnTXRRjR1HZ6m4CFhKZcQVp1SbEA@mail.gmail.com>
On Mon, Mar 18, 2024 at 08:49:55PM +0800, Rafael J. Wysocki wrote:
> On Mon, Mar 18, 2024 at 10:48 AM Perry Yuan <perry.yuan@amd.com> wrote:
> >
> > The patch series adds some fixes and enhancements to the AMD pstate
> > driver.
> > It enables CPPC v2 for certain processors in the family 17H, as
> > requested
> > by TR40 processor users who expect improved performance and lower system
> > temperature.
> >
> > Additionally, it fixes the initialization of nominal_freq for each
> > cpudata
> > and changes latency and delay values to be read from platform firmware
> > firstly
> > for more accurate timing.
> >
> > A new quirk is also added for legacy processors that lack CPPC
> > capabilities which caused the pstate driver to fail loading.
> >
> > Testing done with one APU system while cpb boost on:
> >
> > amd_pstate_lowest_nonlinear_freq:1701000
> > amd_pstate_max_freq:3501000
> > cpuinfo_max_freq:3501000
> > cpuinfo_min_freq:400000
> > scaling_cur_freq:3084836
> > scaling_max_freq:3501000
> > scaling_min_freq:400000
> >
> > analyzing CPU 6:
> > driver: amd-pstate-epp
> > CPUs which run at the same hardware frequency: 6
> > CPUs which need to have their frequency coordinated by software: 6
> > maximum transition latency: Cannot determine or is not supported.
> > hardware limits: 400 MHz - 3.50 GHz
> > available cpufreq governors: performance powersave
> > current policy: frequency should be within 400 MHz and 3.50 GHz.
> > The governor "powersave" may decide which speed to use
> > within this range.
> > current CPU frequency: Unable to call hardware
> > current CPU frequency: 3.50 GHz (asserted by call to kernel)
> > boost state support:
> > Supported: yes
> > Active: yes
> > AMD PSTATE Highest Performance: 255. Maximum Frequency: 3.50 GHz.
> > AMD PSTATE Nominal Performance: 204. Nominal Frequency: 2.80 GHz.
> > AMD PSTATE Lowest Non-linear Performance: 124. Lowest Non-linear Frequency: 1.70 GHz.
> > AMD PSTATE Lowest Performance: 30. Lowest Frequency: 400 MHz.
> >
> > If someone would like to test this patchset, it would need to apply
> > another patchset on top of this in case of some unexpected issue found.
> >
> > https://lore.kernel.org/lkml/cover.1707297581.git.perry.yuan@amd.com/
> > It implements the amd pstate cpb boost feature
> > the below patch link is old version, please apply the latest version
> > while you start the testing work.
> >
> > I would greatly appreciate any feedbacks.
>
> There are missing changelogs and S-o-b tags in a few messages in this series.
>
> Overall, I would like someone, preferably at AMD, to take
> responsibility for the amd-pstate driver, review patches modifying it
> and ACK the approved ones.
>
> Huang Rui, who is listed in MAINTAINERS as the official maintainer of
> it, does not seem to be interested in it any more.
>
> Can this be addressed, please?
Hi Rafael,
Sorry, I was occupied by other task a couple of months ago. I will talk
with AMD colleagues and figure out the way to make sure the amd-pstate
patches will be actively reviewed and tested. Will give you the feedback.
Thanks,
Ray
prev parent reply other threads:[~2024-03-19 5:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:48 [PATCH v8 0/8] AMD Pstate Fixes And Enhancements Perry Yuan
2024-03-18 9:48 ` [PATCH v8 1/8] cpufreq: amd-pstate: Document *_limit_* fields in struct amd_cpudata Perry Yuan
2024-03-18 12:34 ` Rafael J. Wysocki
2024-03-19 8:03 ` Yuan, Perry
2024-03-18 9:48 ` [PATCH v8 2/8] cpufreq: amd-pstate: Document the units for freq variables in amd_cpudata Perry Yuan
2024-03-18 12:35 ` Rafael J. Wysocki
2024-03-18 9:48 ` [PATCH v8 3/8] cpufreq: amd-pstate: Unify computation of {max,min,nominal,lowest_nonlinear}_freq Perry Yuan
2024-03-18 9:48 ` [PATCH v8 4/8] cpufreq: amd-pstate: Remove amd_get_{min,max,nominal,lowest_nonlinear}_freq() Perry Yuan
2024-03-18 12:36 ` Rafael J. Wysocki
2024-03-18 9:48 ` [PATCH v8 5/8] cpufreq: amd-pstate: Bail out if min/max/nominal_freq is 0 Perry Yuan
2024-03-18 9:48 ` [PATCH v8 6/8] cpufreq: amd-pstate: get transition delay and latency value from ACPI tables Perry Yuan
2024-03-18 9:48 ` [PATCH v8 7/8] cppc_acpi: print error message if CPPC is unsupported Perry Yuan
2024-03-18 9:48 ` [PATCH v8 8/8] cpufreq: amd-pstate: Add quirk for the pstate CPPC capabilities missing Perry Yuan
2024-03-18 12:49 ` [PATCH v8 0/8] AMD Pstate Fixes And Enhancements Rafael J. Wysocki
2024-03-19 5:37 ` Huang Rui [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=ZfkksfgB9cIUkWlu@amd.com \
--to=ray.huang@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Borislav.Petkov@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Shimmer.Huang@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
/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).