[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250904071732.3513694-1-maobibo@loongson.cn>
Date: Thu, 4 Sep 2025 15:17:30 +0800
From: Bibo Mao <maobibo@...ngson.cn>
To: Huacai Chen <chenhuacai@...nel.org>,
Anna-Maria Behnsen <anna-maria@...utronix.de>,
Frederic Weisbecker <frederic@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org,
loongarch@...ts.linux.dev,
Xianglai Li <lixianglai@...ngson.cn>
Subject: [PATCH v2 0/2] Remove unreasonable detached state set in tick_shutdown()
Function clockevents_switch_state() will check whether it has already
switched to specified state, do nothing if it has.
In function tick_shutdown(), it will set detached state at first and
call clockevents_switch_state() in clockevents_exchange_device(). The
function clockevents_switch_state() will do nothing since it is already
detached state. So the tick timer device will not be shutdown when CPU
is offline.
Here remove state set before calling clockevents_exchange_device(),
its state will be set in function clockevents_switch_state() if it
succeeds to do so.
---
v1 ... v2:
1. Add Fixes tag in patch 1 since those commits removed shutdown calls
made from drivers that assumed the timer core would do so.
2. Remove clockevents shutdown call on LoongArch cpu offline
---
Bibo Mao (2):
tick: Remove unreasonable detached state set in tick_shutdown()
LoongArch: Remove clockevents shutdown call on offlining
arch/loongarch/kernel/time.c | 2 --
kernel/time/tick-common.c | 5 -----
2 files changed, 7 deletions(-)
base-commit: b9a10f876409bf3768178f4aded199e193ddbe33
--
2.39.3
Powered by blists - more mailing lists