From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: lirongqing <lirongqing@baidu.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] platform/x86: intel_speed_select: Use static_cpu_has for HWP check
Date: Fri, 27 Feb 2026 23:01:06 -0800 [thread overview]
Message-ID: <fa10ba0b396d5c67bf1762e06869950496d85280.camel@linux.intel.com> (raw)
In-Reply-To: <20260228035108.2543-1-lirongqing@baidu.com>
On Fri, 2026-02-27 at 22:51 -0500, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> The current implementation of disable_dynamic_sst_features() reads
> MSR_PM_ENABLE to check if HWP is enabled. This can be optimized by
> using static_cpu_has(X86_FEATURE_HWP), which is the standard way
> in the kernel to check for HWP support without the overhead of
> an MSR read.
>
> Replace the MSR read with static_cpu_has().
>
That is not same. Presence of HWP feature means that HWP can be enabled
on this SoC. But user can boot with option to not enable HWP by
intel_pstate driver.
If HWP is not enabled, then SST features can't be enabled.
Thanks,
Srinivas
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c | 5 +---
> -
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git
> a/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> b/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> index b8cdaa2..416620b 100644
> --- a/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> +++ b/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> @@ -556,10 +556,7 @@ static struct tpmi_per_power_domain_info
> *get_instance(int pkg_id, int power_dom
>
> static bool disable_dynamic_sst_features(void)
> {
> - u64 value;
> -
> - rdmsrq(MSR_PM_ENABLE, value);
> - return !(value & 0x1);
> + return !static_cpu_has(X86_FEATURE_HWP);
> }
>
> #define _read_cp_info(name_str, name, offset, start, width,
> mult_factor)\
next prev parent reply other threads:[~2026-02-28 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 3:51 lirongqing
2026-02-28 6:57 ` 答复: " Li,Rongqing(ACG CCN)
2026-02-28 7:02 ` srinivas pandruvada
2026-02-28 7:01 ` srinivas pandruvada [this message]
2026-02-28 7:22 ` 答复: [外部邮件] " Li,Rongqing(ACG CCN)
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=fa10ba0b396d5c67bf1762e06869950496d85280.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=platform-driver-x86@vger.kernel.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
all inboxes | Powered by JetHome®