From: "Jürgen Groß" <jgross@suse.com>
To: Dave Hansen <dave.hansen@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v2 0/4] x86/mtrr: Allow MTRR updates on multiple CPUs in parallel
Date: Fri, 13 Mar 2026 07:03:36 +0100 [thread overview]
Message-ID: <cc490898-fff3-4984-8c3e-eeda16bcb757@suse.com> (raw)
In-Reply-To: <720a1f4d-edb7-4645-9813-2a932659c4b2@intel.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1715 bytes --]
On 12.03.26 22:33, Dave Hansen wrote:
> On 3/11/26 02:08, Juergen Gross wrote:
>> Any real reason not to take this patch series?
>
> Uhh, it has zero review comments on it. That's usually a pretty good reason.
>
> It is a little worrying that this is even happening. Is there just a
> single blip during boot when the MTRRs are "corrected" and then it's
> never a problem again? Or is it causing latency blips all the time?
The machine having the lockups has been verified to have inconsistent
initial MTRR values, so the APs (at least some of them) need to update
their MTRR registers during boot.
BUT: I believe that the same could happen in case some device driver needs
to set some MTRR registers when adding a device. The code will do the same
as during boot: all CPUs need to do the update of the MTRR(s) using
stop_machine_cpuslocked(), which will serialize the updates across the CPUs.
With enough CPUs on the machine time will sum up again.
> I do share some of Peter's concern that this is creaky, fragile,
> lightly-used code and this series is mucking with it to work around a
> BIOS issue.
The real change on each CPU is just the drop of global variable use and the
drop of the lock. MTRR handling itself on each CPU isn't modified.
Additionally there is even a comment in today's code that doing only one
CPU at a time is not an optimal solution and that doing all CPUs at the same
time would be the preferred way to handle it.
In case you are really worried that updating all CPUs in parallel might be
problematic in rare cases, I could be talked into making the lock optional
(defaulting to not using it) and controllable via a boot parameter.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2026-03-13 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 11:36 Juergen Gross
2026-01-30 11:36 ` [PATCH v2 1/4] x86/mtrr: Move cache_enable() and cache_disable() to mtrr/generic.c Juergen Gross
2026-01-30 11:36 ` [PATCH v2 2/4] x86/mtrr: Introduce MTRR work state structure Juergen Gross
2026-01-30 11:36 ` [PATCH v2 3/4] x86/mtrr: Add a prepare_set hook to mtrr_ops Juergen Gross
2026-01-30 11:36 ` [PATCH v2 4/4] x86/mtrr: Drop cache_disable_lock Juergen Gross
2026-02-09 9:12 ` [PATCH v2 0/4] x86/mtrr: Allow MTRR updates on multiple CPUs in parallel Juergen Gross
2026-02-09 18:37 ` H. Peter Anvin
2026-02-10 6:51 ` Jürgen Groß
2026-02-10 7:28 ` H. Peter Anvin
2026-02-12 16:24 ` Jürgen Groß
2026-02-12 16:54 ` H. Peter Anvin
2026-02-13 13:21 ` Jürgen Groß
2026-03-11 9:08 ` Juergen Gross
2026-03-12 21:33 ` Dave Hansen
2026-03-13 6:03 ` Jürgen Groß [this message]
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=cc490898-fff3-4984-8c3e-eeda16bcb757@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.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
all inboxes | Powered by JetHome®