From: Xiaojian Du <xiaojidu@amd.com>
To: "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Mario Limonciello <mario.limonciello@amd.com>,
Huang Rui <ray.huang@amd.com>, Perry Yuan <perry.yuan@amd.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
David Wang <00107082@163.com>
Subject: Re: [PATCH 3/3] cpufreq/amd-pstate: Remove warning for X86_FEATURE_CPPC on Zen1 and Zen2
Date: Wed, 14 Aug 2024 17:29:04 +0800 [thread overview]
Message-ID: <9ca4054e-a130-b65b-d2f3-3ef84c997dfd@amd.com> (raw)
In-Reply-To: <20240813095459.2122-1-gautham.shenoy@amd.com>
Hi Gautham,
On 2024/8/13 17:54, Gautham R. Shenoy wrote:
> ...
>
> This feature bit corresponds to CPUID 0x80000008.ebx[27] which is a
> reserved bit on the Zen1 and Zen2 platforms, and is expected to be
> cleared on these platforms. Thus printing the warning message for Zen1
> and Zen2 models when X86_FEATURE_CPPC is incorrect. Fix this.
>
> ...
> if (!cpu_feature_enabled(X86_FEATURE_CPPC)) {
> - if (cpu_feature_enabled(X86_FEATURE_ZEN1) || cpu_feature_enabled(X86_FEATURE_ZEN2)) {
> - if (c->x86_model > 0x60 && c->x86_model < 0xaf)
> - warn = true;
Some models of ZEN2 APU/CPU require this warning info, like Renoir
(Ryzen 7 4800H mobile APU/4750G desktop APU,
Ryzen 5 4600 desktop CPU), Lucienne (Ryzen 5 5500U mobile APU) and
Aerith (APU of Steam Deck console).
So it has to use model ID to narrow down the coverage.
For ZEN1 APU/CPU, this warning can be removed completely, because ZEN1
doesn't support CPPC.
Thanks,
Xiaojian
> - } else if (cpu_feature_enabled(X86_FEATURE_ZEN3) || cpu_feature_enabled(X86_FEATURE_ZEN4)) {
> + if (cpu_feature_enabled(X86_FEATURE_ZEN3) ||
> + cpu_feature_enabled(X86_FEATURE_ZEN4)) {
> if ((c->x86_model > 0x10 && c->x86_model < 0x1F) ||
> (c->x86_model > 0x40 && c->x86_model < 0xaf))
> warn = true;
next prev parent reply other threads:[~2024-08-14 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 9:51 [PATCH 0/3] cpufreq/amd-pstate: A set of fixes Gautham R. Shenoy
2024-08-13 9:51 ` [PATCH 1/3] cpufreq: amd-pstate: Fix uninitialized variable in amd_pstate_cpu_boost_update() Gautham R. Shenoy
2024-08-13 9:51 ` [PATCH 2/3] cpufreq/amd-pstate: Use topology_logical_package_id() instead of logical_die_id() Gautham R. Shenoy
2024-08-13 9:54 ` [PATCH 3/3] cpufreq/amd-pstate: Remove warning for X86_FEATURE_CPPC on Zen1 and Zen2 Gautham R. Shenoy
2024-08-14 9:29 ` Xiaojian Du [this message]
2024-08-21 5:41 ` Gautham R. Shenoy
2024-08-22 20:41 ` [PATCH 0/3] cpufreq/amd-pstate: A set of fixes Mario Limonciello
2024-08-23 4:13 ` Gautham R. Shenoy
2024-08-23 15:42 ` Mario Limonciello
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=9ca4054e-a130-b65b-d2f3-3ef84c997dfd@amd.com \
--to=xiaojidu@amd.com \
--cc=00107082@163.com \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=dan.carpenter@linaro.org \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--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