Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932189AbdG3UA0 (ORCPT ); Sun, 30 Jul 2017 16:00:26 -0400 Received: from mail-wm0-f43.google.com ([74.125.82.43]:37864 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932146AbdG3UAW (ORCPT ); Sun, 30 Jul 2017 16:00:22 -0400 Date: Sun, 30 Jul 2017 22:00:20 +0200 From: Christoffer Dall To: Jintack Lim Cc: kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org, marc.zyngier@arm.com, corbet@lwn.net, pbonzini@redhat.com, rkrcmar@redhat.com, linux@armlinux.org.uk, catalin.marinas@arm.com, will.deacon@arm.com, akpm@linux-foundation.org, mchehab@kernel.org, cov@codeaurora.org, daniel.lezcano@linaro.org, david.daney@cavium.com, mark.rutland@arm.com, suzuki.poulose@arm.com, stefan@hello-penguin.com, andy.gross@linaro.org, wcohen@redhat.com, ard.biesheuvel@linaro.org, shankerd@codeaurora.org, vladimir.murzin@arm.com, james.morse@arm.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH v2 22/38] KVM: arm64: Handle PSCI call via smc from the guest Message-ID: <20170730200020.GL5176@cbox> References: <1500397144-16232-1-git-send-email-jintack.lim@linaro.org> <1500397144-16232-23-git-send-email-jintack.lim@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1500397144-16232-23-git-send-email-jintack.lim@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2312 Lines: 72 On Tue, Jul 18, 2017 at 11:58:48AM -0500, Jintack Lim wrote: > VMs used to execute hvc #0 for the psci call if EL3 is not implemented. > However, when we come to provide the virtual EL2 mode to the VM, the > host OS inside the VM calls kvm_call_hyp() which is also hvc #0. So, > it's hard to differentiate between them from the host hypervisor's point > of view. This is a bit confusing. I think you should just refer to the fact that the architecture requires HVC calls to be handled at EL2, and when emulating EL2 inside the VM, HVC calls from the VM are handled by the VM itself, and therefore we add the support for SMC as the conduit for PSCI calls. > > So, let the VM execute smc instruction for the psci call. On ARMv8.3, > even if EL3 is not implemented, a smc instruction executed at non-secure > EL1 is trapped to EL2 if HCR_EL2.TSC==1, rather than being treated as > UNDEFINED. So, the host hypervisor can handle this psci call without any > confusion. > > Signed-off-by: Jintack Lim > --- > arch/arm64/kvm/handle_exit.c | 24 ++++++++++++++++++++++-- > 1 file changed, 22 insertions(+), 2 deletions(-) > > diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c > index d19e253..6cf6b93 100644 > --- a/arch/arm64/kvm/handle_exit.c > +++ b/arch/arm64/kvm/handle_exit.c > @@ -53,8 +53,28 @@ static int handle_hvc(struct kvm_vcpu *vcpu, struct kvm_run *run) > > static int handle_smc(struct kvm_vcpu *vcpu, struct kvm_run *run) > { > - kvm_inject_undefined(vcpu); > - return 1; > + int ret; > + > + /* If imm is non-zero, it's not defined */ > + if (kvm_vcpu_hvc_get_imm(vcpu)) { > + kvm_inject_undefined(vcpu); > + return 1; > + } > + > + /* > + * If imm is zero, it's a psci call. That's only a necessary, but not sufficient requirement. So we should say, it may be a PSCI call or we check if it's a PSCI call... > + * Note that on ARMv8.3, even if EL3 is not implemented, SMC executed > + * at Non-secure EL1 is trapped to EL2 if HCR_EL2.TSC==1, rather than > + * being treated as UNDEFINED. > + */ > + ret = kvm_psci_call(vcpu); > + if (ret < 0) { > + kvm_inject_undefined(vcpu); > + return 1; > + } > + kvm_skip_instr(vcpu, kvm_vcpu_trap_il_is32bit(vcpu)); > + > + return ret; > } > > /* > -- > 1.9.1 > Thanks, -Christoffer