From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: [PATCH 00/10] clockevents: Rearrange cpuhotplug operations v2
Date: Tue, 29 Oct 2024 13:54:41 +0100 [thread overview]
Message-ID: <20241029125451.54574-1-frederic@kernel.org> (raw)
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.
Changes since v1:
* Fix build error
* Fix commits prefixes
Thanks.
Frederic Weisbecker (10):
clockevents: Improve clockevents_notify_released() comment
clockevents: Shutdown and unregister current clockevents at
CPUHP_AP_TICK_DYING
tick: Remove now unneeded low-res tick stop on CPUHP_AP_TICK_DYING
ARM: smp_twd: Remove clockevents shutdown call on offlining
clocksource/drivers/arm_arch_timer: Remove clockevents shutdown call
on offlining
clocksource/drivers/arm_global_timer: Remove clockevents shutdown call
on offlining
clocksource/drivers/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
clocksource/drivers/timer-tegra: Remove clockevents shutdown call on
offlining
arch/arm/kernel/smp_twd.c | 1 -
drivers/clocksource/arm_arch_timer.c | 2 -
drivers/clocksource/arm_global_timer.c | 1 -
drivers/clocksource/exynos_mct.c | 1 -
drivers/clocksource/timer-armada-370-xp.c | 1 -
drivers/clocksource/timer-qcom.c | 1 -
drivers/clocksource/timer-tegra.c | 1 -
include/linux/tick.h | 2 -
kernel/cpu.c | 2 -
kernel/time/clockevents.c | 45 ++++++++++++-----------
kernel/time/tick-internal.h | 3 +-
kernel/time/tick-sched.c | 25 +++----------
12 files changed, 31 insertions(+), 54 deletions(-)
--
2.46.0
next reply other threads:[~2024-10-29 12:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 12:54 Frederic Weisbecker [this message]
2024-10-29 12:54 ` [PATCH 01/10] clockevents: Improve clockevents_notify_released() comment Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-31 12:16 ` [PATCH 02/10] " Marek Szyprowski
2024-10-31 13:09 ` Thomas Gleixner
2024-10-29 12:54 ` [PATCH 03/10] tick: Remove now unneeded low-res tick stop on CPUHP_AP_TICK_DYING Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 04/10] ARM: smp_twd: Remove clockevents shutdown call on offlining Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 05/10] clocksource/drivers/arm_arch_timer: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 06/10] clocksource/drivers/arm_global_timer: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 07/10] clocksource/drivers/exynos_mct: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 08/10] clocksource/drivers/armada-370-xp: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 09/10] clocksource/drivers/qcom: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for Frederic Weisbecker
2024-10-29 12:54 ` [PATCH 10/10] clocksource/drivers/timer-tegra: " Frederic Weisbecker
2024-10-30 20:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2024-10-31 9:51 ` tip-bot2 for 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=20241029125451.54574-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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