Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp222991imb; Thu, 28 Feb 2019 22:00:12 -0800 (PST) X-Google-Smtp-Source: APXvYqyzwsT5Hp6mvvR6eZdZ4wxDLo/QrGtc9FQqoHajhYAgbz70YQ7lFM6o2MbWiSncuMcusBYA X-Received: by 2002:a17:902:b486:: with SMTP id y6mr3741722plr.104.1551420012102; Thu, 28 Feb 2019 22:00:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551420012; cv=none; d=google.com; s=arc-20160816; b=FawjNw7Lj/GVkuzSqJR5nb1j7Z2L4yHd2iYnRE91Z4wv0UmKH4Rs/tqsBpUpuudWWU O/xlgCej4eddwLJbfQkXFx0SwmXUp968IUpZVzGU8rVHTGu0IQlnsHm1o/f+Et9aFQl4 oMS5c2JqG657M1+Aqoi7pcNM5KxMu0f8gN1Bo92+X2RurX/h5ySGIohckvWXZs2CZi9B yAgA25C7iHDyQKSXkdautG7nK512ShATwRI9e0O1eaid0nl6kvQt4MKdcVTemdnHQ0s2 gqyov3hZ/G5OD1Y9gMgjpxrfnnSse7uPkLSzKszXbZS5fF2XVt96b6i6WqDHIXmQDQMJ b7MQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Xb1T3mvm8ivBV5tHNqHgxTRyqbIUqFQTX12klcCPvaM=; b=WjuGw9LCa+KqTz/hIB1W6D0IFc2bcWHu2V99l6wbtlJZ9DVuMawnTnmk76dMr8JRRu +JQ7iu5RpPzx9wekorZCYzzS8XjGaHuPq5elFvOPrlrfJkNyCciB+YTyIGBb+lVK5SGN wtYZgwTVDRdu3kztMzHfdQgb3UAKRSTvrUPlkzfz5AVOG5ltE30dCaTR3u9KFLbObMGs KnpezoJK+LbnbqFApJBWQO1X4Ablb7MHxS4u1cXfPhbMVJ4aZk9m+XJpUYDeVzVzb4Yt SvUoUS7Y83fwQPM3CavZiqER2+XVcrP1ygBqs0jFccRp70s/XbgtGAnAkLnQ+arUQzyr fDfA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cn17si21114021plb.139.2019.02.28.21.59.56; Thu, 28 Feb 2019 22:00:12 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727938AbfCAF4M (ORCPT + 99 others); Fri, 1 Mar 2019 00:56:12 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:58076 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726207AbfCAF4L (ORCPT ); Fri, 1 Mar 2019 00:56:11 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 44BB6EBD; Thu, 28 Feb 2019 21:56:11 -0800 (PST) Received: from [10.162.0.144] (a075553-lin.blr.arm.com [10.162.0.144]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 981BF3F5C1; Thu, 28 Feb 2019 21:56:08 -0800 (PST) Subject: Re: [PATCH v6 1/6] arm64/kvm: preserve host HCR_EL2 value To: Dave Martin Cc: linux-arm-kernel@lists.infradead.org, Marc Zyngier , Catalin Marinas , Will Deacon , Kristina Martsenko , kvmarm@lists.cs.columbia.edu, Ramana Radhakrishnan , linux-kernel@vger.kernel.org References: <1550568271-5319-1-git-send-email-amit.kachhap@arm.com> <1550568271-5319-2-git-send-email-amit.kachhap@arm.com> <20190221154935.GU3567@e103592.cambridge.arm.com> From: Amit Daniel Kachhap Message-ID: Date: Fri, 1 Mar 2019 11:26:05 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190221154935.GU3567@e103592.cambridge.arm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 2/21/19 9:19 PM, Dave Martin wrote: > On Tue, Feb 19, 2019 at 02:54:26PM +0530, Amit Daniel Kachhap wrote: >> From: Mark Rutland >> >> When restoring HCR_EL2 for the host, KVM uses HCR_HOST_VHE_FLAGS, which >> is a constant value. This works today, as the host HCR_EL2 value is >> always the same, but this will get in the way of supporting extensions >> that require HCR_EL2 bits to be set conditionally for the host. >> >> To allow such features to work without KVM having to explicitly handle >> every possible host feature combination, this patch has KVM save/restore >> for the host HCR when switching to/from a guest HCR. The saving of the >> register is done once during cpu hypervisor initialization state and is >> just restored after switch from guest. >> >> For fetching HCR_EL2 during kvm initialisation, a hyp call is made using >> kvm_call_hyp and is helpful in NHVE case. > > Minor nit: NVHE misspelled. This looks a bit like it's naming an arch > feature rather than a kernel implementation detail though. Maybe write > "non-VHE". yes. > >> For the hyp TLB maintenance code, __tlb_switch_to_host_vhe() is updated >> to toggle the TGE bit with a RMW sequence, as we already do in >> __tlb_switch_to_guest_vhe(). >> >> The value of hcr_el2 is now stored in struct kvm_cpu_context as both host >> and guest can now use this field in a common way. >> >> Signed-off-by: Mark Rutland >> [Added __cpu_copy_hyp_conf, hcr_el2 field in struct kvm_cpu_context] >> Signed-off-by: Amit Daniel Kachhap >> Cc: Marc Zyngier >> Cc: Christoffer Dall >> Cc: kvmarm@lists.cs.columbia.edu >> --- >> arch/arm/include/asm/kvm_host.h | 2 ++ >> arch/arm64/include/asm/kvm_asm.h | 2 ++ >> arch/arm64/include/asm/kvm_emulate.h | 22 +++++++++++----------- >> arch/arm64/include/asm/kvm_host.h | 13 ++++++++++++- >> arch/arm64/include/asm/kvm_hyp.h | 2 +- >> arch/arm64/kvm/guest.c | 2 +- >> arch/arm64/kvm/hyp/switch.c | 23 +++++++++++++---------- >> arch/arm64/kvm/hyp/sysreg-sr.c | 21 ++++++++++++++++++++- >> arch/arm64/kvm/hyp/tlb.c | 6 +++++- >> virt/kvm/arm/arm.c | 1 + >> 10 files changed, 68 insertions(+), 26 deletions(-) >> >> diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h >> index ca56537..05706b4 100644 >> --- a/arch/arm/include/asm/kvm_host.h >> +++ b/arch/arm/include/asm/kvm_host.h >> @@ -273,6 +273,8 @@ static inline void __cpu_init_stage2(void) >> kvm_call_hyp(__init_stage2_translation); >> } >> >> +static inline void __cpu_copy_hyp_conf(void) {} >> + >> static inline int kvm_arch_vm_ioctl_check_extension(struct kvm *kvm, long ext) >> { >> return 0; >> diff --git a/arch/arm64/include/asm/kvm_asm.h b/arch/arm64/include/asm/kvm_asm.h >> index f5b79e9..8acd73f 100644 >> --- a/arch/arm64/include/asm/kvm_asm.h >> +++ b/arch/arm64/include/asm/kvm_asm.h >> @@ -80,6 +80,8 @@ extern void __vgic_v3_init_lrs(void); >> >> extern u32 __kvm_get_mdcr_el2(void); >> >> +extern void __kvm_populate_host_regs(void); >> + >> /* Home-grown __this_cpu_{ptr,read} variants that always work at HYP */ >> #define __hyp_this_cpu_ptr(sym) \ >> ({ \ >> diff --git a/arch/arm64/include/asm/kvm_emulate.h b/arch/arm64/include/asm/kvm_emulate.h >> index 506386a..0dbe795 100644 >> --- a/arch/arm64/include/asm/kvm_emulate.h >> +++ b/arch/arm64/include/asm/kvm_emulate.h >> @@ -50,25 +50,25 @@ void kvm_inject_pabt32(struct kvm_vcpu *vcpu, unsigned long addr); >> >> static inline bool vcpu_el1_is_32bit(struct kvm_vcpu *vcpu) >> { >> - return !(vcpu->arch.hcr_el2 & HCR_RW); >> + return !(vcpu->arch.ctxt.hcr_el2 & HCR_RW); > > Putting hcr_el2 into struct kvm_cpu_context creates a lot of splatter > here, and I'm wondering whether it's really necessary. Otherwise, > we could just put the per-vcpu guest HCR_EL2 value in struct > kvm_vcpu_arch. I did like that in V4 version [1] but comments were raised that this was repetition of hcr_el2 field in 2 places and may be avoided. [1]: https://lkml.org/lkml/2019/1/4/433 > > Is the *host* hcr_el2 value really different per-vcpu? That looks > odd. I would have thought this is fixed across the system at KVM > startup time. > > Having a single global host hcr_el2 would also avoid the need for > __kvm_populate_host_regs(): instead, we just decide what HCR_EL2 is to > be ahead of time and set a global variable that we map into Hyp. > > > Or does the host HCR_EL2 need to vary at runtime for some reason I've > missed? This patch basically makes host hcr_el2 not to use fixed values like HCR_HOST_NVHE_FLAGS/HCR_HOST_VHE_FLAGS during context switch and hence saves those values at boot time. This patch is just preparation to configure host hcr_el2 dynamically. However currently it is same for all cpus. I suppose it is better to have host hcr_el2 as percpu to take care of heterogeneous systems. Currently even host mdcr_el2 is stored on percpu basis(arch/arm64/kvm/debug.c). > > [...] > > +void __hyp_text __kvm_populate_host_regs(void) > +{ > + struct kvm_cpu_context *host_ctxt; > + > + if (has_vhe()) > + host_ctxt = this_cpu_ptr(&kvm_host_cpu_state); > + else > + host_ctxt = __hyp_this_cpu_ptr(kvm_host_cpu_state); > > According to the comment by the definition of __hyp_this_cpu_ptr(), this > always works at Hyp. I also see other calls with no fallback > this_cpu_ptr() call like we have here. > > So, can we simply always call __hyp_this_cpu_ptr() here? Yes i missed this. Thanks, Amit D > > (I'm not familiar with this, myself.) > > Cheers > ---Dave >