From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, Pengjie Zhang <zhangpengjie2@huawei.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
maz@kernel.org, timothy.hayes@arm.com, lpieralisi@kernel.org,
mrigendra.chaubey@gmail.com, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, zhanjie9@hisilicon.com,
zhenglifeng1@huawei.com, lihuisong@huawei.com,
yubowen8@huawei.com, linhongye@h-partners.com,
linuxarm@huawei.com, wangzhi12@huawei.com
Subject: Re: [PATCH v3] arm64: smp: Do not mark secondary CPUs possible under nosmp
Date: Tue, 19 May 2026 16:23:11 +0100 [thread overview]
Message-ID: <177918943007.755487.16810413573676566822.b4-ty@kernel.org> (raw)
In-Reply-To: <20260506090851.1858467-1-zhangpengjie2@huawei.com>
On Wed, 06 May 2026 17:08:51 +0800, Pengjie Zhang wrote:
> Under nosmp (maxcpus=0), arm64 never brings up secondary CPUs.
>
> smp_prepare_cpus() already treats this as a UP-mandated boot and returns
> before marking secondary CPUs present. However, smp_init_cpus() may still
> enumerate firmware-described secondary CPUs and mark them possible before
> that point.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: smp: Do not mark secondary CPUs possible under nosmp
https://git.kernel.org/arm64/c/e7cec385d2c6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-05-19 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 9:08 [PATCH v3] arm64: smp: Do not mark secondary CPUs possible under nosmp Pengjie Zhang
2026-05-19 15:23 ` Will Deacon [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=177918943007.755487.16810413573676566822.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=lihuisong@huawei.com \
--cc=linhongye@h-partners.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=mrigendra.chaubey@gmail.com \
--cc=timothy.hayes@arm.com \
--cc=wangzhi12@huawei.com \
--cc=yubowen8@huawei.com \
--cc=zhangpengjie2@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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