From: Jim Mattson <jmattson@google.com>
To: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, yosry@kernel.org
Cc: Jim Mattson <jmattson@google.com>
Subject: [PATCH v2 0/3] Fix three racy updates to MSR_K7_HWCR
Date: Fri, 12 Jun 2026 14:53:16 -0700 [thread overview]
Message-ID: <20260612215729.1532175-1-jmattson@google.com> (raw)
I was backporting commit 65f55a301766 ("x86/CPU/AMD: Add CPUID faulting
support") to a local branch based on Linux v6.12, when our internal Sashiko
asked:
> Can this corrupt MSR_K7_HWCR? disable_cpuid()->set_cpuid_faulting() is
> called with preemption disabled, but interrupts are still enabled. Since
> msr_set_bit() performs a read-modify-write without disabling interrupts,
> if an IPI arrives between the read and write and modifies MSR_K7_HWCR
> (e.g. acpi-cpufreq toggling Core Performance Boost), the IPI's update
> will be lost.
To confirm that this wasn't just AI slop, I set up an empirical test on a
Turin system. First, I replaced the amd-pstate cpufreq driver with
acpi-cpufreq. Then I ran a test program, where one thread repeatedly reads
CPU0's HWCR, toggles /sys/devices/system/cpu/cpufreq/boost, reads CPU0's
HWCR again, and then verifies that the CPB_DIS bit has flipped. A second
thread, pinned to CPU0, repeatedly calls arch_prctl(ARCH_SET_CPUID, <val>),
where <val> alternates between 0 and 1. With the second thread running, the
first thread soon fails the verification step, indicating that the CPB_DIS
bit change is, in fact, lost.
Per Boris's review of v1, this version hoists the HWCR update logic out
into a new helper, amd_update_hwcr(), which performs the read-modify-write
with interrupts disabled, and converts the three runtime
(non-initialization) HWCR read-modify-write sites to use it:
* set_cpuid_faulting(), fixing the race demonstrated above (patch 1);
* toggle_hw_mce_inject(), which previously performed the
read-modify-write as two independent crosscalls (patch 2);
* boost_set_msr() in acpi-cpufreq, whose process-context invocation on
the cpufreq policy teardown path can race with an HWCR update made by
the MCE injector's crosscall (patch 3).
Initialization-time HWCR updates are left alone for now, to avoid excessive
churn.
v1 -> v2:
- Add some of the cover letter details to the first patch
- Hoist the HWCR update logic out into amd_update_hwcr() [Boris]
- Use the helper in toggle_hw_mce_inject(), collapsing the split
read/write crosscalls into one
- Use the helper in boost_set_msr() [Boris]
v1: https://lore.kernel.org/all/20260609211611.466231-1-jmattson@google.com/
Jim Mattson (3):
x86/CPU/AMD: Avoid racy updates to MSR_K7_HWCR in set_cpuid_faulting()
x86/mce/inject: Avoid racy updates to MSR_K7_HWCR in
toggle_hw_mce_inject()
cpufreq: ACPI: Avoid racy updates to MSR_K7_HWCR in boost_set_msr()
arch/x86/include/asm/msr-index.h | 3 +++
arch/x86/include/asm/processor.h | 2 ++
arch/x86/kernel/cpu/amd.c | 42 ++++++++++++++++++++++++++++++++
arch/x86/kernel/cpu/mce/inject.c | 34 +++++++++++++++++++-------
arch/x86/kernel/process.c | 4 +--
drivers/cpufreq/acpi-cpufreq.c | 7 +++---
6 files changed, 78 insertions(+), 14 deletions(-)
base-commit: 2b414a95b8f7307d42173ba9e580d6d3e2bcbfce
--
2.54.0.1136.gdb2ca164c4-goog
next reply other threads:[~2026-06-12 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:53 Jim Mattson [this message]
2026-06-12 21:53 ` [PATCH v2 1/3] x86/CPU/AMD: Avoid racy updates to MSR_K7_HWCR in set_cpuid_faulting() Jim Mattson
2026-06-12 22:30 ` Yosry Ahmed
2026-06-16 21:54 ` Jim Mattson
2026-06-12 21:53 ` [PATCH v2 2/3] x86/mce/inject: Avoid racy updates to MSR_K7_HWCR in toggle_hw_mce_inject() Jim Mattson
2026-06-12 21:53 ` [PATCH v2 3/3] cpufreq: ACPI: Avoid racy updates to MSR_K7_HWCR in boost_set_msr() Jim Mattson
2026-06-12 23:01 ` [PATCH v2 0/3] Fix three racy updates to MSR_K7_HWCR Andrew Cooper
2026-06-12 23:21 ` Jim Mattson
-- strict thread matches above, loose matches on Subject: below --
2026-06-13 1:55 Christian Ludloff
2026-06-13 15:09 ` Jim Mattson
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=20260612215729.1532175-1-jmattson@google.com \
--to=jmattson@google.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.org \
--cc=yosry@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