From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: [PATCH v2 2/3] cpu/hotplug: Weak fallback for arch_cpuhp_init_parallel_bringup
Date: Mon, 15 Jul 2024 21:35:29 +0800 [thread overview]
Message-ID: <20240715-loongarch-hotplug-v2-2-7d18b3d46b11@flygoat.com> (raw)
In-Reply-To: <20240715-loongarch-hotplug-v2-0-7d18b3d46b11@flygoat.com>
It is a general assumption that architectures entitled to parallel
bringup with CONFIG_HOTPLUG_PARALLEL do expect parallel bringup to
be available.
Provide a weak fallback arch_cpuhp_init_parallel_bringup function
to match this assumption.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
kernel/cpu.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index c89e0e91379a..16323610cd20 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1829,6 +1829,11 @@ static inline const struct cpumask *cpuhp_get_primary_thread_mask(void)
}
#endif
+bool __weak arch_cpuhp_init_parallel_bringup(void)
+{
+ return true;
+}
+
/*
* On architectures which have enabled parallel bringup this invokes all BP
* prepare states for each of the to be onlined APs first. The last state
--
2.45.2
next prev parent reply other threads:[~2024-07-15 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 13:35 [PATCH v2 0/3] LoongArch: CPU parallel bring up Jiaxun Yang
2024-07-15 13:35 ` [PATCH v2 1/3] cpu/hotplug: Make HOTPLUG_PARALLEL independent of HOTPLUG_SMT Jiaxun Yang
2024-07-16 4:45 ` Thomas Gleixner
2024-07-15 13:35 ` Jiaxun Yang [this message]
2024-07-16 4:53 ` [PATCH v2 2/3] cpu/hotplug: Weak fallback for arch_cpuhp_init_parallel_bringup Thomas Gleixner
2024-07-15 13:35 ` [PATCH v2 3/3] LoongArch: SMP: Implement parallel CPU bring up Jiaxun Yang
2024-07-16 4:56 ` Thomas Gleixner
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=20240715-loongarch-hotplug-v2-2-7d18b3d46b11@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®