From: Salil Mehta via <qemu-devel@nongnu.org>
To: Gavin Shan <gshan@redhat.com>,
Gustavo Romero <gustavo.romero@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Igor Mammedov <imammedo@redhat.com>,
"Eric Auger" <eauger@redhat.com>
Cc: "maz@kernel.org" <maz@kernel.org>,
"jean-philippe@linaro.org" <jean-philippe@linaro.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"andrew.jones@linux.dev" <andrew.jones@linux.dev>,
"david@redhat.com" <david@redhat.com>,
"philmd@linaro.org" <philmd@linaro.org>,
"peterx@redhat.com" <peterx@redhat.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"will@kernel.org" <will@kernel.org>,
"ardb@kernel.org" <ardb@kernel.org>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>,
"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"harshpb@linux.ibm.com" <harshpb@linux.ibm.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"darren@os.amperecomputing.com" <darren@os.amperecomputing.com>,
"ilkka@os.amperecomputing.com" <ilkka@os.amperecomputing.com>,
"vishnu@os.amperecomputing.com" <vishnu@os.amperecomputing.com>,
"karl.heubaum@oracle.com" <karl.heubaum@oracle.com>,
"miguel.luis@oracle.com" <miguel.luis@oracle.com>,
"salil.mehta@opnsrc.net" <salil.mehta@opnsrc.net>,
zhukeqian <zhukeqian1@huawei.com>,
"wangxiongfeng (C)" <wangxiongfeng2@huawei.com>,
"wangyanan (Y)" <wangyanan55@huawei.com>,
"jiakernel2@gmail.com" <jiakernel2@gmail.com>,
"maobibo@loongson.cn" <maobibo@loongson.cn>,
"lixianglai@loongson.cn" <lixianglai@loongson.cn>,
"shahuang@redhat.com" <shahuang@redhat.com>,
"zhao1.liu@intel.com" <zhao1.liu@intel.com>,
Linuxarm <linuxarm@huawei.com>
Subject: RE: [PATCH RFC V5 00/30] Support of Virtual CPU Hotplug for ARMv8 Arch
Date: Thu, 22 May 2025 13:24:33 +0000 [thread overview]
Message-ID: <67025b22e4864caaa5b3dd19eb6d95ac@huawei.com> (raw)
In-Reply-To: <0d1208fa-9fca-4b4b-bad0-8b596d5102fb@redhat.com>
HI Gavin,
> -----Original Message-----
> From: Gavin Shan <gshan@redhat.com>
> Sent: Thursday, May 22, 2025 12:54 AM
> To: Gustavo Romero <gustavo.romero@linaro.org>; Salil Mehta
> <salil.mehta@huawei.com>; qemu-devel@nongnu.org; qemu-
> arm@nongnu.org; mst@redhat.com; Jonathan Cameron
> <jonathan.cameron@huawei.com>; Igor Mammedov
> <imammedo@redhat.com>; Eric Auger <eauger@redhat.com>
[..]
>
> Hi Gustavo and Salil,
>
> On 5/22/25 1:06 AM, Gustavo Romero wrote:
> > Hi Salil, Gavin, and folks,
> >
> > On 5/20/25 21:22, Gavin Shan wrote:
> >> Hi Salil,
> >>
> >> A kindly ping. vCPU hotplug is an important feature and You has put
> >> so much energies and amazing efforts to enable the feature from QEMU
> >> side, but it seems it has been stuck recently. I received many
> >> messages from Redhat internal and external to ask if vCPU hotplug has
> >> been supported on aarch64 in the past. So I'm heading up to check if
> >> you have bandwidth to continue the effort, any kinds of helps are
> needed, especially from me.
> >
> > You can count on me as well, Salil. I'm definitely in a better
> > position now to help you with the technical review of the series, and
> > I can also weigh in to help resolve any remaining issues so we can
> > finally get it merged. Don't give up! :)
> >
> > My suggestion: go ahead and post what you have now. Just highlight the
> > main points of objection raised in the last review that still need to be
> addressed.
> >
>
> Thanks for your response and to offer helps. Another suggestion I have in
> mind:
> if there is uncertainty regarding the design, it would be nice to post a specific
> thread for discussion until it's cleared prior to diving into code. After the
> design is acknowledged by maintainers, our life will be much easier. The
> point is to get enough attentions and feedbacks from the maintainers until
> it's acknowledged.
The changes were mainly to address Igor's concern which have to be respected
as he is a maintainer of vCPU hotplug on x86. And to ensure that his time is
utilized best as he is understandably a busy person, we all thought to share the
updated code to him.
There are design changes but these are not which makes the design completely
different as we have to respect the interfaces which have been frozen with the
kernel and hence the handshakes ideally should remain same. Also, as part of
the review, I've had some internal discussions related to these changes in Huawei
with Jonathan and he was in agreement with the approach. But of course, end
acknowledgement has to come from Igor. 😊
> >> Besides, I'm reluctantly to ask if you're fine for some body else to
> >> pick this up and continue the effort. The credits for all the
> >> contributors (Keqian Zhu, Jean Philippe, Miguel Luis and you) will be kept.
> >
> > I don’t want to speak for others, but in my view, Salil should ideally
> > be the one to complete this work — as you said, he’s already invested
> > a great deal of time and energy into it.
> >
> > It would be tremendously helpful if maintainers could support Salil in
> > bringing this to completion, kindly guiding him toward the path to get it
> finalized.
> >
>
> Absolutely, Salil knows all the details, especially the historic steps how vCPU
> hotplug has been evolving. I truly hope Salil is able to continue the efforts
> until the feature lands upstream!
Sorry, for any hassle caused due to my absences. Yes, I'm back to work and will
try to expedite the changes and ping you soon for your help.
Thanks for understanding.
Best regards
Salil.
>
> Thanks,
> Gavin
>
next prev parent reply other threads:[~2025-05-22 13:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:59 [PATCH RFC V5 00/30] Support of Virtual CPU Hotplug for ARMv8 Arch Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 01/30] arm/virt, target/arm: Add new ARMCPU {socket, cluster, core, thread}-id property Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 02/30] hw/arm/virt: Disable vCPU hotplug for *unsupported* Accel or GIC Type Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 03/30] hw/arm/virt: Move setting of common vCPU properties in a function Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 04/30] arm/virt, target/arm: Machine init time change common to vCPU {cold|hot}-plug Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 05/30] arm/virt, kvm: Pre-create KVM vCPUs for all unplugged QOM vCPUs @machine init Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 06/30] arm/virt, gicv3: Changes to pre-size GIC with possible " Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 07/30] arm/virt, gicv3: Introduce GICv3 CPU Interface *accessibility* flag and checks Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 08/30] hw/intc/arm-gicv3*: Changes required to (re)init the GICv3 vCPU Interface Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 09/30] arm/acpi: Enable ACPI support for vCPU hotplug Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 10/30] arm/virt: Enhance GED framework to handle vCPU hotplug events Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 11/30] arm/virt: Init PMU at host for all possible vCPUs Salil Mehta via
2025-09-02 13:26 ` Philippe Mathieu-Daudé
2024-10-15 9:59 ` [PATCH RFC V5 12/30] arm/virt: Release objects for *disabled* possible vCPUs after init Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 13/30] arm/virt/acpi: Update ACPI DSDT Tbl to include CPUs AML with hotplug support Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 14/30] hw/acpi: Make _MAT method optional Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 15/30] hw/arm/acpi: MADT Tbl change to size the guest with possible vCPUs Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 16/30] target/arm: Force ARM vCPU *present* status ACPI *persistent* Salil Mehta via
2024-10-15 9:59 ` [PATCH RFC V5 17/30] arm/virt: Add/update basic hot-(un)plug framework Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 18/30] arm/virt: Changes to (un)wire GICC<->vCPU IRQs during hot-(un)plug Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 19/30] hw/arm, gicv3: Changes to notify GICv3 CPU state with vCPU hot-(un)plug event Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 20/30] hw/arm: Changes required for reset and to support next boot Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 21/30] arm/virt: Update the guest(via GED) about vCPU hot-(un)plug events Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 22/30] target/arm/cpu: Check if hotplugged ARM vCPU's FEAT match existing Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 23/30] tcg: Update tcg_register_thread() leg to handle region alloc for hotplugged vCPU Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 24/30] target/arm: Add support to *unrealize* ARMCPU during vCPU Hot-unplug Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 25/30] tcg/mttcg: Introduce MTTCG thread unregistration leg Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 26/30] hw/intc/arm_gicv3_common: Add GICv3CPUState 'accessible' flag migration handling Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 27/30] target/arm/kvm, tcg: Handle SMCCC hypercall exits in VMM during PSCI_CPU_{ON, OFF} Salil Mehta via
2024-10-15 10:00 ` [PATCH RFC V5 28/30] target/arm/kvm: Write vCPU's state back to KVM on cold-reset Salil Mehta via
2024-10-15 10:16 ` [PATCH RFC V5 29/30] hw/intc/arm_gicv3_kvm: Pause all vCPU to ensure locking in KVM of resetting vCPU Salil Mehta via
2024-10-15 10:18 ` [PATCH RFC V5 30/30] hw/arm/virt: Expose cold-booted vCPUs as MADT GICC *Enabled* Salil Mehta via
2024-10-16 14:09 ` [PATCH RFC V5 00/30] Support of Virtual CPU Hotplug for ARMv8 Arch Miguel Luis
2024-10-21 20:49 ` Salil Mehta
2024-10-17 7:07 ` Gavin Shan
2024-10-21 20:47 ` Salil Mehta
2025-05-21 0:22 ` Gavin Shan
2025-05-21 15:06 ` Gustavo Romero
2025-05-21 23:54 ` Gavin Shan
2025-05-22 13:24 ` Salil Mehta via [this message]
2025-05-22 12:40 ` Igor Mammedov
2025-05-22 14:16 ` Salil Mehta via
2025-05-22 13:05 ` Salil Mehta via
2025-05-22 12:44 ` Salil Mehta via
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=67025b22e4864caaa5b3dd19eb6d95ac@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=alex.bennee@linaro.org \
--cc=andrew.jones@linux.dev \
--cc=ardb@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=darren@os.amperecomputing.com \
--cc=david@redhat.com \
--cc=eauger@redhat.com \
--cc=eric.auger@redhat.com \
--cc=gshan@redhat.com \
--cc=gustavo.romero@linaro.org \
--cc=harshpb@linux.ibm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=imammedo@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=jiakernel2@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=karl.heubaum@oracle.com \
--cc=linux@armlinux.org.uk \
--cc=linuxarm@huawei.com \
--cc=lixianglai@loongson.cn \
--cc=lpieralisi@kernel.org \
--cc=maobibo@loongson.cn \
--cc=maz@kernel.org \
--cc=miguel.luis@oracle.com \
--cc=mst@redhat.com \
--cc=npiggin@gmail.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=rafael@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=salil.mehta@huawei.com \
--cc=salil.mehta@opnsrc.net \
--cc=shahuang@redhat.com \
--cc=vishnu@os.amperecomputing.com \
--cc=wangxiongfeng2@huawei.com \
--cc=wangyanan55@huawei.com \
--cc=will@kernel.org \
--cc=zhao1.liu@intel.com \
--cc=zhukeqian1@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;
as well as URLs for NNTP newsgroup(s).