From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, alex@ghiti.fr, atish.patra@linux.dev,
anup@brainfault.org, linux-kernel@vger.kernel.org,
ajones@ventanamicro.com
Subject: Re: [PATCH] RISC-V: Enable HOTPLUG_PARALLEL for secondary CPUs
Date: Tue, 18 Nov 2025 08:13:56 +0000 [thread overview]
Message-ID: <176345363624.4032995.4350980055596642476.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905122512.71684-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 5 Sep 2025 17:55:12 +0530 you wrote:
> The core kernel already supports parallel bringup of secondary
> CPUs (aka HOTPLUG_PARALLEL). The x86 and MIPS architectures
> already use HOTPLUG_PARALLEL and ARM is also moving toward it.
>
> On RISC-V, there is no arch specific global data accessed in the
> RISC-V secondary CPU bringup path so enabling HOTPLUG_PARALLEL for
> RISC-V would only requires:
> 1) Providing RISC-V specific arch_cpuhp_kick_ap_alive()
> 2) Calling cpuhp_ap_sync_alive() from smp_callin()
>
> [...]
Here is the summary with links:
- RISC-V: Enable HOTPLUG_PARALLEL for secondary CPUs
https://git.kernel.org/riscv/c/dd2fbacc2ec5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, alex@ghiti.fr, atish.patra@linux.dev,
anup@brainfault.org, linux-kernel@vger.kernel.org,
ajones@ventanamicro.com
Subject: Re: [PATCH] RISC-V: Enable HOTPLUG_PARALLEL for secondary CPUs
Date: Tue, 18 Nov 2025 08:13:56 +0000 [thread overview]
Message-ID: <176345363624.4032995.4350980055596642476.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905122512.71684-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 5 Sep 2025 17:55:12 +0530 you wrote:
> The core kernel already supports parallel bringup of secondary
> CPUs (aka HOTPLUG_PARALLEL). The x86 and MIPS architectures
> already use HOTPLUG_PARALLEL and ARM is also moving toward it.
>
> On RISC-V, there is no arch specific global data accessed in the
> RISC-V secondary CPU bringup path so enabling HOTPLUG_PARALLEL for
> RISC-V would only requires:
> 1) Providing RISC-V specific arch_cpuhp_kick_ap_alive()
> 2) Calling cpuhp_ap_sync_alive() from smp_callin()
>
> [...]
Here is the summary with links:
- RISC-V: Enable HOTPLUG_PARALLEL for secondary CPUs
https://git.kernel.org/riscv/c/dd2fbacc2ec5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-11-18 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 12:25 [PATCH] RISC-V: Enable HOTPLUG_PARALLEL for secondary CPUs Anup Patel
2025-09-05 12:25 ` Anup Patel
2025-10-14 9:59 ` Anup Patel
2025-10-14 9:59 ` Anup Patel
2025-10-28 8:35 ` Atish Patra
2025-10-28 8:35 ` Atish Patra
2025-10-28 8:48 ` Anup Patel
2025-10-28 8:48 ` Anup Patel
2025-10-28 16:13 ` Atish Patra
2025-10-28 16:13 ` Atish Patra
2025-11-18 8:13 ` patchwork-bot+linux-riscv [this message]
2025-11-18 8:13 ` patchwork-bot+linux-riscv
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=176345363624.4032995.4350980055596642476.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atish.patra@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.