From: Vishal Chourasia <vishalc@linux.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: npiggin@gmail.com, rathc@linux.ibm.com, harshpb@linux.ibm.com,
amachhiw@linux.ibm.com, sbhat@linux.ibm.com,
gautam@linux.ibm.com, Vishal Chourasia <vishalc@linux.ibm.com>
Subject: [PATCH 0/2] ppc/spapr: refactor cpu hotplug related code
Date: Sat, 4 Jul 2026 16:06:12 +0530 [thread overview]
Message-ID: <20260704103617.632929-2-vishalc@linux.ibm.com> (raw)
In the past we have seen issues related to cpu hotplug which are
observed in certain rare case scenarios and not always easy to
investigate and debug [1]. Recently we merged a fix for specific cpu
hotplug scenario which observed along with kdump operations [2].
Additionally, spapr.c has grown to over 5000 lines which also contains
CPU hotplug related code which accounts for nearly 1000 of those lines
yet is conceptually self-contained and independent of the rest of the
machine model.
Extract the cpu hotplug related code into a new compilation unit,
spapr_cpu_hotplug.c, with a matching header.
Also, adding myself as reviewer for PPC KVM CPUs to help share the
review work.
[1] https://lore.kernel.org/all/0732de44-964c-4e0f-b4fd-dcc631ba70fa@linux.ibm.com/
[2] https://gitlab.com/qemu-project/qemu/-/commit/a1c2dfee4f0229bc59bd3ca20af8de1b5543973d
Vishal Chourasia (2):
ppc/spapr: refactor cpu hotplug code to separate file
MAINTAINERS: add self as reviewer for PPC KVM CPUs
MAINTAINERS | 4 +
hw/ppc/meson.build | 1 +
hw/ppc/spapr.c | 903 +-------------------------
hw/ppc/spapr_cpu_hotplug.c | 984 +++++++++++++++++++++++++++++
include/hw/ppc/spapr_cpu_hotplug.h | 74 +++
5 files changed, 1064 insertions(+), 902 deletions(-)
create mode 100644 hw/ppc/spapr_cpu_hotplug.c
create mode 100644 include/hw/ppc/spapr_cpu_hotplug.h
--
2.54.0
next reply other threads:[~2026-07-04 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 10:36 Vishal Chourasia [this message]
2026-07-04 10:36 ` [PATCH 1/2] ppc/spapr: refactor cpu hotplug code to separate file Vishal Chourasia
2026-07-07 13:49 ` Amit Machhiwal
2026-07-08 5:41 ` Harsh Prateek Bora
2026-07-04 10:36 ` [PATCH 2/2] MAINTAINERS: add self as reviewer for PPC KVM CPUs Vishal Chourasia
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=20260704103617.632929-2-vishalc@linux.ibm.com \
--to=vishalc@linux.ibm.com \
--cc=amachhiw@linux.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.ibm.com \
--cc=sbhat@linux.ibm.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.