From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: MTRR init sequence in Xen
Date: Thu, 22 Jan 2026 18:18:45 +0100 [thread overview]
Message-ID: <aXJb9V34fTLR1Fd3@Mac.lan> (raw)
In-Reply-To: <145af46c-eab5-4d0f-ba35-4ae646c0e4cd@suse.com>
On Thu, Jan 22, 2026 at 04:56:24PM +0100, Jürgen Groß wrote:
> Just as a heads up: a hardware partner of SUSE has seen hard lockups
> of the Linux kernel during boot on a new machine. This machine has
> 8 NUMA nodes and 960 CPUs. The hang occurs in roughly 1.5% of the boot
> attempts in MTRR initialization of the APs.
Do you know why you get hard lockups? Is some watchdog triggering on
Linux? Otherwise I think it should just be slow, but ultimately
succeed?
> I have sent a small patch series to LKML which seems to fix the problem:
> https://lore.kernel.org/lkml/20260121141106.755458-1-jgross@suse.com/
>
> As Xen MTRR handling is taken from the Linux kernel, I guess the same
> problem could happen in Xen, too.
>
> As the hang always occurred while waiting for the lock, which is
> serializing the single CPUs doing MTRR initialization, my solution was
> to eliminate the lock, allowing all APs to init MTRRs in parallel.
>
> Maybe we want to do the same in Xen.
Hm, yes, I think Xen would be equally affected with regards to being
contented on a lock while updating MTRRs. The MTRR initialization is
deferred until all APs are up, and serialized on the
set_atomicity_lock lock.
Regards, Roger.
next prev parent reply other threads:[~2026-01-22 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 15:56 MTRR init sequence in Xen Jürgen Groß
2026-01-22 17:18 ` Roger Pau Monné [this message]
2026-01-22 19:22 ` Jürgen Groß
2026-01-22 17:21 ` Andrew Cooper
2026-01-22 17:36 ` Roger Pau Monné
2026-01-22 19:24 ` Jürgen Groß
2026-01-23 9:24 ` Roger Pau Monné
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=aXJb9V34fTLR1Fd3@Mac.lan \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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 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.