From: Thomas Gleixner <tglx@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
Michael Kelley <mhklinux@outlook.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"pjw@kernel.org" <pjw@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"kees@kernel.org" <kees@kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"linusw@kernel.org" <linusw@kernel.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"david.kaplan@amd.com" <david.kaplan@amd.com>,
"lukas.bulwahn@redhat.com" <lukas.bulwahn@redhat.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"maz@kernel.org" <maz@kernel.org>,
"timothy.hayes@arm.com" <timothy.hayes@arm.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"thuth@redhat.com" <thuth@redhat.com>,
"oupton@kernel.org" <oupton@kernel.org>,
"yeoreum.yun@arm.com" <yeoreum.yun@arm.com>,
"miko.lenczewski@arm.com" <miko.lenczewski@arm.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"kevin.brodsky@arm.com" <kevin.brodsky@arm.com>,
"james.clark@linaro.org" <james.clark@linaro.org>,
"tabba@google.com" <tabba@google.com>,
"mrigendra.chaubey@gmail.com" <mrigendra.chaubey@gmail.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH RFC 3/3] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs
Date: Thu, 18 Jun 2026 17:53:41 +0200 [thread overview]
Message-ID: <874iizdeuy.ffs@fw13> (raw)
In-Reply-To: <4588efb4-e757-4ca7-9197-025b67ca9ef6@huawei.com>
On Mon, Jun 15 2026 at 17:57, Jinjie Ruan wrote:
> On 6/12/2026 11:45 PM, Michael Kelley wrote:
>
> - Default (no patch): Slowest HVC64 handling (126 μs), highest WFx count
> (85k), and most total VM‑exits.
>
> - cpuhp.parallel=1: HVC64 latency improved to 78 μs (close to
> cpuhp.parallel=0), but IRQ exits increased dramatically (12.9k, 2.7×
> that of `cpuhp.parallel=0`), accounting for 95% of event time and
> becoming the new bottleneck.
>
> - cpuhp.parallel=0: Fastest HVC64 (69 μs), lowest IRQ exits (4.8k), and
> lowest total samples, delivering the best overall boot performance.
>
> Therefor, `cpuhp.parallel=1` reduces HVC cost but suffers from a massive
> increase in IRQ exits, while `cpuhp.parallel=0` avoids this interrupt
> storm and therefore performs best in a KVM guest.
What's the cause for having this massive interrupt exit rate in parallel
mode? Just because parallel does not give a useful explanation.
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
Michael Kelley <mhklinux@outlook.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"pjw@kernel.org" <pjw@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"kees@kernel.org" <kees@kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"linusw@kernel.org" <linusw@kernel.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"david.kaplan@amd.com" <david.kaplan@amd.com>,
"lukas.bulwahn@redhat.com" <lukas.bulwahn@redhat.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"maz@kernel.org" <maz@kernel.org>,
"timothy.hayes@arm.com" <timothy.hayes@arm.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"thuth@redhat.com" <thuth@redhat.com>,
"oupton@kernel.org" <oupton@kernel.org>,
"yeoreum.yun@arm.com" <yeoreum.yun@arm.com>,
"miko.lenczewski@arm.com" <miko.lenczewski@arm.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"kevin.brodsky@arm.com" <kevin.brodsky@arm.com>,
"james.clark@linaro.org" <james.clark@linaro.org>,
"tabba@google.com" <tabba@google.com>,
"mrigendra.chaubey@gmail.com" <mrigendra.chaubey@gmail.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH RFC 3/3] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs
Date: Thu, 18 Jun 2026 17:53:41 +0200 [thread overview]
Message-ID: <874iizdeuy.ffs@fw13> (raw)
In-Reply-To: <4588efb4-e757-4ca7-9197-025b67ca9ef6@huawei.com>
On Mon, Jun 15 2026 at 17:57, Jinjie Ruan wrote:
> On 6/12/2026 11:45 PM, Michael Kelley wrote:
>
> - Default (no patch): Slowest HVC64 handling (126 μs), highest WFx count
> (85k), and most total VM‑exits.
>
> - cpuhp.parallel=1: HVC64 latency improved to 78 μs (close to
> cpuhp.parallel=0), but IRQ exits increased dramatically (12.9k, 2.7×
> that of `cpuhp.parallel=0`), accounting for 95% of event time and
> becoming the new bottleneck.
>
> - cpuhp.parallel=0: Fastest HVC64 (69 μs), lowest IRQ exits (4.8k), and
> lowest total samples, delivering the best overall boot performance.
>
> Therefor, `cpuhp.parallel=1` reduces HVC cost but suffers from a massive
> increase in IRQ exits, while `cpuhp.parallel=0` avoids this interrupt
> storm and therefore performs best in a KVM guest.
What's the cause for having this massive interrupt exit rate in parallel
mode? Just because parallel does not give a useful explanation.
Thanks,
tglx
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-06-18 15:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 13:38 [PATCH RFC 0/3] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs Jinjie Ruan
2026-06-11 13:38 ` Jinjie Ruan
2026-06-11 13:38 ` [PATCH RFC 1/3] cpu/hotplug: Introduce CONFIG_PARALLEL_SMT_PRIMARY_FIRST Jinjie Ruan
2026-06-11 13:38 ` Jinjie Ruan
2026-06-18 15:17 ` Thomas Gleixner
2026-06-18 15:17 ` Thomas Gleixner
2026-06-11 13:38 ` [PATCH RFC 2/3] arm64: smp: Pass CPU ID to update_cpu_boot_status() Jinjie Ruan
2026-06-11 13:38 ` Jinjie Ruan
2026-06-11 13:38 ` [PATCH RFC 3/3] arm64: Add HOTPLUG_PARALLEL support for secondary CPUs Jinjie Ruan
2026-06-11 13:38 ` Jinjie Ruan
2026-06-12 15:45 ` Michael Kelley
2026-06-12 15:45 ` Michael Kelley
2026-06-15 8:51 ` Jinjie Ruan
2026-06-15 8:51 ` Jinjie Ruan
2026-06-18 12:21 ` Will Deacon
2026-06-18 12:21 ` Will Deacon
2026-06-15 9:57 ` Jinjie Ruan
2026-06-15 9:57 ` Jinjie Ruan
2026-06-18 15:53 ` Thomas Gleixner [this message]
2026-06-18 15:53 ` Thomas Gleixner
2026-06-18 15:49 ` Thomas Gleixner
2026-06-18 15:49 ` Thomas Gleixner
2026-06-12 15:51 ` [PATCH RFC 0/3] " Michael Kelley
2026-06-12 15:51 ` Michael Kelley
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=874iizdeuy.ffs@fw13 \
--to=tglx@kernel.org \
--cc=alex@ghiti.fr \
--cc=anshuman.khandual@arm.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=hpa@zytor.com \
--cc=james.clark@linaro.org \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.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=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=maz@kernel.org \
--cc=mhklinux@outlook.com \
--cc=miko.lenczewski@arm.com \
--cc=mingo@redhat.com \
--cc=mrigendra.chaubey@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=oupton@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=tabba@google.com \
--cc=thuth@redhat.com \
--cc=timothy.hayes@arm.com \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--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 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.