From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<tsbogend@alpha.franken.de>, <tglx@kernel.org>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>, <peterz@infradead.org>, <kees@kernel.org>,
<nathan@kernel.org>, <linusw@kernel.org>, <ojeda@kernel.org>,
<david.kaplan@amd.com>, <lukas.bulwahn@redhat.com>,
<ryan.roberts@arm.com>, <maz@kernel.org>, <timothy.hayes@arm.com>,
<lpieralisi@kernel.org>, <thuth@redhat.com>,
<menglong8.dong@gmail.com>, <oupton@kernel.org>,
<yeoreum.yun@arm.com>, <miko.lenczewski@arm.com>,
<broonie@kernel.org>, <kevin.brodsky@arm.com>,
<james.clark@linaro.org>, <yangyicong@hisilicon.com>,
<tabba@google.com>, <osandov@fb.com>, <arnd@arndb.de>,
<anshuman.khandual@arm.com>, <david@kernel.org>,
<akpm@linux-foundation.org>, <ljs@kernel.org>, <dev.jain@arm.com>,
<yang@os.amperecomputing.com>, <chaitanyas.prakash@arm.com>,
<kprateek.nayak@amd.com>, <chenl311@chinatelecom.cn>,
<thorsten.blum@linux.dev>, <chang.seok.bae@intel.com>,
<tim.c.chen@linux.intel.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mips@vger.kernel.org>
Subject: Re: [PATCH v3 00/12] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs
Date: Thu, 9 Jul 2026 19:20:24 +0800 [thread overview]
Message-ID: <1350371d-db50-4c3d-adae-6657e2c0e3fc@huawei.com> (raw)
In-Reply-To: <e0607dbe-4d55-4aee-8368-25110848bc09@linux.ibm.com>
On 6/29/2026 12:04 PM, Shrikanth Hegde wrote:
>
>
> On 6/24/26 2:55 PM, Jinjie Ruan wrote:
>> Support for parallel secondary CPU bringup is already utilized by x86,
>> MIPS, and RISC-V. This patch brings this capability to the arm64
>> architecture.
>>
>> Introduce CONFIG_HOTPLUG_PARALLEL_SMT to avoid primary SMT threads
>> to boot first constraint.
>>
>> And add a 'cpu' parameter to update_cpu_boot_status() to allow updating
>> the boot status at a per-CPU granularity during parallel bringup.
>>
>> Rework the global `secondary_data` and `__early_cpu_boot_status` accessed
>> during early boot into per-CPU arrays to allow secondary CPUs to boot
>> in parallel.
>>
>
> Shouldn't this be called CONFIG_BRINGUP_PARALLEL instead?
> Hotplug usually means disable/enable CPU at runtime.
According to my understanding, the parallelism here includes CPU bringup
and hotplug.
prev parent reply other threads:[~2026-07-09 11:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 9:25 [PATCH v3 00/12] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 01/12] cpu/hotplug: Introduce CONFIG_HOTPLUG_PARALLEL_SMT Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 02/12] cpu/hotplug: Propagate bring-up status to arch_cpuhp_cleanup_kick_cpu() Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 03/12] arm64: smp: Tidy up smp_prepare_cpus() Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 04/12] arm64: smp: Tidy up cpuinfo init and cpufeature updates Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 05/12] arm64: smp: Defer RCU registration during secondary CPU bringup Jinjie Ruan
2026-07-06 17:39 ` Will Deacon
2026-07-07 3:02 ` Jinjie Ruan
2026-07-07 10:27 ` Will Deacon
2026-07-08 9:13 ` Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 06/12] arm64: smp: Use generic HOTPLUG_SPLIT_STARTUP machinery for CPU onlining Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 07/12] arm64: cpu_ops: Make 'cpu_operations' pointer global instead of per-cpu Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 08/12] arm64: cpu_ops: Introduce get_secondary_cpu_ops() Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 09/12] arm64: cpufeature: Ensure atomic updates to system_cpucaps bitmap Jinjie Ruan
2026-07-06 17:40 ` Will Deacon
2026-07-07 3:24 ` Jinjie Ruan
2026-07-08 10:01 ` Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 10/12] arm64: smp: Pass CPU ID to update_cpu_boot_status() Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 11/12] arm64: smp: Rework early boot data into per-CPU arrays Jinjie Ruan
2026-06-24 9:25 ` [PATCH v3 12/12] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs Jinjie Ruan
2026-07-07 4:00 ` Jinjie Ruan
2026-07-07 10:30 ` Will Deacon
2026-06-24 12:16 ` [PATCH v3 00/12] " Will Deacon
2026-06-24 14:59 ` Borislav Petkov
2026-06-25 1:34 ` Jinjie Ruan
2026-07-06 17:39 ` Will Deacon
2026-07-07 8:14 ` Jinjie Ruan
2026-07-07 10:37 ` Will Deacon
2026-07-08 9:36 ` Jinjie Ruan
2026-07-09 11:45 ` Jinjie Ruan
2026-06-29 4:04 ` Shrikanth Hegde
2026-07-09 11:20 ` Jinjie Ruan [this message]
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=1350371d-db50-4c3d-adae-6657e2c0e3fc@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chaitanyas.prakash@arm.com \
--cc=chang.seok.bae@intel.com \
--cc=chenl311@chinatelecom.cn \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hpa@zytor.com \
--cc=james.clark@linaro.org \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=kprateek.nayak@amd.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=maz@kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=miko.lenczewski@arm.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=osandov@fb.com \
--cc=oupton@kernel.org \
--cc=peterz@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=sshegde@linux.ibm.com \
--cc=tabba@google.com \
--cc=tglx@kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=thuth@redhat.com \
--cc=tim.c.chen@linux.intel.com \
--cc=timothy.hayes@arm.com \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=yangyicong@hisilicon.com \
--cc=yeoreum.yun@arm.com \
/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