From: Dave Hansen <dave.hansen@intel.com>
To: Juergen Gross <jgross@suse.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: Thu, 12 Mar 2026 14:33:23 -0700 [thread overview]
Message-ID: <720a1f4d-edb7-4645-9813-2a932659c4b2@intel.com> (raw)
In-Reply-To: <cbf8a0e2-dcf2-4e65-a0c6-81fc38643840@suse.com>
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?
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.
next prev parent reply other threads:[~2026-03-12 21:33 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 [this message]
2026-03-13 6:03 ` Jürgen Groß
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=720a1f4d-edb7-4645-9813-2a932659c4b2@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.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®