From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Michal Orzel" <michal.orzel@amd.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Timothy Pearson" <tpearson@raptorengineering.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Juergen Gross" <jgross@suse.com>
Subject: Re: [PATCH v5 0/5] Implement CPU hotplug on Arm
Date: Tue, 3 Feb 2026 16:35:07 +0000 [thread overview]
Message-ID: <51B975F5-C0EB-43AE-97FD-CC937DBC593B@arm.com> (raw)
In-Reply-To: <cover.1768293759.git.mykyta_poturai@epam.com>
Hi Mykyta,
> On 13 Jan 2026, at 09:45, Mykyta Poturai <Mykyta_Poturai@epam.com> wrote:
>
> This series implements support for CPU hotplug/unplug on Arm. To achieve this,
> several things need to be done:
>
> 1. XEN_SYSCTL_CPU_HOTPLUG_* calls implemented on Arm64.
> 2. Enabled building of xen-hptool.
> 3. Migration of irqs from dying CPUs implemented.
>
> Tested on QEMU.
Do you have a way to validate this on real hardware ?
Doing hotplug/unplug might have side effects (caches, coherency, interrupts, etc) that
I would not be completely confident to have validated by only testing this in qemu.
Could you explain how you validated this (what kind of tests you did).
I would be interested to know how the system behave in the following cases:
- stopping cpu with guests pinned to specific cores
- stopping a cpu with a guest pinned and only running on that one
- checking with passthrough devices (for irq balancing)
Then a general remark i have is that most of this code (if not all) is always in Xen
even if CONFIG_CPU_HOTPLUG is not activated in xen config which will probably
generate some dead code. Could we protect some of the code not used when
HOTPLUG is not activated with if (is_enabled(CONFIG_CPU_HOTPLUG)) or
equivalent forms ?
Cheers
Bertrand
>
> v4->v5:
> * drop merged patches
> * combine "smp: Move cpu_up/down helpers to common code" with
> "arm/sysctl: Implement cpu hotplug ops"
> * see individual patches
>
> v3->v4:
> * add irq migration patches
> * see individual patches
>
> v2->v3:
> * add docs
>
> v1->v2:
> * see individual patches
>
> Mykyta Poturai (5):
> arm/irq: Keep track of irq affinities
> arm/irq: Migrate IRQs during CPU up/down operations
> arm/sysctl: Implement cpu hotplug ops
> tools: Allow building xen-hptool without CONFIG_MIGRATE
> docs: Document CPU hotplug
>
> SUPPORT.md | 1 +
> docs/misc/cpu-hotplug.txt | 50 +++++++++++++++++++++++++
> tools/libs/guest/Makefile.common | 2 +-
> tools/misc/Makefile | 2 +-
> xen/arch/arm/Kconfig | 1 +
> xen/arch/arm/gic-vgic.c | 2 +
> xen/arch/arm/include/asm/irq.h | 2 +
> xen/arch/arm/irq.c | 63 +++++++++++++++++++++++++++++++-
> xen/arch/arm/smp.c | 9 +++++
> xen/arch/arm/smpboot.c | 6 +++
> xen/arch/arm/vgic.c | 14 ++++++-
> xen/arch/ppc/stubs.c | 4 ++
> xen/arch/riscv/stubs.c | 5 +++
> xen/arch/x86/Kconfig | 1 +
> xen/arch/x86/include/asm/smp.h | 3 --
> xen/arch/x86/smp.c | 33 ++---------------
> xen/arch/x86/sysctl.c | 12 ++----
> xen/common/Kconfig | 3 ++
> xen/common/smp.c | 34 +++++++++++++++++
> xen/common/sysctl.c | 45 +++++++++++++++++++++++
> xen/include/xen/smp.h | 4 ++
> 21 files changed, 248 insertions(+), 48 deletions(-)
> create mode 100644 docs/misc/cpu-hotplug.txt
>
> --
> 2.51.2
next prev parent reply other threads:[~2026-02-03 16:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 8:45 [PATCH v5 0/5] Implement CPU hotplug on Arm Mykyta Poturai
2026-01-13 8:45 ` [PATCH v5 1/5] arm/irq: Keep track of irq affinities Mykyta Poturai
2026-02-03 16:51 ` Bertrand Marquis
2026-01-13 8:45 ` [PATCH v5 2/5] arm/irq: Migrate IRQs during CPU up/down operations Mykyta Poturai
2026-02-04 14:20 ` Bertrand Marquis
2026-02-05 13:23 ` Mykyta Poturai
2026-02-05 14:07 ` Bertrand Marquis
2026-03-03 23:55 ` Stefano Stabellini
2026-01-13 8:45 ` [PATCH v5 3/5] arm/sysctl: Implement cpu hotplug ops Mykyta Poturai
2026-01-14 9:49 ` Jan Beulich
2026-02-03 10:30 ` Mykyta Poturai
2026-02-03 11:20 ` Jan Beulich
2026-01-13 8:45 ` [PATCH v5 4/5] tools: Allow building xen-hptool without CONFIG_MIGRATE Mykyta Poturai
2026-01-13 9:32 ` Jan Beulich
2026-01-13 8:45 ` [PATCH v5 5/5] docs: Document CPU hotplug Mykyta Poturai
2026-02-03 16:35 ` Bertrand Marquis [this message]
2026-02-04 12:58 ` [PATCH v5 0/5] Implement CPU hotplug on Arm Mykyta Poturai
2026-02-04 13:02 ` Bertrand Marquis
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=51B975F5-C0EB-43AE-97FD-CC937DBC593B@arm.com \
--to=bertrand.marquis@arm.com \
--cc=Mykyta_Poturai@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=connojdavis@gmail.com \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tpearson@raptorengineering.com \
--cc=xen-devel@lists.xenproject.org \
/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.