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 07/37] arm/virt, gicv3: Changes to pre-size GIC with possible vcpus @machine init Date: Mon, 16 Oct 2023 16:15:57 +0000 [thread overview] Message-ID: <6530351c0fa94f68ab4be05198434794@huawei.com> (raw) In-Reply-To: <ae71fa00-fcc5-ef34-ef94-b3fd37622582@redhat.com> Hi Gavin, > From: Gavin Shan <gshan@redhat.com> > Sent: Thursday, September 28, 2023 1:14 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 07/37] arm/virt,gicv3: Changes to pre-size GIC > with possible vcpus @machine init > > Hi Salil, > > On 9/26/23 20:04, Salil Mehta wrote: > > GIC needs to be pre-sized with possible vcpus at the initialization time. This > > is necessary because Memory regions and resources associated with GICC/GICR > > etc cannot be changed (add/del/modified) after VM has inited. Also, GIC_TYPER > > needs to be initialized with mp_affinity and cpu interface number association. > > This cannot be changed after GIC has initialized. > > > > Once all the cpu interfaces of the GIC has been inited it needs to be ensured > ^^^^^^ > initialized, Sure. Thanks! > > that any updates to the GICC during reset only takes place for the present > > ^^^^^^^^^^^ > the > enabled Yes. I will fix the sentence. Thanks Salil. > > vcpus and not the disabled ones. Therefore, proper checks are required at > > various places. > > > > Co-developed-by: Salil Mehta <salil.mehta@huawei.com> > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > Co-developed-by: Keqian Zhu <zhukeqian1@huawei.com> > > Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com> > > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org> > > [changed the comment in arm_gicv3_icc_reset] > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > --- > > hw/arm/virt.c | 15 ++++++++------- > > hw/intc/arm_gicv3_common.c | 7 +++++-- > > hw/intc/arm_gicv3_cpuif.c | 8 ++++++++ > > hw/intc/arm_gicv3_kvm.c | 34 +++++++++++++++++++++++++++++++--- > > include/hw/arm/virt.h | 2 +- > > 5 files changed, 53 insertions(+), 13 deletions(-) > > > > I guess the subject can be improved to something like below because it's the preparatory > work to support vCPU hotplug (notifier) in the subsequent patches. In this patch, most > of the code changes is related to vCPU state, ms->smp_pros.max_cpus and the CPU interface > instances associated to GICv3 controller. I general, any commit-log should state 'why' and not 'what' the patch is doing. > > arm/virt,gicv3: Prepare for vCPU hotplug by checking GICv3CPUState states Subject is a summary of what patch intends to do. It is pre-sizing the GIC in QOM and in KVM as well i.e. VGIC. Please check the KVMForum 2023 slides page-6 for more details. > We already had wrappers to check vCPU's states. I'm wandering if we need another set > of wrappers for GICv3 for several facts: (a) In this patch, we're actually concerned > by GICv3CPUState's states, disabled or enabled. vCPU states have been classified to > possible, present, and enabled. Their states aren't matching strictly. (b) With GICv3 > own wrappers, the code can be detached from vCPU in high level. Please evaluate it's > worthy to have GICv3 own wrappers and we can have the folowing wrappers if > want. It will open up the pandoras box if we tickle with GIC as we cannot play with VGIC states in the KVM due to ARM architecture constraints. These states are always part of always-on power domain. In case, we decide to model the QEMU GIC to relax later aspect we would still need to re-size the VGIC at KVM and still expose all of the GIC CPU Interfaces to the Guest OS at boot time. Hence, those GICV3CPUState specific APIs do not add much value to logic to be frank. Plus, once we have these states formally described as part of the QOM then we need to explicitly handle cases, for example, what will these new states mean in terms of Live/Pseudo Migration? Thanks Salil. [...] > > diff --git a/hw/intc/arm_gicv3_common.c b/hw/intc/arm_gicv3_common.c > > index 2ebf880ead..ebd99af610 100644 > > --- a/hw/intc/arm_gicv3_common.c > > +++ b/hw/intc/arm_gicv3_common.c > > @@ -392,10 +392,13 @@ static void arm_gicv3_common_realize(DeviceState > *dev, Error **errp) > > s->cpu = g_new0(GICv3CPUState, s->num_cpu); > > > > for (i = 0; i < s->num_cpu; i++) { > > - CPUState *cpu = qemu_get_cpu(i); > > + CPUState *cpu = qemu_get_possible_cpu(i); > > uint64_t cpu_affid; > > > > - s->cpu[i].cpu = cpu; > > + if (qemu_enabled_cpu(cpu)) { > > + s->cpu[i].cpu = cpu; > > + } > > + > > s->cpu[i].gic = s; > > /* Store GICv3CPUState in CPUARMState gicv3state pointer */ > > gicv3_set_gicv3state(cpu, &s->cpu[i]); > > I don't think gicv3_set_gicv3state() isn't needed for !qemu_enabled_cpu(cpu) > since those disabled vCPUs will be released in hw/arm/virt.c pretty soon. For disabled CPUs, GICV3CPUState will be initialized to NULL and will continue to exists even after its corresponding QOM CPUState objects have been released. > > diff --git a/hw/intc/arm_gicv3_cpuif.c b/hw/intc/arm_gicv3_cpuif.c > > index d07b13eb27..7b7a0fdb9c 100644 > > --- a/hw/intc/arm_gicv3_cpuif.c > > +++ b/hw/intc/arm_gicv3_cpuif.c > > @@ -934,6 +934,10 @@ void gicv3_cpuif_update(GICv3CPUState *cs) > > ARMCPU *cpu = ARM_CPU(cs->cpu); > > CPUARMState *env = &cpu->env; > > > > + if (!qemu_enabled_cpu(cs->cpu)) { > > + return; > > + } > > + > > The question is how it's possible. It seems a bug to update GICv3CPUState > who isn't ready or disabled. Ideally, it should not. This code is meant for TCG and any updates happening for the entire GICv3 like in GICv3_update() function, which iterates over number of GICV3 CPUs, this is required to ensure updates do not happen if corresponding CPUState object does not exist. [...] > > > > + /* > > + * This shall be called even when vcpu is being hotplugged or onlined and > > + * other vcpus might be running. Host kernel KVM code to handle device > > + * access of IOCTLs KVM_{GET|SET}_DEVICE_ATTR might fail due to inability to > > + * grab vcpu locks for all the vcpus. Hence, we need to pause all vcpus to > > + * facilitate locking within host. > > + */ > > + pause_all_vcpus(); > > /* Initialize to actual HW supported configuration */ > > kvm_device_access(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS, > > KVM_VGIC_ATTR(ICC_CTLR_EL1, c->gicr_typer), > > &c->icc_ctlr_el1[GICV3_NS], false, &error_abort); > > + resume_all_vcpus(); > > Please swap the positions for paused_all_vcpu() and the next comment, and > then combine the comments. No issues. 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 07/37] arm/virt, gicv3: Changes to pre-size GIC with possible vcpus @machine init Date: Mon, 16 Oct 2023 16:15:57 +0000 [thread overview] Message-ID: <6530351c0fa94f68ab4be05198434794@huawei.com> (raw) Message-ID: <20231016161557.oPX51zybe3NnI74Zy_uzjjRIzibtyy5F1Npj7K32kHo@z> (raw) In-Reply-To: <ae71fa00-fcc5-ef34-ef94-b3fd37622582@redhat.com> Hi Gavin, > From: Gavin Shan <gshan@redhat.com> > Sent: Thursday, September 28, 2023 1:14 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 07/37] arm/virt,gicv3: Changes to pre-size GIC > with possible vcpus @machine init > > Hi Salil, > > On 9/26/23 20:04, Salil Mehta wrote: > > GIC needs to be pre-sized with possible vcpus at the initialization time. This > > is necessary because Memory regions and resources associated with GICC/GICR > > etc cannot be changed (add/del/modified) after VM has inited. Also, GIC_TYPER > > needs to be initialized with mp_affinity and cpu interface number association. > > This cannot be changed after GIC has initialized. > > > > Once all the cpu interfaces of the GIC has been inited it needs to be ensured > ^^^^^^ > initialized, Sure. Thanks! > > that any updates to the GICC during reset only takes place for the present > > ^^^^^^^^^^^ > the > enabled Yes. I will fix the sentence. Thanks Salil. > > vcpus and not the disabled ones. Therefore, proper checks are required at > > various places. > > > > Co-developed-by: Salil Mehta <salil.mehta@huawei.com> > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > Co-developed-by: Keqian Zhu <zhukeqian1@huawei.com> > > Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com> > > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org> > > [changed the comment in arm_gicv3_icc_reset] > > Signed-off-by: Salil Mehta <salil.mehta@huawei.com> > > --- > > hw/arm/virt.c | 15 ++++++++------- > > hw/intc/arm_gicv3_common.c | 7 +++++-- > > hw/intc/arm_gicv3_cpuif.c | 8 ++++++++ > > hw/intc/arm_gicv3_kvm.c | 34 +++++++++++++++++++++++++++++++--- > > include/hw/arm/virt.h | 2 +- > > 5 files changed, 53 insertions(+), 13 deletions(-) > > > > I guess the subject can be improved to something like below because it's the preparatory > work to support vCPU hotplug (notifier) in the subsequent patches. In this patch, most > of the code changes is related to vCPU state, ms->smp_pros.max_cpus and the CPU interface > instances associated to GICv3 controller. I general, any commit-log should state 'why' and not 'what' the patch is doing. > > arm/virt,gicv3: Prepare for vCPU hotplug by checking GICv3CPUState states Subject is a summary of what patch intends to do. It is pre-sizing the GIC in QOM and in KVM as well i.e. VGIC. Please check the KVMForum 2023 slides page-6 for more details. > We already had wrappers to check vCPU's states. I'm wandering if we need another set > of wrappers for GICv3 for several facts: (a) In this patch, we're actually concerned > by GICv3CPUState's states, disabled or enabled. vCPU states have been classified to > possible, present, and enabled. Their states aren't matching strictly. (b) With GICv3 > own wrappers, the code can be detached from vCPU in high level. Please evaluate it's > worthy to have GICv3 own wrappers and we can have the folowing wrappers if > want. It will open up the pandoras box if we tickle with GIC as we cannot play with VGIC states in the KVM due to ARM architecture constraints. These states are always part of always-on power domain. In case, we decide to model the QEMU GIC to relax later aspect we would still need to re-size the VGIC at KVM and still expose all of the GIC CPU Interfaces to the Guest OS at boot time. Hence, those GICV3CPUState specific APIs do not add much value to logic to be frank. Plus, once we have these states formally described as part of the QOM then we need to explicitly handle cases, for example, what will these new states mean in terms of Live/Pseudo Migration? Thanks Salil. [...] > > diff --git a/hw/intc/arm_gicv3_common.c b/hw/intc/arm_gicv3_common.c > > index 2ebf880ead..ebd99af610 100644 > > --- a/hw/intc/arm_gicv3_common.c > > +++ b/hw/intc/arm_gicv3_common.c > > @@ -392,10 +392,13 @@ static void arm_gicv3_common_realize(DeviceState > *dev, Error **errp) > > s->cpu = g_new0(GICv3CPUState, s->num_cpu); > > > > for (i = 0; i < s->num_cpu; i++) { > > - CPUState *cpu = qemu_get_cpu(i); > > + CPUState *cpu = qemu_get_possible_cpu(i); > > uint64_t cpu_affid; > > > > - s->cpu[i].cpu = cpu; > > + if (qemu_enabled_cpu(cpu)) { > > + s->cpu[i].cpu = cpu; > > + } > > + > > s->cpu[i].gic = s; > > /* Store GICv3CPUState in CPUARMState gicv3state pointer */ > > gicv3_set_gicv3state(cpu, &s->cpu[i]); > > I don't think gicv3_set_gicv3state() isn't needed for !qemu_enabled_cpu(cpu) > since those disabled vCPUs will be released in hw/arm/virt.c pretty soon. For disabled CPUs, GICV3CPUState will be initialized to NULL and will continue to exists even after its corresponding QOM CPUState objects have been released. > > diff --git a/hw/intc/arm_gicv3_cpuif.c b/hw/intc/arm_gicv3_cpuif.c > > index d07b13eb27..7b7a0fdb9c 100644 > > --- a/hw/intc/arm_gicv3_cpuif.c > > +++ b/hw/intc/arm_gicv3_cpuif.c > > @@ -934,6 +934,10 @@ void gicv3_cpuif_update(GICv3CPUState *cs) > > ARMCPU *cpu = ARM_CPU(cs->cpu); > > CPUARMState *env = &cpu->env; > > > > + if (!qemu_enabled_cpu(cs->cpu)) { > > + return; > > + } > > + > > The question is how it's possible. It seems a bug to update GICv3CPUState > who isn't ready or disabled. Ideally, it should not. This code is meant for TCG and any updates happening for the entire GICv3 like in GICv3_update() function, which iterates over number of GICV3 CPUs, this is required to ensure updates do not happen if corresponding CPUState object does not exist. [...] > > > > + /* > > + * This shall be called even when vcpu is being hotplugged or onlined and > > + * other vcpus might be running. Host kernel KVM code to handle device > > + * access of IOCTLs KVM_{GET|SET}_DEVICE_ATTR might fail due to inability to > > + * grab vcpu locks for all the vcpus. Hence, we need to pause all vcpus to > > + * facilitate locking within host. > > + */ > > + pause_all_vcpus(); > > /* Initialize to actual HW supported configuration */ > > kvm_device_access(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS, > > KVM_VGIC_ATTR(ICC_CTLR_EL1, c->gicr_typer), > > &c->icc_ctlr_el1[GICV3_NS], false, &error_abort); > > + resume_all_vcpus(); > > Please swap the positions for paused_all_vcpu() and the next comment, and > then combine the comments. No issues. Thanks Salil.
next prev parent reply other threads:[~2023-10-16 16:17 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 [this message] 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 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=6530351c0fa94f68ab4be05198434794@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).