From: Thomas Gleixner <tglx@linutronix.de>
To: Frederic Weisbecker <frederic@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [PATCH 00/10] clockevents: Rearrange cpuhotplug operations
Date: Thu, 24 Oct 2024 10:34:34 +0200 [thread overview]
Message-ID: <87wmhx6grp.ffs@tglx> (raw)
In-Reply-To: <20241017165041.6954-1-frederic@kernel.org>
On Thu, Oct 17 2024 at 18:50, Frederic Weisbecker wrote:
> Some recent RCU issues triggered with offline ticks uncovered
> hotplug behaviour differences between oneshot and periodic ticks.
> The former is disabled on the dying CPU but not the latter. Also
> the clockevents hotplug code is quite chaotic. This is a proposal to
> fix the situation.
I like it very much!
> Frederic Weisbecker (10):
> clockevents: Improve clockevents_notify_released() comment
> clockevents: Shutdown and unregister current clockevents at
> CPUHP_AP_TICK_DYING
This has a build fail.
> tick: Remove now unneeded low-res tick stop on CPUHP_AP_TICK_DYING
> arm/twd: Remove clockevents shutdown call on offlining
The ARM prefix preference is:
ARM: smp_twd:
> clocksource/drivers/arm_arch_timer: Remove clockevents shutdown call
> on offlining
> clocksource/driver/arm_global_timer: Remove clockevents shutdown call
> on offlining
> drivers/clocksource/exynos_mct: Remove clockevents shutdown call on
> offlining
> clocksource/drivers/armada-370-xp: Remove clockevents shutdown call on
> offlining
> clocksource/drivers/qcom: Remove clockevents shutdown call on
> offlining
> drivers/clocksource/timer-tegra: Remove clockevents shutdown call on
> offlining
Can you please make the subsystem prefixes for the clocksource drivers
consistent 'clocksource/drivers/foo:' ?
Thanks,
tglx
next prev parent reply other threads:[~2024-10-24 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:50 [PATCH 00/10] clockevents: Rearrange cpuhotplug operations Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 01/10] clockevents: Improve clockevents_notify_released() comment Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-21 5:00 ` kernel test robot
2024-10-17 16:50 ` [PATCH 03/10] tick: Remove now unneeded low-res tick stop on CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 04/10] arm/twd: Remove clockevents shutdown call on offlining Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 05/10] clocksource/drivers/arm_arch_timer: " Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 06/10] clocksource/driver/arm_global_timer: " Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 07/10] drivers/clocksource/exynos_mct: " Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 08/10] clocksource/drivers/armada-370-xp: " Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 09/10] clocksource/drivers/qcom: " Frederic Weisbecker
2024-10-17 16:50 ` [PATCH 10/10] drivers/clocksource/timer-tegra: " Frederic Weisbecker
2024-10-24 8:34 ` Thomas Gleixner [this message]
2024-10-29 12:35 ` [PATCH 00/10] clockevents: Rearrange cpuhotplug operations Frederic Weisbecker
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=87wmhx6grp.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.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 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.