From: Vincent Donnefort <vdonnefort@google.com>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: maz@kernel.org, oupton@kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, joey.gouly@arm.com, seiden@linux.ibm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
mark.rutland@arm.com, steven.price@arm.com, qperret@google.com,
tabba@google.com
Subject: Re: [PATCH v3 10/18] KVM: arm64: Handle PSCI calls for protected VMs at EL2
Date: Tue, 22 Sep 2026 17:35:09 +0100 [thread overview]
Message-ID: <arKuPQ-w5EFXo-n8@google.com> (raw)
In-Reply-To: <20260914113338.159227-11-fuad.tabba@linux.dev>
On Mon, Sep 14, 2026 at 12:33:30PM +0100, Fuad Tabba wrote:
> EL2 implements PSCI 1.1 for protected VMs: CPU_ON, CPU_OFF,
> PSCI_VERSION and PSCI_FEATURES are decided at EL2 (CPU_ON and CPU_OFF
> still exit to the host, which only schedules or parks the target),
> AFFINITY_INFO, CPU_SUSPEND and the platform power operations are
> forwarded to the host, and anything else returns NOT_SUPPORTED,
> including the TRNG calls and the functions above 1.1, SYSTEM_OFF2
> among them, that the host handled for a protected guest until now.
> TRNG for protected guests is a follow-up. AFFINITY_INFO stays
> with the host, which returns OFF only once it has parked the target:
> the host is what a guest polls to see a CPU_OFF complete before it
> issues the next CPU_ON, as Linux does on hotplug.
>
> Three consequences follow:
>
> - A protected VM has one primary vCPU, the first whose hyp vCPU is
> created with mp_state RUNNABLE. A second one, or an mp_state other
> than RUNNABLE or STOPPED, fails that vCPU's first KVM_RUN with
> -EINVAL.
>
> - CPU_ON finds its target among the hyp vCPUs, which exist from the
> target's first KVM_RUN; before that the guest gets
> INVALID_PARAMETERS.
>
> - A vCPU EL2 holds powered off doesn't run: handle___kvm_vcpu_run()
> returns ARM_EXCEPTION_IL, reported as KVM_EXIT_FAIL_ENTRY. Its
> existing bail-outs return the same code instead of an -EINVAL that
> handle_exit() didn't recognise, for every hyp vCPU.
>
> Non-protected VMs keep power_state ON and accept any mp_state.
>
> Each protected vCPU is OFF, ON_PENDING or ON. CPU_ON moves the target
> to ON_PENDING, and the target's next run resets it and moves it to ON.
> The racing transitions are cmpxchg, and the reset state is published
> with a release/acquire pair, documented at each site. CPU_OFF publishes
> OFF with a release, so the target's clear of reset_state.reset is
> ordered before it and a CPU_ON that then wins on OFF republishes after
> the clear. Rolling a CPU_ON the host failed back to OFF needs the
> host's return value, which the per-EC marshalling patch delivers along
> with the rollback. Until then such a target stays ON_PENDING, and the
> reset has no observable effect: flush_hyp_vcpu() copies the host's
> context in on every entry until that patch removes the copy, so the
> target enters on the host's values rather than the ones EL2 reset.
>
> Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
> ---
> arch/arm64/kvm/hyp/include/nvhe/pkvm.h | 14 ++
> arch/arm64/kvm/hyp/nvhe/hyp-main.c | 25 ++-
> arch/arm64/kvm/hyp/nvhe/pkvm.c | 283 ++++++++++++++++++++++++-
> 3 files changed, 311 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/include/nvhe/pkvm.h b/arch/arm64/kvm/hyp/include/nvhe/pkvm.h
> index a04b7c04d5135..63b368baf0e72 100644
> --- a/arch/arm64/kvm/hyp/include/nvhe/pkvm.h
> +++ b/arch/arm64/kvm/hyp/include/nvhe/pkvm.h
> @@ -29,6 +29,12 @@ struct pkvm_hyp_vcpu {
>
> /* The previous exit's ARM_EXCEPTION_* code. */
> u32 exit_code;
> +
> + /*
> + * PSCI_0_2_AFFINITY_LEVEL_{OFF, ON_PENDING, ON}. A non-protected
> + * vCPU is always ON.
> + */
> + int power_state;
> };
>
> /*
> @@ -46,6 +52,12 @@ struct pkvm_hyp_vm {
> struct hyp_pool pool;
> hyp_spinlock_t lock;
>
> + /*
> + * The vCPU initialised RUNNABLE: claimed under vm_table_lock,
> + * released only if its own init fails.
> + */
> + struct pkvm_hyp_vcpu *primary_vcpu;
> +
> /* Array of the hyp vCPU structures for this VM. */
> struct pkvm_hyp_vcpu *vcpus[];
> };
> @@ -98,4 +110,6 @@ void kvm_init_pvm_id_regs(struct kvm_vcpu *vcpu);
> void kvm_reset_pvm_sys_regs(struct kvm_vcpu *vcpu);
> int kvm_check_pvm_sysreg_table(void);
>
> +int pkvm_reset_vcpu(struct pkvm_hyp_vcpu *hyp_vcpu);
> +struct pkvm_hyp_vcpu *pkvm_mpidr_to_hyp_vcpu(struct pkvm_hyp_vm *vm, u64 mpidr);
> #endif /* __ARM64_KVM_NVHE_PKVM_H__ */
> diff --git a/arch/arm64/kvm/hyp/nvhe/hyp-main.c b/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> index 9cc8ef16897c1..da8ab636063cf 100644
> --- a/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> +++ b/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> @@ -8,6 +8,7 @@
> #include <hyp/switch.h>
>
> #include <linux/irqchip/arm-gic-v3.h>
> +#include <uapi/linux/psci.h>
>
> #include <asm/pgtable-types.h>
> #include <asm/kvm_asm.h>
> @@ -456,14 +457,12 @@ static void handle___kvm_vcpu_run(struct kvm_cpu_context *host_ctxt)
> {
> struct pkvm_hyp_vcpu *hyp_vcpu;
> struct kvm_vcpu *host_vcpu;
> - int ret;
> + int ret = ARM_EXCEPTION_IL;
>
> host_vcpu = get_host_hyp_vcpus(host_ctxt, 1, &hyp_vcpu);
>
> - if (!host_vcpu) {
> - ret = -EINVAL;
> + if (!host_vcpu)
> goto out;
> - }
>
> if (unlikely(hyp_vcpu)) {
> /*
> @@ -472,8 +471,22 @@ static void handle___kvm_vcpu_run(struct kvm_cpu_context *host_ctxt)
> * loading a vcpu. Therefore, if SME features enabled the host
> * is misbehaving.
> */
> - if (unlikely(system_supports_sme() && read_sysreg_s(SYS_SVCR))) {
> - ret = -EINVAL;
> + if (unlikely(system_supports_sme() && read_sysreg_s(SYS_SVCR)))
> + goto out;
> +
> + /*
> + * ON has a single writer, pkvm_reset_vcpu() on this CPU, so
> + * READ_ONCE suffices. ON_PENDING takes the reset; -ECANCELED
> + * is a rollback that raced it.
> + */
> + switch (READ_ONCE(hyp_vcpu->power_state)) {
> + case PSCI_0_2_AFFINITY_LEVEL_ON:
> + break;
> + case PSCI_0_2_AFFINITY_LEVEL_ON_PENDING:
> + if (pkvm_reset_vcpu(hyp_vcpu))
> + goto out;
> + break;
> + default:
> goto out;
> }
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/pkvm.c b/arch/arm64/kvm/hyp/nvhe/pkvm.c
> index 855cb77c8bba1..d970cba12ca47 100644
> --- a/arch/arm64/kvm/hyp/nvhe/pkvm.c
> +++ b/arch/arm64/kvm/hyp/nvhe/pkvm.c
> @@ -5,6 +5,7 @@
> */
>
> #include <kvm/arm_hypercalls.h>
> +#include <kvm/arm_psci.h>
>
> #include <linux/kvm_host.h>
> #include <linux/mm.h>
> @@ -433,6 +434,40 @@ static void pkvm_init_features_from_host(struct pkvm_hyp_vm *hyp_vm, const struc
> allowed_features, KVM_VCPU_MAX_FEATURES);
> }
>
> +static int pkvm_vcpu_init_psci(struct pkvm_hyp_vcpu *hyp_vcpu, u32 mp_state)
> +{
> + struct vcpu_reset_state *reset_state = &hyp_vcpu->vcpu.arch.reset_state;
> + struct pkvm_hyp_vm *hyp_vm = pkvm_hyp_vcpu_to_hyp_vm(hyp_vcpu);
> + struct kvm_vcpu *host_vcpu;
> +
> + if (!pkvm_hyp_vcpu_is_protected(hyp_vcpu)) {
> + /* The host manages a non-protected vCPU: always ON at EL2. */
> + hyp_vcpu->power_state = PSCI_0_2_AFFINITY_LEVEL_ON;
> + return 0;
> + }
> +
> + if (mp_state != KVM_MP_STATE_RUNNABLE && mp_state != KVM_MP_STATE_STOPPED)
> + return -EINVAL;
> +
> + if (mp_state == KVM_MP_STATE_STOPPED) {
> + reset_state->reset = false;
> + hyp_vcpu->power_state = PSCI_0_2_AFFINITY_LEVEL_OFF;
> + return 0;
> + }
> +
> + hyp_assert_lock_held(&vm_table_lock);
> + if (hyp_vm->primary_vcpu)
> + return -EINVAL;
> + hyp_vm->primary_vcpu = hyp_vcpu;
> +
> + host_vcpu = hyp_vcpu->host_vcpu;
> + reset_state->pc = READ_ONCE(host_vcpu->arch.ctxt.regs.pc);
> + reset_state->r0 = READ_ONCE(host_vcpu->arch.ctxt.regs.regs[0]);
> + reset_state->reset = true;
> + hyp_vcpu->power_state = PSCI_0_2_AFFINITY_LEVEL_ON_PENDING;
> + return 0;
> +}
> +
> static void unpin_host_vcpu(struct kvm_vcpu *host_vcpu)
> {
> if (host_vcpu)
> @@ -447,6 +482,9 @@ static void unpin_host_sve_state(struct pkvm_hyp_vcpu *hyp_vcpu)
> return;
>
> sve_state = hyp_vcpu->vcpu.arch.sve_state;
> + if (!sve_state)
> + return;
> +
> hyp_unpin_shared_mem(sve_state,
> sve_state + vcpu_sve_state_size(&hyp_vcpu->vcpu));
> }
> @@ -559,10 +597,12 @@ static int init_pkvm_hyp_vcpu(struct pkvm_hyp_vcpu *hyp_vcpu,
> struct kvm_vcpu *host_vcpu)
> {
> int ret = 0;
> + u32 mp_state;
>
> if (hyp_pin_shared_mem(host_vcpu, host_vcpu + 1))
> return -EBUSY;
>
> + mp_state = READ_ONCE(host_vcpu->arch.mp_state.mp_state);
> hyp_vcpu->host_vcpu = host_vcpu;
>
> hyp_vcpu->vcpu.kvm = &hyp_vm->kvm;
> @@ -571,7 +611,6 @@ static int init_pkvm_hyp_vcpu(struct pkvm_hyp_vcpu *hyp_vcpu,
>
> hyp_vcpu->vcpu.arch.hw_mmu = &hyp_vm->kvm.arch.mmu;
> hyp_vcpu->vcpu.arch.cflags = READ_ONCE(host_vcpu->arch.cflags);
> - hyp_vcpu->vcpu.arch.mp_state.mp_state = KVM_MP_STATE_STOPPED;
>
> if (!pkvm_hyp_vcpu_is_protected(hyp_vcpu)) {
> /*
> @@ -601,9 +640,12 @@ static int init_pkvm_hyp_vcpu(struct pkvm_hyp_vcpu *hyp_vcpu,
>
> if (pkvm_hyp_vcpu_is_protected(hyp_vcpu))
> kvm_reset_pvm_sys_regs(&hyp_vcpu->vcpu);
> + ret = pkvm_vcpu_init_psci(hyp_vcpu, mp_state);
> done:
> - if (ret)
> + if (ret) {
> unpin_host_vcpu(host_vcpu);
> + unpin_host_sve_state(hyp_vcpu);
> + }
Was it planned for a different commit of the series?
> return ret;
> }
>
> @@ -980,13 +1022,22 @@ int __pkvm_init_vcpu(pkvm_handle_t handle, struct kvm_vcpu *host_vcpu,
>
> ret = init_pkvm_hyp_vcpu(hyp_vcpu, hyp_vm, host_vcpu);
> if (ret)
> - goto unlock;
> + goto unclaim;
>
> ret = register_hyp_vcpu(hyp_vm, hyp_vcpu);
> if (ret) {
> unpin_host_vcpu(host_vcpu);
> unpin_host_sve_state(hyp_vcpu);
> + goto unclaim;
> }
> + goto unlock;
> +unclaim:
> + /*
> + * Under vm_table_lock, so no other claim can have landed: undo
> + * this one.
> + */
> + if (hyp_vm->primary_vcpu == hyp_vcpu)
> + hyp_vm->primary_vcpu = NULL;
> unlock:
> hyp_spin_unlock(&vm_table_lock);
>
> @@ -1178,6 +1229,228 @@ static void pkvm_memunshare_call(u64 *ret, struct kvm_vcpu *vcpu)
> ret[0] = SMCCC_RET_SUCCESS;
> }
>
> +/*
> + * Reset the vCPU to its power-on state and commit ON_PENDING -> ON, on the
> + * target's own CPU. Returns -ECANCELED, with no side effects, if a rollback
> + * raced the reset.
> + */
> +int pkvm_reset_vcpu(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + struct vcpu_reset_state *reset_state = &hyp_vcpu->vcpu.arch.reset_state;
> + int prev;
> +
> + /*
> + * Pairs with smp_store_release(&reset_state->reset, true) in
> + * pvm_psci_vcpu_on(). The acquire must precede the cmpxchg: reversed, a
> + * winning cmpxchg with a false acquire would leave power_state == ON
> + * with the reset skipped.
> + */
> + if (!smp_load_acquire(&reset_state->reset))
> + return -ECANCELED;
> +
> + prev = cmpxchg_relaxed(&hyp_vcpu->power_state,
> + PSCI_0_2_AFFINITY_LEVEL_ON_PENDING,
> + PSCI_0_2_AFFINITY_LEVEL_ON);
> + if (prev != PSCI_0_2_AFFINITY_LEVEL_ON_PENDING) {
> + /* The only other writer of ON_PENDING is the rollback. */
> + WARN_ON(prev != PSCI_0_2_AFFINITY_LEVEL_OFF);
> + return -ECANCELED;
> + }
> +
> + kvm_reset_vcpu_core(&hyp_vcpu->vcpu);
> + kvm_reset_pvm_sys_regs(&hyp_vcpu->vcpu);
> +
> + /* Must be done after resetting sys registers. */
> + kvm_reset_vcpu_psci(&hyp_vcpu->vcpu, reset_state);
> +
> + hyp_vcpu->exit_code = 0;
> + /*
> + * A source that raced a rollback can publish after this clear, and
> + * the next cycle then passes the acquire on a stale flag: the pc,
> + * r0 and be it reads are still the guest's own.
> + */
> + reset_state->reset = false;
> + return 0;
> +}
> +
> +struct pkvm_hyp_vcpu *pkvm_mpidr_to_hyp_vcpu(struct pkvm_hyp_vm *hyp_vm,
> + u64 mpidr)
> +{
> + struct pkvm_hyp_vcpu *hyp_vcpu;
> + int i;
> +
> + mpidr &= MPIDR_HWID_BITMASK;
> +
> + for (i = 0; i < hyp_vm->kvm.created_vcpus; i++) {
> + /* Pairs with smp_store_release() in register_hyp_vcpu(). */
> + hyp_vcpu = smp_load_acquire(&hyp_vm->vcpus[i]);
> +
> + if (!hyp_vcpu)
> + continue;
> +
> + if (mpidr == kvm_vcpu_get_mpidr_aff(&hyp_vcpu->vcpu))
> + return hyp_vcpu;
> + }
> +
> + return NULL;
> +}
> +
> +/*
> + * Returns true when handled at EL2, false when the host must wake the target
> + * vCPU.
> + */
> +static bool pvm_psci_vcpu_on(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + struct pkvm_hyp_vm *hyp_vm = pkvm_hyp_vcpu_to_hyp_vm(hyp_vcpu);
> + struct vcpu_reset_state *reset_state;
> + struct pkvm_hyp_vcpu *target;
> + unsigned long cpu_id, ret;
> + int power_state;
> +
> + cpu_id = smccc_get_arg1(&hyp_vcpu->vcpu);
> + if (!kvm_psci_valid_affinity(&hyp_vcpu->vcpu, cpu_id)) {
> + ret = PSCI_RET_INVALID_PARAMS;
> + goto error;
> + }
> +
> + target = pkvm_mpidr_to_hyp_vcpu(hyp_vm, cpu_id);
> + if (!target) {
> + ret = PSCI_RET_INVALID_PARAMS;
> + goto error;
> + }
> +
> + /*
> + * vCPUs race to power on the same target. Relaxed: reset_state
> + * is published by the release on reset_state.reset below.
> + */
> + power_state = cmpxchg_relaxed(&target->power_state,
> + PSCI_0_2_AFFINITY_LEVEL_OFF,
> + PSCI_0_2_AFFINITY_LEVEL_ON_PENDING);
> + switch (power_state) {
> + case PSCI_0_2_AFFINITY_LEVEL_ON_PENDING:
> + ret = PSCI_RET_ON_PENDING;
> + goto error;
> + case PSCI_0_2_AFFINITY_LEVEL_ON:
> + ret = PSCI_RET_ALREADY_ON;
> + goto error;
> + case PSCI_0_2_AFFINITY_LEVEL_OFF:
> + break;
> + default:
> + ret = PSCI_RET_INTERNAL_FAILURE;
> + goto error;
> + }
> +
> + reset_state = &target->vcpu.arch.reset_state;
> + reset_state->pc = smccc_get_arg2(&hyp_vcpu->vcpu);
> + reset_state->r0 = smccc_get_arg3(&hyp_vcpu->vcpu);
> + reset_state->be = kvm_vcpu_is_be(&hyp_vcpu->vcpu);
> + /*
> + * Publish reset_state.{pc, r0, be} to the target vCPU. Pairs with
> + * smp_load_acquire(&reset_state->reset) in pkvm_reset_vcpu().
> + */
> + smp_store_release(&reset_state->reset, true);
> +
> + /* The host requests KVM_REQ_VCPU_RESET and wakes the target. */
> + return false;
> +
> +error:
> + smccc_set_retval(&hyp_vcpu->vcpu, ret, 0, 0, 0);
> + return true;
> +}
> +
> +/*
> + * Returns true when handled at EL2, false when the host must stop scheduling
> + * the vCPU.
> + */
> +static bool pvm_psci_vcpu_off(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + /* No other writer runs while this vCPU is ON and executing. */
> + WARN_ON(READ_ONCE(hyp_vcpu->power_state) != PSCI_0_2_AFFINITY_LEVEL_ON);
> +
> + /*
> + * Orders pkvm_reset_vcpu()'s clear of reset_state.reset before OFF, so
> + * a CPU_ON that wins on OFF republishes after it. Pairs with the
> + * cmpxchg in pvm_psci_vcpu_on().
> + */
> + smp_store_release(&hyp_vcpu->power_state, PSCI_0_2_AFFINITY_LEVEL_OFF);
> +
> + /* Return to the host so that it can finish powering off the vcpu. */
> + return false;
> +}
> +
> +static bool pvm_psci_version(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + /* Nothing to be handled by the host. Go back to the guest. */
> + smccc_set_retval(&hyp_vcpu->vcpu, KVM_ARM_PSCI_1_1, 0, 0, 0);
> + return true;
> +}
> +
> +static bool pvm_psci_features(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + struct kvm_vcpu *vcpu = &hyp_vcpu->vcpu;
> + u32 feature = smccc_get_arg1(vcpu);
> + unsigned long val;
> +
> + switch (feature) {
> + case PSCI_0_2_FN_PSCI_VERSION:
> + case PSCI_0_2_FN_CPU_SUSPEND:
> + case PSCI_0_2_FN64_CPU_SUSPEND:
> + case PSCI_0_2_FN_CPU_OFF:
> + case PSCI_0_2_FN_CPU_ON:
> + case PSCI_0_2_FN64_CPU_ON:
> + case PSCI_0_2_FN_AFFINITY_INFO:
> + case PSCI_0_2_FN64_AFFINITY_INFO:
> + case PSCI_0_2_FN_SYSTEM_OFF:
> + case PSCI_0_2_FN_SYSTEM_RESET:
> + case PSCI_1_0_FN_PSCI_FEATURES:
> + case PSCI_1_1_FN_SYSTEM_RESET2:
> + case PSCI_1_1_FN64_SYSTEM_RESET2:
> + case ARM_SMCCC_VERSION_FUNC_ID:
> + val = PSCI_RET_SUCCESS;
> + break;
> + default:
> + val = PSCI_RET_NOT_SUPPORTED;
> + break;
> + }
> +
> + /* Nothing to be handled by the host. Go back to the guest. */
> + smccc_set_retval(vcpu, val, 0, 0, 0);
> + return true;
> +}
> +
> +static bool pkvm_handle_psci(struct pkvm_hyp_vcpu *hyp_vcpu)
> +{
> + struct kvm_vcpu *vcpu = &hyp_vcpu->vcpu;
> + u32 psci_fn = smccc_get_function(vcpu);
> +
> + switch (psci_fn) {
> + case PSCI_0_2_FN_CPU_ON:
> + kvm_psci_narrow_to_32bit(vcpu);
> + fallthrough;
> + case PSCI_0_2_FN64_CPU_ON:
> + return pvm_psci_vcpu_on(hyp_vcpu);
> + case PSCI_0_2_FN_CPU_OFF:
> + return pvm_psci_vcpu_off(hyp_vcpu);
> + case PSCI_0_2_FN_PSCI_VERSION:
> + return pvm_psci_version(hyp_vcpu);
> + case PSCI_1_0_FN_PSCI_FEATURES:
> + return pvm_psci_features(hyp_vcpu);
> + case PSCI_0_2_FN_AFFINITY_INFO:
> + case PSCI_0_2_FN64_AFFINITY_INFO:
> + case PSCI_0_2_FN_SYSTEM_RESET:
> + case PSCI_0_2_FN_CPU_SUSPEND:
> + case PSCI_0_2_FN64_CPU_SUSPEND:
> + case PSCI_0_2_FN_SYSTEM_OFF:
> + case PSCI_1_1_FN_SYSTEM_RESET2:
> + case PSCI_1_1_FN64_SYSTEM_RESET2:
> + return false; /* Handled by the host. */
> + default:
> + /* Unknown PSCI calls are answered here, not forwarded. */
> + smccc_set_retval(vcpu, PSCI_RET_NOT_SUPPORTED, 0, 0, 0);
> + return true;
> + }
> +}
> +
> /*
> * Handler for protected VM HVC calls.
> *
> @@ -1187,6 +1460,7 @@ static void pkvm_memunshare_call(u64 *ret, struct kvm_vcpu *vcpu)
> */
> bool kvm_handle_pvm_hvc64(struct kvm_vcpu *vcpu, u64 *exit_code)
> {
> + struct pkvm_hyp_vcpu *hyp_vcpu = container_of(vcpu, struct pkvm_hyp_vcpu, vcpu);
> u64 val[4] = { SMCCC_RET_INVALID_PARAMETER };
> bool handled = true;
> u32 feature;
> @@ -1285,8 +1559,7 @@ bool kvm_handle_pvm_hvc64(struct kvm_vcpu *vcpu, u64 *exit_code)
> pkvm_memunshare_call(val, vcpu);
> break;
> default:
> - /* Punt everything else back to the host, for now. */
> - handled = false;
> + return pkvm_handle_psci(hyp_vcpu);
> }
>
> if (handled)
> --
> 2.39.5
>
--
Vincent
next prev parent reply other threads:[~2026-09-22 16:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:33 [PATCH v3 00/18] KVM: arm64: Confine protected VM vCPU state to EL2 Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 01/18] KVM: arm64: Sync HCR_EL2.VSE back to the host vCPU under pKVM Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 02/18] KVM: arm64: Validate the host vCPU's VM before reading it " Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 03/18] KVM: arm64: Pin the host vCPU before adjusting its PC " Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 04/18] KVM: arm64: Disable steal time for protected VMs Fuad Tabba
2026-09-22 14:34 ` Vincent Donnefort
2026-09-14 11:33 ` [PATCH v3 05/18] KVM: arm64: Introduce per-EC entry handlers for pKVM Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 06/18] KVM: arm64: Skip fixed-feature state flush for protected vCPUs Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 07/18] KVM: arm64: Add {flush,sync}_hyp_timer_state() primitives Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 08/18] KVM: arm64: Add system register reset framework for protected VMs Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 09/18] KVM: arm64: Implement HVC handling for protected guests at EL2 Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 10/18] KVM: arm64: Handle PSCI calls for protected VMs " Fuad Tabba
2026-09-22 16:35 ` Vincent Donnefort [this message]
2026-09-22 16:37 ` Vincent Donnefort
2026-09-22 17:07 ` Vincent Donnefort
2026-09-23 9:51 ` Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 11/18] KVM: arm64: Restrict KVM_ARM_VCPU_INIT and PSCI version for protected VMs Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 12/18] KVM: arm64: Prevent host PC adjustments for protected vCPUs Fuad Tabba
2026-09-14 13:42 ` Marc Zyngier
2026-09-14 14:43 ` Fuad Tabba
2026-09-15 11:02 ` Marc Zyngier
2026-09-15 11:19 ` Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 13/18] KVM: arm64: Inject an UNDEF at EL2 for unhandled protected guest exits Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 14/18] KVM: arm64: Add per-EC entry/exit state marshalling for protected guests Fuad Tabba
2026-09-16 16:27 ` Marc Zyngier
2026-09-16 19:05 ` Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 15/18] KVM: arm64: Reject host access to protected VM private state Fuad Tabba
2026-09-16 16:30 ` Marc Zyngier
2026-09-16 19:07 ` Fuad Tabba
2026-09-17 8:06 ` Marc Zyngier
2026-09-17 18:42 ` Fuad Tabba
2026-09-18 13:21 ` Will Deacon
2026-09-18 13:24 ` Will Deacon
2026-09-14 11:33 ` [PATCH v3 16/18] KVM: arm64: Reject host power-on of a vCPU that EL2 holds powered off Fuad Tabba
2026-09-16 16:43 ` Marc Zyngier
2026-09-16 19:08 ` Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 17/18] KVM: arm64: Advertise the capabilities that protected VMs support Fuad Tabba
2026-09-14 11:33 ` [PATCH v3 18/18] KVM: arm64: Document the protected VM userspace API Fuad Tabba
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=arKuPQ-w5EFXo-n8@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=qperret@google.com \
--cc=seiden@linux.ibm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@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
all inboxes | Powered by JetHome®