[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230609075049.2651723-1-songshuaishuai@tinylab.org>
Date: Fri, 9 Jun 2023 15:50:45 +0800
From: Song Shuai <songshuaishuai@...ylab.org>
To: catalin.marinas@....com, will@...nel.org, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, chris@...kel.net,
jcmvbkbc@...il.com, songshuaishuai@...ylab.org,
steven.price@....com, vincenzo.frascino@....com,
leyfoon.tan@...rfivetech.com, mason.huo@...rfivetech.com,
jeeheng.sia@...rfivetech.com, conor.dooley@...rochip.com,
ajones@...tanamicro.com
Cc: linux@...linux.org.uk, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: [PATCH V2 0/4] Remove WARN_ON in save_processor_state
During hibernation or restoration, freeze_secondary_cpus
checks num_online_cpus via BUG_ON, and the subsequent
save_processor_state also does the checking with WARN_ON.
In the case of CONFIG_PM_SLEEP_SMP=n, freeze_secondary_cpus
is not defined, but the sole possible condition to disable
CONFIG_PM_SLEEP_SMP is !SMP where num_online_cpus is always 1.
We also don't have to check it in save_processor_state.
So remove the unnecessary checking in save_processor_state
for ARM,arm64,riscv,xtensa architechtures.
Changes since V1:
https://lore.kernel.org/linux-riscv/20230525025555.24104-1-songshuaishuai@tinylab.org/
- supplement the case of CONFIG_PM_SLEEP_SMP=n in commit message as Will suggests
Song Shuai (4):
ARM: hibernate: remove WARN_ON in save_processor_state
arm64: hibernate: remove WARN_ON in save_processor_state
riscv: hibernate: remove WARN_ON in save_processor_state
xtensa: hibernate: remove WARN_ON in save_processor_state
arch/arm/kernel/hibernate.c | 1 -
arch/arm64/kernel/hibernate.c | 1 -
arch/riscv/kernel/hibernate.c | 1 -
arch/xtensa/kernel/hibernate.c | 1 -
4 files changed, 4 deletions(-)
--
2.20.1
Powered by blists - more mailing lists