mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Teddy Astie <teddy.astie@vates.tech>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	regressions@lists.linux.dev, Thomas Gleixner <tglx@linutronix.de>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Olivier Lambert <olivier.lambert@vates.tech>
Subject: Re: [REGRESSION][BISECTED] Long boot time with Xen HVM guests during PV spinlock initialization
Date: Mon, 8 Jun 2026 12:57:46 +0200	[thread overview]
Message-ID: <8d17788d-c7cf-47ff-9216-41f920eea621@suse.com> (raw)
In-Reply-To: <1780914594.8631fc262581453bbf619ec5b2062170.19ea6c8227b000701b@vates.tech>


[-- Attachment #1.1.1: Type: text/plain, Size: 1535 bytes --]

Add Thomas Gleixner (author of the patch introducing the regression).


Juergen

On 08.06.26 12:29, Teddy Astie wrote:
> Hello,
> 
> In 6.12.5+ kernels on AMD CPUs, we observe abnormally long boot times where the 
> guest is struggling on PV spinlock initialization.
> 
> This occurs starting with 6.12.5, and also on more recent kernels on Intel 
> platforms, but that hasn't been fully investigated at this time (but I assume 
> it's a variant of the same issue).
> 
> This occurs since a backport of 76031d9 ("clocksource: Make negative motion 
> detection more robust").
> 
> Some (claude-based) analysis made appears to relate that to the lack of proper 
> max_raw_delta in the jiffies clocksource which appears to make the clock fail to 
> progress meaningfully.
> 
> Here is a raw summary of the analysis
>  > We tracked it down to a single stable backport in 6.12.5: commit 1a678f6829a8 
> ("clocksource: Make negative motion detection more robust", upstream 
> 76031d9536a0). It introduces a max_raw_delta field on struct clocksource but 
> never initializes it for the default boot timekeeper (the jiffies clocksource), 
> so clocksource_delta() clamps every delta to 0 and CLOCK_MONOTONIC freezes while 
> that clocksource is active. On this HVM guest, SMP bring-up runs while the 
> jiffies clocksource is still the timekeeper, and the Xen single shot (high 
> resolution) tick then advances jiffies far too slowly, so the secondary CPUs 
> burn seconds in calibrate_delay().
> 
> Teddy


[-- 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 --]

  reply	other threads:[~2026-06-08 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 10:29 Teddy Astie
2026-06-08 10:57 ` Juergen Gross [this message]
2026-06-08 15:13 ` Thomas Gleixner
2026-06-08 21:29   ` Thomas Gleixner
2026-06-09  9:27   ` Teddy Astie
2026-06-09 15:14     ` Thomas Gleixner
2026-06-12  9:02       ` Teddy Astie
2026-06-13 13:28       ` [tip: timers/core] time/jiffies: Register jiffies clocksource before usage tip-bot2 for Thomas Gleixner
     [not found]         ` <CGME20260616184701eucas1p13c7aff447073832095aa4adfb85935f0@eucas1p1.samsung.com>
2026-06-16 18:47           ` Marek Szyprowski
2026-06-17 14:17             ` Conor Dooley
2026-06-17 15:04               ` Thomas Gleixner
2026-06-17 15:04             ` Thomas Gleixner

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=8d17788d-c7cf-47ff-9216-41f920eea621@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olivier.lambert@vates.tech \
    --cc=regressions@lists.linux.dev \
    --cc=teddy.astie@vates.tech \
    --cc=tglx@linutronix.de \
    --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 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®