From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Yafang Shao" <laoar.shao@gmail.com>,
paulmck@kernel.org, linux-kernel@vger.kernel.org,
jstultz@google.com, sboyd@kernel.org, christian@heusel.eu,
kernel-team@meta.com, "Michal Koutný" <mkoutny@suse.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>
Subject: Re: [PATCH v2] clocksource: Defer marking clocksources unstable to kthread
Date: Mon, 10 Mar 2025 09:57:21 +0100 [thread overview]
Message-ID: <20250310085721.GP16878@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <87ecz62nn4.ffs@tglx>
On Sun, Mar 09, 2025 at 05:07:43PM +0100, Thomas Gleixner wrote:
> On Sun, Mar 09 2025 at 19:36, Yafang Shao wrote:
> > On Sun, Mar 9, 2025 at 12:38 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> >> So as this got introduced in the 6.14 merge window, the proper fix is to
> >> revert commit 8722903cbb8f and send it back to the drawing board. It was
> >> clearly never tested with the various possibilities which invoke
> >> mark_tsc*_unstable().
> >
> > Hello Thomas,
> >
> > It has been reverted by the following commit
> > b9f2b29b9494 ("sched: Don't define sched_clock_irqtime as static key")
>
> That does not help much because the commit is in the sched/core branch,
> which is scheduled for the next merge window. But this wants to be fixed
> in Linus tree before 6.14 final. Peter?
Bah, sometimes I get confused by what's where.
I suppose I can pick that one commit into sched/urgent, hmm?
prev parent reply other threads:[~2025-03-10 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 16:06 [PATCH v2] clocksource: Defer marking clocksources unstable to kthread Paul E. McKenney
2025-03-08 16:38 ` Thomas Gleixner
2025-03-09 11:36 ` Yafang Shao
2025-03-09 15:58 ` Paul E. McKenney
2025-03-09 16:07 ` Thomas Gleixner
2025-03-10 8:57 ` Peter Zijlstra [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=20250310085721.GP16878@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=christian@heusel.eu \
--cc=jstultz@google.com \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=paulmck@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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