From: Gavin Shan <gshan@redhat.com>
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@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,
zhukeqian1@huawei.com, wangxiongfeng2@huawei.com,
wangyanan55@huawei.com, jiakernel2@gmail.com,
maobibo@loongson.cn, lixianglai@loongson.cn
Subject: Re: [PATCH RFC V2 34/37] target/arm/kvm,tcg: Register/Handle SMCCC hypercall exits to VMM/Qemu
Date: Fri, 29 Sep 2023 14:15:06 +1000 [thread overview]
Message-ID: <a3ae4b88-6066-4c21-5fe5-cfe74bc58aaa@redhat.com> (raw)
In-Reply-To: <20230926103654.34424-3-salil.mehta@huawei.com>
Hi Salil,
On 9/26/23 20:36, Salil Mehta wrote:
> From: Author Salil Mehta <salil.mehta@huawei.com>
>
> Add registration and Handling of HVC/SMC hypercall exits to VMM
>
> Co-developed-by: Salil Mehta <salil.mehta@huawei.com>
> Signed-off-by: Salil Mehta <salil.mehta@huawei.com>
> Co-developed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Signed-off-by: Salil Mehta <salil.mehta@huawei.com>
> ---
> target/arm/arm-powerctl.c | 51 +++++++++++++++++++++++++++++-------
> target/arm/helper.c | 2 +-
> target/arm/internals.h | 11 --------
> target/arm/kvm.c | 52 +++++++++++++++++++++++++++++++++++++
> target/arm/kvm64.c | 46 +++++++++++++++++++++++++++++---
> target/arm/kvm_arm.h | 13 ++++++++++
> target/arm/meson.build | 1 +
> target/arm/{tcg => }/psci.c | 8 ++++++
> target/arm/tcg/meson.build | 4 ---
> 9 files changed, 160 insertions(+), 28 deletions(-)
> rename target/arm/{tcg => }/psci.c (97%)
>
> diff --git a/target/arm/arm-powerctl.c b/target/arm/arm-powerctl.c
> index 326a03153d..0184c7fb09 100644
> --- a/target/arm/arm-powerctl.c
> +++ b/target/arm/arm-powerctl.c
> @@ -16,6 +16,7 @@
> #include "qemu/log.h"
> #include "qemu/main-loop.h"
> #include "sysemu/tcg.h"
> +#include "hw/boards.h"
>
> #ifndef DEBUG_ARM_POWERCTL
> #define DEBUG_ARM_POWERCTL 0
> @@ -28,18 +29,37 @@
> } \
> } while (0)
>
> +static CPUArchId *arm_get_archid_by_id(uint64_t id)
> +{
> + int n;
> + CPUArchId *arch_id;
> + MachineState *ms = MACHINE(qdev_get_machine());
> +
> + /*
> + * At this point disabled CPUs don't have a CPUState, but their CPUArchId
> + * exists.
> + *
> + * TODO: Is arch_id == mp_affinity? This needs work.
> + */
> + for (n = 0; n < ms->possible_cpus->len; n++) {
> + arch_id = &ms->possible_cpus->cpus[n];
> +
> + if (arch_id->arch_id == id) {
> + return arch_id;
> + }
> + }
> + return NULL;
> +}
> +
The @arch_id should be same thing to @mp_affinity except for the boot CPU.
For the boot CPU, its value is fetched from MPIDR, which is determined by
cs->cpu_index, passed to host via ioctl(CREATE_VCPU). Besides, another
similiar function qemu_get_cpu_archid() exists in cpus-common.c. I think
they can be combined. Again, all these information inherited from
ms->possible_cpus may be better to be managed in board level, like the
vCPU states.
> CPUState *arm_get_cpu_by_id(uint64_t id)
> {
> - CPUState *cpu;
> + CPUArchId *arch_id;
>
> DPRINTF("cpu %" PRId64 "\n", id);
>
> - CPU_FOREACH(cpu) {
> - ARMCPU *armcpu = ARM_CPU(cpu);
> -
> - if (armcpu->mp_affinity == id) {
> - return cpu;
> - }
> + arch_id = arm_get_archid_by_id(id);
> + if (arch_id && arch_id->cpu) {
> + return CPU(arch_id->cpu);
> }
>
> qemu_log_mask(LOG_GUEST_ERROR,
> @@ -148,6 +168,7 @@ int arm_set_cpu_on(uint64_t cpuid, uint64_t entry, uint64_t context_id,
> {
> CPUState *target_cpu_state;
> ARMCPU *target_cpu;
> + CPUArchId *arch_id;
> struct CpuOnInfo *info;
>
> assert(qemu_mutex_iothread_locked());
> @@ -168,12 +189,24 @@ int arm_set_cpu_on(uint64_t cpuid, uint64_t entry, uint64_t context_id,
> }
>
> /* Retrieve the cpu we are powering up */
> - target_cpu_state = arm_get_cpu_by_id(cpuid);
> - if (!target_cpu_state) {
> + arch_id = arm_get_archid_by_id(cpuid);
> + if (!arch_id) {
> /* The cpu was not found */
> return QEMU_ARM_POWERCTL_INVALID_PARAM;
> }
>
> + target_cpu_state = CPU(arch_id->cpu);
> + if (!qemu_enabled_cpu(target_cpu_state)) {
> + /*
> + * The cpu is not plugged in or disabled. We should return appropriate
> + * value as introduced in DEN0022E PSCI 1.2 issue E
^^^^^^^
issue E, which is QEMU_PSCI_RET_DENIED.
> + */
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "[ARM]%s: Denying attempt to online removed/disabled "
> + "CPU%" PRId64"\n", __func__, cpuid);
> + return QEMU_ARM_POWERCTL_IS_OFF;
> + }
> +
> target_cpu = ARM_CPU(target_cpu_state);
> if (target_cpu->power_state == PSCI_ON) {
> qemu_log_mask(LOG_GUEST_ERROR,
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index 272d6ba139..4d396426f2 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -11187,7 +11187,7 @@ void arm_cpu_do_interrupt(CPUState *cs)
> env->exception.syndrome);
> }
>
> - if (tcg_enabled() && arm_is_psci_call(cpu, cs->exception_index)) {
> + if (arm_is_psci_call(cpu, cs->exception_index)) {
> arm_handle_psci_call(cpu);
> qemu_log_mask(CPU_LOG_INT, "...handled as PSCI call\n");
> return;
We may still limit the capability to handle PSCI calls to TCG and KVM,
meaning HVF and QTest won't have this capability.
> diff --git a/target/arm/internals.h b/target/arm/internals.h
> index fe330e89e7..7ffefc2d58 100644
> --- a/target/arm/internals.h
> +++ b/target/arm/internals.h
> @@ -305,21 +305,10 @@ vaddr arm_adjust_watchpoint_address(CPUState *cs, vaddr addr, int len);
> /* Callback function for when a watchpoint or breakpoint triggers. */
> void arm_debug_excp_handler(CPUState *cs);
>
> -#if defined(CONFIG_USER_ONLY) || !defined(CONFIG_TCG)
> -static inline bool arm_is_psci_call(ARMCPU *cpu, int excp_type)
> -{
> - return false;
> -}
> -static inline void arm_handle_psci_call(ARMCPU *cpu)
> -{
> - g_assert_not_reached();
> -}
> -#else
> /* Return true if the r0/x0 value indicates that this SMC/HVC is a PSCI call. */
> bool arm_is_psci_call(ARMCPU *cpu, int excp_type);
> /* Actually handle a PSCI call */
> void arm_handle_psci_call(ARMCPU *cpu);
> -#endif
>
> /**
> * arm_clear_exclusive: clear the exclusive monitor
> diff --git a/target/arm/kvm.c b/target/arm/kvm.c
> index 8e7c68af6a..6f3fd5aecd 100644
> --- a/target/arm/kvm.c
> +++ b/target/arm/kvm.c
> @@ -250,6 +250,7 @@ int kvm_arm_get_max_vm_ipa_size(MachineState *ms, bool *fixed_ipa)
> int kvm_arch_init(MachineState *ms, KVMState *s)
> {
> int ret = 0;
> +
^^^^
Unnecessary change.
> /* For ARM interrupt delivery is always asynchronous,
> * whether we are using an in-kernel VGIC or not.
> */
> @@ -280,6 +281,22 @@ int kvm_arch_init(MachineState *ms, KVMState *s)
> }
> }
>
> + /*
> + * To be able to handle PSCI CPU ON calls in QEMU, we need to install SMCCC
^^
ON/OFF
> + * filter in the Host KVM. This is required to support features like
> + * virtual CPU Hotplug on ARM platforms.
> + */
> + if (kvm_arm_set_smccc_filter(PSCI_0_2_FN64_CPU_ON,
> + KVM_SMCCC_FILTER_FWD_TO_USER)) {
> + error_report("CPU On PSCI-to-user-space fwd filter install failed");
> + abort();
> + }
> + if (kvm_arm_set_smccc_filter(PSCI_0_2_FN_CPU_OFF,
> + KVM_SMCCC_FILTER_FWD_TO_USER)) {
> + error_report("CPU Off PSCI-to-user-space fwd filter install failed");
> + abort();
> + }
> +
> kvm_arm_init_debug(s);
>
> return ret;
The PSCI_ON and PSCI_OFF will be unconditionally handled by QEMU if KVM is
enabled, even vCPU hotplug isn't supported on hw/arm/virt board. Do we need to
enable it only when vCPU hotplug is supported?
> @@ -952,6 +969,38 @@ static int kvm_arm_handle_dabt_nisv(CPUState *cs, uint64_t esr_iss,
> return -1;
> }
>
> +static int kvm_arm_handle_hypercall(CPUState *cs, struct kvm_run *run)
> +{
> + ARMCPU *cpu = ARM_CPU(cs);
> + CPUARMState *env = &cpu->env;
> +
> + kvm_cpu_synchronize_state(cs);
> +
> + /*
> + * hard coding immediate to 0 as we dont expect non-zero value as of now
^^^^
don't
> + * This might change in future versions. Hence, KVM_GET_ONE_REG could be
> + * used in such cases but it must be enhanced then only synchronize will
> + * also fetch ESR_EL2 value.
> + */
> + if (run->hypercall.flags == KVM_HYPERCALL_EXIT_SMC) {
> + cs->exception_index = EXCP_SMC;
> + env->exception.syndrome = syn_aa64_smc(0);
> + } else {
> + cs->exception_index = EXCP_HVC;
> + env->exception.syndrome = syn_aa64_hvc(0);
> + }
> + env->exception.target_el = 1;
> + qemu_mutex_lock_iothread();
> + arm_cpu_do_interrupt(cs);
> + qemu_mutex_unlock_iothread();
> +
> + /*
> + * For PSCI, exit the kvm_run loop and process the work. Especially
> + * important if this was a CPU_OFF command and we can't return to the guest.
> + */
> + return EXCP_INTERRUPT;
> +}
> +
> int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)
> {
> int ret = 0;
> @@ -967,6 +1016,9 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)
> ret = kvm_arm_handle_dabt_nisv(cs, run->arm_nisv.esr_iss,
> run->arm_nisv.fault_ipa);
> break;
> + case KVM_EXIT_HYPERCALL:
> + ret = kvm_arm_handle_hypercall(cs, run);
> + break;
> default:
> qemu_log_mask(LOG_UNIMP, "%s: un-handled exit reason %d\n",
> __func__, run->exit_reason);
> diff --git a/target/arm/kvm64.c b/target/arm/kvm64.c
> index 38de0b4148..efe24e3f90 100644
> --- a/target/arm/kvm64.c
> +++ b/target/arm/kvm64.c
> @@ -113,6 +113,25 @@ bool kvm_arm_hw_debug_active(CPUState *cs)
> return ((cur_hw_wps > 0) || (cur_hw_bps > 0));
> }
>
> +static bool kvm_arm_set_vm_attr(struct kvm_device_attr *attr, const char *name)
> +{
> + int err;
> +
> + err = kvm_vm_ioctl(kvm_state, KVM_HAS_DEVICE_ATTR, attr);
> + if (err != 0) {
> + error_report("%s: KVM_HAS_DEVICE_ATTR: %s", name, strerror(-err));
> + return false;
> + }
> +
> + err = kvm_vm_ioctl(kvm_state, KVM_SET_DEVICE_ATTR, attr);
> + if (err != 0) {
> + error_report("%s: KVM_SET_DEVICE_ATTR: %s", name, strerror(-err));
> + return false;
> + }
> +
> + return true;
> +}
> +
> static bool kvm_arm_set_device_attr(CPUState *cs, struct kvm_device_attr *attr,
> const char *name)
> {
> @@ -183,6 +202,28 @@ void kvm_arm_pvtime_init(CPUState *cs, uint64_t ipa)
> }
> }
>
> +int kvm_arm_set_smccc_filter(uint64_t func, uint8_t faction)
> +{
> + struct kvm_smccc_filter filter = {
> + .base = func,
> + .nr_functions = 1,
> + .action = faction,
> + };
> + struct kvm_device_attr attr = {
> + .group = KVM_ARM_VM_SMCCC_CTRL,
> + .attr = KVM_ARM_VM_SMCCC_FILTER,
> + .flags = 0,
> + .addr = (uintptr_t)&filter,
> + };
> +
> + if (!kvm_arm_set_vm_attr(&attr, "SMCCC Filter")) {
> + error_report("failed to set SMCCC filter in KVM Host");
> + return -1;
> + }
> +
> + return 0;
> +}
> +
> static int read_sys_reg32(int fd, uint32_t *pret, uint64_t id)
> {
> uint64_t ret;
> @@ -633,9 +674,8 @@ int kvm_arch_init_vcpu(CPUState *cs)
> }
>
> /*
> - * When KVM is in use, PSCI is emulated in-kernel and not by qemu.
> - * Currently KVM has its own idea about MPIDR assignment, so we
> - * override our defaults with what we get from KVM.
> + * KVM may emulate PSCI in-kernel. Currently KVM has its own idea about
> + * MPIDR assignment, so we override our defaults with what we get from KVM.
> */
> ret = kvm_get_one_reg(cs, ARM64_SYS_REG(ARM_CPU_ID_MPIDR), &mpidr);
> if (ret) {
> diff --git a/target/arm/kvm_arm.h b/target/arm/kvm_arm.h
> index 31408499b3..bf4df54c96 100644
> --- a/target/arm/kvm_arm.h
> +++ b/target/arm/kvm_arm.h
> @@ -388,6 +388,15 @@ void kvm_arm_pvtime_init(CPUState *cs, uint64_t ipa);
>
> int kvm_arm_set_irq(int cpu, int irqtype, int irq, int level);
>
> +/**
> + * kvm_arm_set_smccc_filter
> + * @func: funcion
> + * @faction: SMCCC filter action(handle, deny, fwd-to-user) to be deployed
> + *
> + * Sets the ARMs SMC-CC filter in KVM Host for selective hypercall exits
> + */
> +int kvm_arm_set_smccc_filter(uint64_t func, uint8_t faction);
> +
> #else
>
> /*
> @@ -462,6 +471,10 @@ static inline uint32_t kvm_arm_sve_get_vls(CPUState *cs)
> g_assert_not_reached();
> }
>
> +static inline int kvm_arm_set_smccc_filter(uint64_t func, uint8_t faction)
> +{
> + g_assert_not_reached();
> +}
> #endif
>
> /**
> diff --git a/target/arm/meson.build b/target/arm/meson.build
> index e645e456da..fdfc8b958f 100644
> --- a/target/arm/meson.build
> +++ b/target/arm/meson.build
> @@ -23,6 +23,7 @@ arm_system_ss.add(files(
> 'arm-qmp-cmds.c',
> 'cortex-regs.c',
> 'machine.c',
> + 'psci.c',
> 'ptw.c',
> ))
>
> diff --git a/target/arm/tcg/psci.c b/target/arm/psci.c
> similarity index 97%
> rename from target/arm/tcg/psci.c
> rename to target/arm/psci.c
> index 6c1239bb96..a8690a16af 100644
> --- a/target/arm/tcg/psci.c
> +++ b/target/arm/psci.c
> @@ -21,7 +21,9 @@
> #include "exec/helper-proto.h"
> #include "kvm-consts.h"
> #include "qemu/main-loop.h"
> +#include "qemu/error-report.h"
> #include "sysemu/runstate.h"
> +#include "sysemu/tcg.h"
> #include "internals.h"
> #include "arm-powerctl.h"
>
> @@ -157,6 +159,11 @@ void arm_handle_psci_call(ARMCPU *cpu)
> case QEMU_PSCI_0_1_FN_CPU_SUSPEND:
> case QEMU_PSCI_0_2_FN_CPU_SUSPEND:
> case QEMU_PSCI_0_2_FN64_CPU_SUSPEND:
> + if (!tcg_enabled()) {
> + warn_report("CPU suspend not supported in non-tcg mode");
> + break;
> + }
> +#ifdef CONFIG_TCG
> /* Affinity levels are not supported in QEMU */
> if (param[1] & 0xfffe0000) {
> ret = QEMU_PSCI_RET_INVALID_PARAMS;
> @@ -169,6 +176,7 @@ void arm_handle_psci_call(ARMCPU *cpu)
> env->regs[0] = 0;
> }
> helper_wfi(env, 4);
> +#endif
> break;
> case QEMU_PSCI_1_0_FN_PSCI_FEATURES:
> switch (param[1]) {
> diff --git a/target/arm/tcg/meson.build b/target/arm/tcg/meson.build
> index 6fca38f2cc..ad3cfcb3bd 100644
> --- a/target/arm/tcg/meson.build
> +++ b/target/arm/tcg/meson.build
> @@ -51,7 +51,3 @@ arm_ss.add(when: 'TARGET_AARCH64', if_true: files(
> 'sme_helper.c',
> 'sve_helper.c',
> ))
> -
> -arm_system_ss.add(files(
> - 'psci.c',
> -))
Thanks,
Gavin
next prev parent reply other threads:[~2023-09-29 4:16 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
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 ` Gavin Shan [this message]
2023-10-17 0:03 ` [PATCH RFC V2 34/37] target/arm/kvm,tcg: " 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=a3ae4b88-6066-4c21-5fe5-cfe74bc58aaa@redhat.com \
--to=gshan@redhat.com \
--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=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=qemu-devel@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: 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).