From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael@kernel.org, viresh.kumar@linaro.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v2 0/2] Update highest frequency of a CPU after boot
Date: Mon, 24 Jun 2024 09:11:07 -0700 [thread overview]
Message-ID: <20240624161109.1427640-1-srinivas.pandruvada@linux.intel.com> (raw)
Intel Xeon servers, which are capable of dynamic highest performance
change, are unable to achieve the highest frequency when the performance
profile is changed.
The highest frequency at which a CPU can operate is not fixed and can
vary after the system boots. These changes can be initiated by switching
to different performance profiles using the Intel Speed Select Technology
interface. Additionally, adjustments can be made remotely through a BMC
(Baseboard Management Controller) interface. Administrators can select
various performance profiles to align with specific performance
requirements, as these choices will directly influence the total power
consumption and cooling requirements.
Whenever an administrator switches to a different performance profile that
alters the highest frequency, the hardware sends an interrupt and update
the new highest frequency at which the system can operate. This interrupt
can be enabled via the MSR_HWP_INTERRUPT register, and only if support is
indicated by the CPUID[6].EAX[15] = 1.
To enable changes to the highest frequency, add a CPU features flag and
enable the HWP (Hardware P-states) highest performance change interrupt
when it is supported by the CPU.
v2:
- Prevent display in /proc/cpuinfo flags
- Use cpu_feature_enabled() instead of boot_cpu_has()
Srinivas Pandruvada (2):
x86/cpufeatures: Add HWP highest perf change feature flag
cpufreq: intel_pstate: Support highest performance change interrupt
arch/x86/include/asm/cpufeatures.h | 1 +
drivers/cpufreq/intel_pstate.c | 23 +++++++++++++++++++----
2 files changed, 20 insertions(+), 4 deletions(-)
--
2.40.1
next reply other threads:[~2024-06-24 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:11 Srinivas Pandruvada [this message]
2024-06-24 16:11 ` [PATCH v2 1/2] x86/cpufeatures: Add HWP highest perf change feature flag Srinivas Pandruvada
2024-06-24 17:45 ` Borislav Petkov
2024-06-24 16:11 ` [PATCH v2 2/2] cpufreq: intel_pstate: Support highest performance change interrupt Srinivas Pandruvada
2024-06-25 19:04 ` [PATCH v2 0/2] Update highest frequency of a CPU after boot Rafael J. Wysocki
2024-06-28 18:55 ` Rafael J. Wysocki
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=20240624161109.1427640-1-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=x86@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