From: Piotr Kubaj <piotr.kubaj@intel.com>
To: ltp@lists.linux.it
Cc: helena.anna.dubel@intel.com, tomasz.ossowski@intel.com,
rafael.j.wysocki@intel.com, daniel.niestepski@intel.com
Subject: [LTP] [PATCH v12] high_freq_hwp_cap_cppc.c: new test
Date: Thu, 7 May 2026 09:22:39 +0200 [thread overview]
Message-ID: <20260507072238.102543-2-piotr.kubaj@intel.com> (raw)
Verify for all online logical CPUs that their highest performance value are
the same for HWP Capability MSR 0x771 and CPPC sysfs file.
On HWP-capable x86 platforms the acpi_cppc/highest_perf sysfs attribute is
expected to reflect the same highest-performance value that firmware
programs into the HWP Capabilities MSR (0x771, bits 7:0). A mismatch
between the two interfaces indicates a kernel regression in how CPPC
values are exposed to userspace, and would break tools (e.g. cpupower,
intel_pstate tuning scripts) that rely on the sysfs interface to make
frequency-scaling decisions.
Signed-off-by: Piotr Kubaj <piotr.kubaj@intel.com>
---
Following review, add memset() at the beginning of run().
This also allows to switch to malloc() for mismatch array.
runtest/power_management_tests | 1 +
testcases/kernel/power_management/.gitignore | 1 +
.../power_management/high_freq_hwp_cap_cppc.c | 114 ++++++++++++++++++
3 files changed, 116 insertions(+)
create mode 100644 testcases/kernel/power_management/.gitignore
create mode 100644 testcases/kernel/power_management/high_freq_hwp_cap_cppc.c
diff --git a/runtest/power_management_tests b/runtest/power_management_tests
index b670da6ec..4da57ee72 100644
--- a/runtest/power_management_tests
+++ b/runtest/power_management_tests
@@ -1,4 +1,5 @@
#POWER_MANAGEMENT
+high_freq_hwp_cap_cppc high_freq_hwp_cap_cppc
runpwtests03 runpwtests03.sh
runpwtests04 runpwtests04.sh
runpwtests06 runpwtests06.sh
diff --git a/testcases/kernel/power_management/.gitignore b/testcases/kernel/power_management/.gitignore
new file mode 100644
index 000000000..03f0c83e4
--- /dev/null
+++ b/testcases/kernel/power_management/.gitignore
@@ -0,0 +1 @@
+high_freq_hwp_cap_cppc
diff --git a/testcases/kernel/power_management/high_freq_hwp_cap_cppc.c b/testcases/kernel/power_management/high_freq_hwp_cap_cppc.c
new file mode 100644
index 000000000..bebce943c
--- /dev/null
+++ b/testcases/kernel/power_management/high_freq_hwp_cap_cppc.c
@@ -0,0 +1,114 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Copyright (C) 2026 Piotr Kubaj <piotr.kubaj@intel.com>
+ */
+
+/*\
+ * Verify for all online logical CPUs that their highest performance value are
+ * the same for HWP Capability MSR 0x771 and CPPC sysfs file.
+ *
+ * On HWP-capable x86 platforms the acpi_cppc/highest_perf sysfs attribute is
+ * expected to reflect the same highest-performance value that firmware
+ * programs into the HWP Capabilities MSR (0x771, bits 7:0). A mismatch
+ * between the two interfaces indicates a kernel regression in how CPPC
+ * values are exposed to userspace, and would break tools (e.g. cpupower,
+ * intel_pstate tuning scripts) that rely on the sysfs interface to make
+ * frequency-scaling decisions.
+ */
+
+#include "tst_test.h"
+#include "tst_safe_prw.h"
+
+#define MSR_HWP_CAPABILITIES 0x771
+#define HIGHEST_PERF_MASK 0xFF
+
+static int nproc;
+static int fd = -1;
+static int *mismatch;
+
+static void setup(void)
+{
+ if (access("/dev/cpu/0/msr", F_OK) == -1)
+ tst_brk(TCONF | TERRNO, "msr driver not loaded");
+
+ if (access("/sys/devices/system/cpu/cpu0/acpi_cppc/highest_perf", F_OK) == -1)
+ tst_brk(TCONF | TERRNO, "CPPC sysfs not available");
+
+ nproc = tst_ncpus_conf();
+ mismatch = SAFE_MALLOC(nproc, sizeof(int));
+}
+
+static void cleanup(void)
+{
+ if (fd != -1)
+ SAFE_CLOSE(fd);
+
+ free(mismatch);
+}
+
+static void run(void)
+{
+ bool status = true;
+ char path[PATH_MAX];
+
+ memset(mismatch, 0, nproc * sizeof(*mismatch));
+
+ for (int i = 0; i < nproc; i++) {
+ int online = 1;
+ unsigned long long msr_highest_perf = 0, sysfs_highest_perf = 0;
+
+ if (i) {
+ snprintf(path, sizeof(path), "/sys/devices/system/cpu/cpu%d/online", i);
+ SAFE_FILE_SCANF(path, "%d", &online);
+ }
+
+ if (!online) {
+ tst_res(TINFO, "CPU%d offline, skipping", i);
+ continue;
+ }
+
+ snprintf(path, sizeof(path), "/sys/devices/system/cpu/cpu%d/acpi_cppc/highest_perf", i);
+ SAFE_FILE_SCANF(path, "%llu", &sysfs_highest_perf);
+ tst_res(TDEBUG, "%s: %llu", path, sysfs_highest_perf);
+
+ snprintf(path, sizeof(path), "/dev/cpu/%d/msr", i);
+ fd = SAFE_OPEN(path, O_RDONLY);
+
+ SAFE_PREAD(1, fd, &msr_highest_perf, sizeof(msr_highest_perf), MSR_HWP_CAPABILITIES);
+ SAFE_CLOSE(fd);
+ msr_highest_perf &= HIGHEST_PERF_MASK;
+ tst_res(TDEBUG, "%s: %llu", path, msr_highest_perf);
+
+ if (msr_highest_perf != sysfs_highest_perf) {
+ tst_res(TINFO, "cpu%d: sysfs=%llu MSR=%llu",
+ i, sysfs_highest_perf, msr_highest_perf);
+ mismatch[i] = 1;
+ status = false;
+ }
+ }
+
+ for (int i = 0; i < nproc; i++)
+ tst_res(TINFO, "cpu%d: %s", i, mismatch[i] ? "MISMATCH" : "OK");
+
+ if (status)
+ tst_res(TPASS, "Sysfs and MSR values are equal");
+ else
+ tst_res(TFAIL, "Highest performance values differ between sysfs and MSR");
+}
+
+static struct tst_test test = {
+ .needs_kconfigs = (const char *const []) {
+ "CONFIG_ACPI_CPPC_LIB",
+ "CONFIG_X86_MSR",
+ NULL
+ },
+ .needs_root = 1,
+ .setup = setup,
+ .cleanup = cleanup,
+ .supported_archs = (const char *const []) {
+ "x86",
+ "x86_64",
+ NULL
+ },
+ .test_all = run
+};
--
2.47.3
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Spolka oswiadcza, ze posiada status duzego przedsiebiorcy w rozumieniu ustawy z dnia 8 marca 2013 r. o przeciwdzialaniu nadmiernym opoznieniom w transakcjach handlowych.
Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-05-07 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:22 Piotr Kubaj [this message]
2026-05-07 7:29 ` [LTP] [PATCH v12] high_freq_hwp_cap_cppc.c: new test Andrea Cervesato via ltp
2026-05-14 9:25 ` Kubaj, Piotr
2026-05-07 8:34 ` Andrea Cervesato via ltp
2026-05-07 9:38 ` [LTP] " linuxtestproject.agent
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=20260507072238.102543-2-piotr.kubaj@intel.com \
--to=piotr.kubaj@intel.com \
--cc=daniel.niestepski@intel.com \
--cc=helena.anna.dubel@intel.com \
--cc=ltp@lists.linux.it \
--cc=rafael.j.wysocki@intel.com \
--cc=tomasz.ossowski@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.