From: Frederic Weisbecker <frederic@kernel.org>
To: Naman Jain <namjain@linux.microsoft.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Dexuan Cui <decui@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Long Li <longli@microsoft.com>,
Marco Crivellari <marco.crivellari@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
Phil Auld <pauld@redhat.com>, Thomas Gleixner <tglx@kernel.org>,
Waiman Long <longman@redhat.com>, Wei Liu <wei.liu@kernel.org>,
linux-hyperv@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH 39/47] clocksource: hyper-v: Move CPUHP_AP_HYPERV_TIMER_STARTING post stop_machine()
Date: Fri, 6 Nov 2026 13:38:10 +0100 [thread overview]
Message-ID: <au3KMiLqclDsVESx@pavilion.home> (raw)
In-Reply-To: <da4937bd-542e-4a46-a5a5-35596572f5df@linux.microsoft.com>
Le Fri, Nov 06, 2026 at 03:37:26PM +0530, Naman Jain a écrit :
>
>
> On 11/5/2026 10:00 PM, Frederic Weisbecker wrote:
> > Between CPUHP_TEARDOWN_CPU and CPUHP_AP_OFFLINE, stop_machine executes
> > all the teardown callbacks while stopping all CPUs in the system. This
> > doesn't mix-up well with running RT or isolated tasks.
> >
> > In order to transition smoothly from global stop_machine to finer
> > grained synchronization between teardown callbacks and the other CPUs,
> > a new stop machine post function has been introduced to be executed
> > after the main one with IRQs still disabled while other CPUs can exit
> > stop_machine().
> >
> > The teardown callback here simply performs timer and IRQ disablement,
> > both of which can run concurrently with other CPUs.
> >
> > Move it to post stop_machine() accordingly.
> >
> > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> > ---
> > kernel/cpu.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/cpu.c b/kernel/cpu.c
> > index 93b8498e26c4..b49b67ef5ecb 100644
>
> I am unable to correlate the commit message with the change and could not
> find the rest of the series on lore to get more context.
Sorry about that. I couldn't CC everyone to the motherpatch so I tried
to bring as much context as I could to each individual follow-up's changelog.
Probably that wasn't enough.
So here is the cover letter that explains the whole intent:
https://lore.kernel.org/lkml/20261105163045.38862-1-frederic@kernel.org/
And the patch that does the initial infrastructure change to stop machine:
https://lore.kernel.org/lkml/20261105163045.38862-2-frederic@kernel.org/
Thanks.
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2026-11-06 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261105163045.38862-1-frederic@kernel.org>
2026-11-05 16:30 ` [PATCH 39/47] clocksource: hyper-v: Move CPUHP_AP_HYPERV_TIMER_STARTING post stop_machine() Frederic Weisbecker
2026-11-06 10:07 ` Naman Jain
2026-11-06 12:38 ` Frederic Weisbecker [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=au3KMiLqclDsVESx@pavilion.home \
--to=frederic@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=longman@redhat.com \
--cc=marco.crivellari@suse.com \
--cc=namjain@linux.microsoft.com \
--cc=pauld@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=wei.liu@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