From: Salil Mehta via <qemu-devel@nongnu.org> To: Gavin Shan <gshan@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "qemu-arm@nongnu.org" <qemu-arm@nongnu.org> Cc: "maz@kernel.org" <maz@kernel.org>, "jean-philippe@linaro.org" <jean-philippe@linaro.org>, Jonathan Cameron <jonathan.cameron@huawei.com>, "lpieralisi@kernel.org" <lpieralisi@kernel.org>, "peter.maydell@linaro.org" <peter.maydell@linaro.org>, "richard.henderson@linaro.org" <richard.henderson@linaro.org>, "imammedo@redhat.com" <imammedo@redhat.com>, "andrew.jones@linux.dev" <andrew.jones@linux.dev>, "david@redhat.com" <david@redhat.com>, "philmd@linaro.org" <philmd@linaro.org>, "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>, "mst@redhat.com" <mst@redhat.com>, "rafael@kernel.org" <rafael@kernel.org>, "borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>, "alex.bennee@linaro.org" <alex.bennee@linaro.org>, "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> Subject: RE: [PATCH RFC V2 18/37] arm/virt: Make ARM vCPU *present* status ACPI *persistent* Date: Mon, 16 Oct 2023 22:33:25 +0000 [thread overview] Message-ID: <d2479495683f4c1d9337914b451e2282@huawei.com> (raw) In-Reply-To: <550271cb-c415-f98e-afb4-d62df70c3ffb@redhat.com> Hi Gavin, > From: Gavin Shan <gshan@redhat.com> > Sent: Friday, September 29, 2023 12:18 AM > To: Salil Mehta <salil.mehta@huawei.com>; qemu-devel@nongnu.org; qemu-arm@nongnu.org > Cc: maz@kernel.org; jean-philippe@linaro.org; Jonathan Cameron > <jonathan.cameron@huawei.com>; lpieralisi@kernel.org; > peter.maydell@linaro.org; richard.henderson@linaro.org; > imammedo@redhat.com; andrew.jones@linux.dev; david@redhat.com; > philmd@linaro.org; eric.auger@redhat.com; will@kernel.org; ardb@kernel.org; > oliver.upton@linux.dev; pbonzini@redhat.com; mst@redhat.com; > rafael@kernel.org; borntraeger@linux.ibm.com; alex.bennee@linaro.org; > linux@armlinux.org.uk; darren@os.amperecomputing.com; > ilkka@os.amperecomputing.com; vishnu@os.amperecomputing.com; > karl.heubaum@oracle.com; miguel.luis@oracle.com; salil.mehta@opnsrc.net; > zhukeqian <zhukeqian1@huawei.com>; wangxiongfeng (C) > <wangxiongfeng2@huawei.com>; wangyanan (Y) <wangyanan55@huawei.com>; > jiakernel2@gmail.com; maobibo@loongson.cn; lixianglai@loongson.cn > Subject: Re: [PATCH RFC V2 18/37] arm/virt: Make ARM vCPU *present* status > ACPI *persistent* > > Hi Salil, > > On 9/26/23 20:04, Salil Mehta wrote: > > ARM arch does not allow CPUs presence to be changed [1] after kernel has booted. > > Hence, firmware/ACPI/Qemu must ensure persistent view of the vCPUs to the Guest > > kernel even when they are not present in the QoM i.e. are unplugged or are > > yet-to-be-plugged > > > > References: > > [1] Check comment 5 in the bugzilla entry > > Link: https://bugzilla.tianocore.org/show_bug.cgi?id=4481#c5 > > > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > --- > > cpus-common.c | 6 ++++++ > > hw/arm/virt.c | 7 +++++++ > > include/hw/core/cpu.h | 20 ++++++++++++++++++++ > > 3 files changed, 33 insertions(+) > > > > hmm, it's another CPU state. There are 4 CPU states, plus other 3 CPU states: > possible, present, enabled. Now we're having always-present state. Possible vCPU is not a QOM CPUState. Neither it gets represented through ACPI to the guest OS through _STA method. A device which in this case is a CPU can be in ENABLED state or can just be PRESENT but not ENABLED. All possible vCPUs get detected by guest OS by the mere presence of GICC Entry (Enabled/online-capable) in the ACPI MADT Table. A plugged vCPU will be 'present' in QOM and will be ACPI _STA.PRESENT as well. A un-plugged vCPU will be 'not-present' in QOM i.e. its CPUState object will be NULL. This is akin to x86 or any other architecture and we are not changing any of this at QOM level. What changes is the representation of un-plugged vCPU to Guest OS via ACPI _STA method. For ARM, we *fake* QOM un-plugged vCPU presence to the Guest OS through the ACPI _STA method. To detect this we check the bool 'acpi_persistent' part of CPUState. This has to be set explicitly by Architectures like ARM which do not support hot-plug. Hence, CPUs are in 'always present' state ACPI wise but cannot be used as they are ACPI disabled i.e. ACPI _STA.ENABLED=0. > I think > those CPU states can be squeezed into the previous present state. What we > need is to ensure all possible vCPUs are present from the beginning. All of this is unnecessary, really. Thanks Salil.
WARNING: multiple messages have this Message-ID (diff)
From: Salil Mehta <salil.mehta@huawei.com> To: Gavin Shan <gshan@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "qemu-arm@nongnu.org" <qemu-arm@nongnu.org> Cc: "maz@kernel.org" <maz@kernel.org>, "jean-philippe@linaro.org" <jean-philippe@linaro.org>, Jonathan Cameron <jonathan.cameron@huawei.com>, "lpieralisi@kernel.org" <lpieralisi@kernel.org>, "peter.maydell@linaro.org" <peter.maydell@linaro.org>, "richard.henderson@linaro.org" <richard.henderson@linaro.org>, "imammedo@redhat.com" <imammedo@redhat.com>, "andrew.jones@linux.dev" <andrew.jones@linux.dev>, "david@redhat.com" <david@redhat.com>, "philmd@linaro.org" <philmd@linaro.org>, "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>, "mst@redhat.com" <mst@redhat.com>, "rafael@kernel.org" <rafael@kernel.org>, "borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>, "alex.bennee@linaro.org" <alex.bennee@linaro.org>, "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> Subject: RE: [PATCH RFC V2 18/37] arm/virt: Make ARM vCPU *present* status ACPI *persistent* Date: Mon, 16 Oct 2023 22:33:25 +0000 [thread overview] Message-ID: <d2479495683f4c1d9337914b451e2282@huawei.com> (raw) Message-ID: <20231016223325.PraAJ2UVHwP2fdtobHDMU80DqQ2khBQCbaBvulJlBUs@z> (raw) In-Reply-To: <550271cb-c415-f98e-afb4-d62df70c3ffb@redhat.com> Hi Gavin, > From: Gavin Shan <gshan@redhat.com> > Sent: Friday, September 29, 2023 12:18 AM > To: Salil Mehta <salil.mehta@huawei.com>; qemu-devel@nongnu.org; qemu-arm@nongnu.org > Cc: maz@kernel.org; jean-philippe@linaro.org; Jonathan Cameron > <jonathan.cameron@huawei.com>; lpieralisi@kernel.org; > peter.maydell@linaro.org; richard.henderson@linaro.org; > imammedo@redhat.com; andrew.jones@linux.dev; david@redhat.com; > philmd@linaro.org; eric.auger@redhat.com; will@kernel.org; ardb@kernel.org; > oliver.upton@linux.dev; pbonzini@redhat.com; mst@redhat.com; > rafael@kernel.org; borntraeger@linux.ibm.com; alex.bennee@linaro.org; > linux@armlinux.org.uk; darren@os.amperecomputing.com; > ilkka@os.amperecomputing.com; vishnu@os.amperecomputing.com; > karl.heubaum@oracle.com; miguel.luis@oracle.com; salil.mehta@opnsrc.net; > zhukeqian <zhukeqian1@huawei.com>; wangxiongfeng (C) > <wangxiongfeng2@huawei.com>; wangyanan (Y) <wangyanan55@huawei.com>; > jiakernel2@gmail.com; maobibo@loongson.cn; lixianglai@loongson.cn > Subject: Re: [PATCH RFC V2 18/37] arm/virt: Make ARM vCPU *present* status > ACPI *persistent* > > Hi Salil, > > On 9/26/23 20:04, Salil Mehta wrote: > > ARM arch does not allow CPUs presence to be changed [1] after kernel has booted. > > Hence, firmware/ACPI/Qemu must ensure persistent view of the vCPUs to the Guest > > kernel even when they are not present in the QoM i.e. are unplugged or are > > yet-to-be-plugged > > > > References: > > [1] Check comment 5 in the bugzilla entry > > Link: https://bugzilla.tianocore.org/show_bug.cgi?id=4481#c5 > > > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > --- > > cpus-common.c | 6 ++++++ > > hw/arm/virt.c | 7 +++++++ > > include/hw/core/cpu.h | 20 ++++++++++++++++++++ > > 3 files changed, 33 insertions(+) > > > > hmm, it's another CPU state. There are 4 CPU states, plus other 3 CPU states: > possible, present, enabled. Now we're having always-present state. Possible vCPU is not a QOM CPUState. Neither it gets represented through ACPI to the guest OS through _STA method. A device which in this case is a CPU can be in ENABLED state or can just be PRESENT but not ENABLED. All possible vCPUs get detected by guest OS by the mere presence of GICC Entry (Enabled/online-capable) in the ACPI MADT Table. A plugged vCPU will be 'present' in QOM and will be ACPI _STA.PRESENT as well. A un-plugged vCPU will be 'not-present' in QOM i.e. its CPUState object will be NULL. This is akin to x86 or any other architecture and we are not changing any of this at QOM level. What changes is the representation of un-plugged vCPU to Guest OS via ACPI _STA method. For ARM, we *fake* QOM un-plugged vCPU presence to the Guest OS through the ACPI _STA method. To detect this we check the bool 'acpi_persistent' part of CPUState. This has to be set explicitly by Architectures like ARM which do not support hot-plug. Hence, CPUs are in 'always present' state ACPI wise but cannot be used as they are ACPI disabled i.e. ACPI _STA.ENABLED=0. > I think > those CPU states can be squeezed into the previous present state. What we > need is to ensure all possible vCPUs are present from the beginning. All of this is unnecessary, really. Thanks Salil.
next prev parent reply other threads:[~2023-10-16 22:34 UTC|newest] Thread overview: 146+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 10:03 [PATCH RFC V2 00/37] Support of Virtual CPU Hotplug for ARMv8 Arch Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 01/37] arm/virt, target/arm: Add new ARMCPU {socket, cluster, core, thread}-id property Salil Mehta via 2023-09-26 23:57 ` [PATCH RFC V2 01/37] arm/virt,target/arm: Add new ARMCPU {socket,cluster,core,thread}-id property Gavin Shan 2023-10-02 9:53 ` Salil Mehta via 2023-10-02 9:53 ` Salil Mehta 2023-10-03 5:05 ` Gavin Shan 2023-09-26 10:04 ` [PATCH RFC V2 02/37] cpus-common: Add common CPU utility for possible vCPUs Salil Mehta via 2023-09-27 3:54 ` Gavin Shan 2023-10-02 10:21 ` Salil Mehta via 2023-10-02 10:21 ` Salil Mehta 2023-10-03 5:34 ` Gavin Shan 2023-09-26 10:04 ` [PATCH RFC V2 03/37] hw/arm/virt: Move setting of common CPU properties in a function Salil Mehta via 2023-09-27 5:16 ` Gavin Shan 2023-10-02 10:24 ` Salil Mehta via 2023-10-02 10:24 ` Salil Mehta 2023-10-10 6:46 ` Shaoqin Huang 2023-10-10 9:47 ` Salil Mehta via 2023-10-10 9:47 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 04/37] arm/virt, target/arm: Machine init time change common to vCPU {cold|hot}-plug Salil Mehta via 2023-09-27 6:28 ` [PATCH RFC V2 04/37] arm/virt,target/arm: " Gavin Shan 2023-10-02 16:12 ` Salil Mehta via 2023-10-02 16:12 ` Salil Mehta 2024-01-16 15:59 ` Jonathan Cameron via 2023-09-27 6:30 ` Gavin Shan 2023-10-02 10:27 ` Salil Mehta via 2023-10-02 10:27 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 05/37] accel/kvm: Extract common KVM vCPU {creation, parking} code Salil Mehta via 2023-09-27 6:51 ` [PATCH RFC V2 05/37] accel/kvm: Extract common KVM vCPU {creation,parking} code Gavin Shan 2023-10-02 16:20 ` Salil Mehta via 2023-10-02 16:20 ` Salil Mehta 2023-10-03 5:39 ` Gavin Shan 2023-09-26 10:04 ` [PATCH RFC V2 06/37] arm/virt, kvm: Pre-create disabled possible vCPUs @machine init Salil Mehta via 2023-09-27 10:04 ` [PATCH RFC V2 06/37] arm/virt,kvm: " Gavin Shan 2023-10-02 16:39 ` Salil Mehta via 2023-10-02 16:39 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 07/37] arm/virt, gicv3: Changes to pre-size GIC with possible vcpus " Salil Mehta via 2023-09-28 0:14 ` Gavin Shan 2023-10-16 16:15 ` Salil Mehta via 2023-10-16 16:15 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 08/37] arm/virt: Init PMU at host for all possible vcpus Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 09/37] hw/acpi: Move CPU ctrl-dev MMIO region len macro to common header file Salil Mehta via 2023-09-28 0:19 ` Gavin Shan 2023-10-16 16:20 ` Salil Mehta via 2023-10-16 16:20 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 10/37] arm/acpi: Enable ACPI support for vcpu hotplug Salil Mehta via 2023-09-28 0:25 ` Gavin Shan 2023-10-16 21:23 ` Salil Mehta via 2023-10-16 21:23 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 11/37] hw/acpi: Add ACPI CPU hotplug init stub Salil Mehta via 2023-09-28 0:28 ` Gavin Shan 2023-10-16 21:27 ` Salil Mehta via 2023-10-16 21:27 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 12/37] hw/acpi: Use qemu_present_cpu() API in ACPI CPU hotplug init Salil Mehta via 2023-09-28 0:40 ` Gavin Shan 2023-10-16 21:41 ` Salil Mehta via 2023-10-16 21:41 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 13/37] hw/acpi: Init GED framework with cpu hotplug events Salil Mehta via 2023-09-28 0:56 ` Gavin Shan 2023-10-16 21:44 ` Salil Mehta via 2023-10-16 21:44 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 14/37] arm/virt: Add cpu hotplug events to GED during creation Salil Mehta via 2023-09-28 1:03 ` Gavin Shan 2023-10-16 21:46 ` Salil Mehta via 2023-10-16 21:46 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 15/37] arm/virt: Create GED dev before *disabled* CPU Objs are destroyed Salil Mehta via 2023-09-28 1:08 ` Gavin Shan 2023-10-16 21:54 ` Salil Mehta via 2023-10-16 21:54 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 16/37] hw/acpi: Update CPUs AML with cpu-(ctrl)dev change Salil Mehta via 2023-09-28 1:26 ` Gavin Shan 2023-10-16 21:57 ` Salil Mehta via 2023-10-16 21:57 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 17/37] arm/virt/acpi: Build CPUs AML with CPU Hotplug support Salil Mehta via 2023-09-28 1:36 ` Gavin Shan 2023-10-16 22:05 ` Salil Mehta via 2023-10-16 22:05 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 18/37] arm/virt: Make ARM vCPU *present* status ACPI *persistent* Salil Mehta via 2023-09-28 23:18 ` Gavin Shan 2023-10-16 22:33 ` Salil Mehta via [this message] 2023-10-16 22:33 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 19/37] hw/acpi: ACPI/AML Changes to reflect the correct _STA.{PRES, ENA} Bits to Guest Salil Mehta via 2023-09-28 23:33 ` [PATCH RFC V2 19/37] hw/acpi: ACPI/AML Changes to reflect the correct _STA.{PRES,ENA} " Gavin Shan 2023-10-16 22:59 ` Salil Mehta via 2023-10-16 22:59 ` Salil Mehta 2024-01-17 21:46 ` [PATCH RFC V2 19/37] hw/acpi: ACPI/AML Changes to reflect the correct _STA.{PRES, ENA} " Jonathan Cameron via 2023-09-26 10:04 ` [PATCH RFC V2 20/37] hw/acpi: Update GED _EVT method AML with cpu scan Salil Mehta via 2023-09-28 23:35 ` Gavin Shan 2023-10-16 23:01 ` Salil Mehta via 2023-10-16 23:01 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 21/37] hw/arm: MADT Tbl change to size the guest with possible vCPUs Salil Mehta via 2023-09-28 23:43 ` Gavin Shan 2023-10-16 23:15 ` Salil Mehta via 2023-10-16 23:15 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 22/37] hw/acpi: Make _MAT method optional Salil Mehta via 2023-09-28 23:50 ` Gavin Shan 2023-10-16 23:17 ` Salil Mehta via 2023-10-16 23:17 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 23/37] arm/virt: Release objects for *disabled* possible vCPUs after init Salil Mehta via 2023-09-28 23:57 ` Gavin Shan 2023-10-16 23:28 ` Salil Mehta via 2023-10-16 23:28 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 24/37] hw/acpi: Update ACPI GED framework to support vCPU Hotplug Salil Mehta via 2023-09-26 11:02 ` Michael S. Tsirkin 2023-09-26 11:37 ` Salil Mehta via 2023-09-26 12:00 ` Michael S. Tsirkin 2023-09-26 12:27 ` Salil Mehta via 2023-09-26 13:02 ` lixianglai 2023-09-26 10:04 ` [PATCH RFC V2 25/37] arm/virt: Add/update basic hot-(un)plug framework Salil Mehta via 2023-09-29 0:20 ` Gavin Shan 2023-10-16 23:40 ` Salil Mehta via 2023-10-16 23:40 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 26/37] arm/virt: Changes to (un)wire GICC<->vCPU IRQs during hot-(un)plug Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 27/37] hw/arm, gicv3: Changes to update GIC with vCPU hot-plug notification Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 28/37] hw/intc/arm-gicv3*: Changes required to (re)init the vCPU register info Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 29/37] arm/virt: Update the guest(via GED) about CPU hot-(un)plug events Salil Mehta via 2023-09-29 0:30 ` Gavin Shan 2023-10-16 23:48 ` Salil Mehta via 2023-10-16 23:48 ` Salil Mehta 2023-09-26 10:04 ` [PATCH RFC V2 30/37] hw/arm: Changes required for reset and to support next boot Salil Mehta via 2023-09-26 10:04 ` [PATCH RFC V2 31/37] physmem, gdbstub: Common helping funcs/changes to *unrealize* vCPU Salil Mehta via 2023-10-03 6:33 ` [PATCH RFC V2 31/37] physmem,gdbstub: " Philippe Mathieu-Daudé 2023-10-03 10:22 ` Salil Mehta via 2023-10-03 10:22 ` Salil Mehta 2023-10-04 9:17 ` Salil Mehta via 2023-10-04 9:17 ` Salil Mehta 2023-09-26 10:36 ` [PATCH RFC V2 32/37] target/arm: Add support of *unrealize* ARMCPU during vCPU Hot-unplug Salil Mehta via 2023-09-26 10:36 ` [PATCH RFC V2 33/37] target/arm/kvm: Write CPU state back to KVM on reset Salil Mehta via 2023-09-26 10:36 ` [PATCH RFC V2 34/37] target/arm/kvm, tcg: Register/Handle SMCCC hypercall exits to VMM/Qemu Salil Mehta via 2023-09-29 4:15 ` [PATCH RFC V2 34/37] target/arm/kvm,tcg: " Gavin Shan 2023-10-17 0:03 ` Salil Mehta via 2023-10-17 0:03 ` Salil Mehta 2023-09-26 10:36 ` [PATCH RFC V2 35/37] hw/arm: Support hotplug capability check using _OSC method Salil Mehta via 2023-09-29 4:23 ` Gavin Shan 2023-10-17 0:13 ` Salil Mehta via 2023-10-17 0:13 ` Salil Mehta 2023-09-26 10:36 ` [PATCH RFC V2 36/37] tcg/mttcg: enable threads to unregister in tcg_ctxs[] Salil Mehta via 2023-09-26 10:36 ` [PATCH RFC V2 37/37] hw/arm/virt: Expose cold-booted CPUs as MADT GICC Enabled Salil Mehta via 2023-10-11 10:23 ` [PATCH RFC V2 00/37] Support of Virtual CPU Hotplug for ARMv8 Arch Vishnu Pajjuri 2023-10-11 10:32 ` Salil Mehta via 2023-10-11 10:32 ` Salil Mehta 2023-10-11 11:08 ` Vishnu Pajjuri 2023-10-11 20:15 ` Salil Mehta 2023-10-12 17:02 ` Miguel Luis 2023-10-12 17:54 ` Salil Mehta via 2023-10-12 17:54 ` Salil Mehta 2023-10-13 10:43 ` Miguel Luis
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=d2479495683f4c1d9337914b451e2282@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=eric.auger@redhat.com \ --cc=gshan@redhat.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=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=oliver.upton@linux.dev \ --cc=pbonzini@redhat.com \ --cc=peter.maydell@linaro.org \ --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=vishnu@os.amperecomputing.com \ --cc=wangxiongfeng2@huawei.com \ --cc=wangyanan55@huawei.com \ --cc=will@kernel.org \ --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: linkBe 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).