Received: by 10.213.65.68 with SMTP id h4csp3620768imn; Tue, 3 Apr 2018 08:03:47 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+FGlrEFjFRcxK1DOX4uZXEPSEzf31QoOSpjU3f0oE185996K7SWShwgFU8ctXZGh6upkIL X-Received: by 10.98.34.3 with SMTP id i3mr9280447pfi.203.1522767827294; Tue, 03 Apr 2018 08:03:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522767827; cv=none; d=google.com; s=arc-20160816; b=eaRyF5XjdsoFDIQRd7zWR+SpNtHQ8bh/1bKssh55iULRXPAASlvRbvm/teXg5bxV/3 8XT2JhQfbJFRzv1PmDiNImzbgdlMZyJEmkUw8pcAzGU9votMDIN0J2RcubCUVg6D2qTv 1nZaacdvoX6V38PmGUcBFM+tzPjgtxuSk/VbikhOdl2/lAr6enoTTESXX/pAwTz6pS13 hvhbo9leZZpHrL4XxRNWV7Pddj8dJM9uYcLGxsHCSSuAVWYYiIKlDz09nnlF3CtKndRJ HfTeM7CATlFyn337/tAmUlJ32W165NeOdhGZbZLWm85Q1M/WERMVv+21yi1HQBnjST5Z 5pOA== 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:arc-authentication-results; bh=UuraMJtCbmENPXS5AzFB2bkG2J564t7SAwwqPnAOWLE=; b=uNVIlT/kV676nRkj6MadpM61+fy6DL0g0ELZoF3hGYMIHaG9bmt34SEqeIXjiLx13I vk4IBa6R5fYs/lN/w35GxiOwhMLWpVQBiwnR5qnGpkx7xLWqStMF9ut1jytjK5n+flTF WMcXL6dMdfWrX1h8j7iUGQWerObVh00N5t9sXGYSzXj9/3jG5Z6SuJ7MTtxDwoUVfuPv e+rZLBFjw3V2KW7AKpnWF01sJEMOKh9buvP26bzFfdb60reWrZr5a0oNfQcoJklD8n2O +9aw7bU4ts66eWUwg8bgLhlSYgGV6S1F6LEPwUuPOIeczj4Y2ZG+HIEXDBqZklqN7cQv vkPg== 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 u9si2068046pgc.790.2018.04.03.08.03.29; Tue, 03 Apr 2018 08:03:47 -0700 (PDT) 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 S1751700AbeDCPBc (ORCPT + 99 others); Tue, 3 Apr 2018 11:01:32 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:33790 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751312AbeDCPBa (ORCPT ); Tue, 3 Apr 2018 11:01:30 -0400 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 3ED481529; Tue, 3 Apr 2018 08:01:30 -0700 (PDT) Received: from [10.1.207.55] (melchizedek.cambridge.arm.com [10.1.207.55]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A581A3F24A; Tue, 3 Apr 2018 08:01:27 -0700 (PDT) Subject: Re: [PATCH v2 11/17] kvm: arm64: Configure VTCR per VM To: Suzuki K Poulose Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, cdall@kernel.org, marc.zyngier@arm.com, punit.agrawal@arm.com, will.deacon@arm.com, catalin.marinas@arm.com, pbonzini@redhat.com, rkrcmar@redhat.com, ard.biesheuvel@linaro.org, peter.maydell@linaro.org, kristina.martsenko@arm.com, mark.rutland@arm.com References: <1522156531-28348-1-git-send-email-suzuki.poulose@arm.com> <1522156531-28348-12-git-send-email-suzuki.poulose@arm.com> From: James Morse Message-ID: Date: Tue, 3 Apr 2018 15:58:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1522156531-28348-12-git-send-email-suzuki.poulose@arm.com> Content-Type: text/plain; charset=utf-8 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 Suzuki, On 27/03/18 14:15, Suzuki K Poulose wrote: > We set VTCR_EL2 very early during the stage2 init and don't > touch it ever. This is fine as we had a fixed IPA size. This > patch changes the behavior to set the VTCR for a given VM, > depending on its stage2 table. The common configuration for > VTCR is still performed during the early init as we have to > retain the hardware access flag update bits (VTCR_EL2_HA) > per CPU (as they are only set for the CPUs which are capabile). (Nit: capable) > The bits defining the number of levels in the page table (SL0) > and and the size of the Input address to the translation (T0SZ) > are programmed for each VM upon entry to the guest. > diff --git a/arch/arm64/kvm/hyp/switch.c b/arch/arm64/kvm/hyp/switch.c > index 870f4b1..5ccd3ae 100644 > --- a/arch/arm64/kvm/hyp/switch.c > +++ b/arch/arm64/kvm/hyp/switch.c > @@ -164,6 +164,12 @@ static void __hyp_text __deactivate_traps(struct kvm_vcpu *vcpu) > static void __hyp_text __activate_vm(struct kvm_vcpu *vcpu) > { > struct kvm *kvm = kern_hyp_va(vcpu->kvm); > + u64 vtcr = read_sysreg(vtcr_el2); > + > + vtcr &= ~VTCR_EL2_PRIVATE_MASK; > + vtcr |= VTCR_EL2_SL0(kvm_stage2_levels(kvm)) | > + VTCR_EL2_T0SZ(kvm_phys_shift(kvm)); > + write_sysreg(vtcr, vtcr_el2); > write_sysreg(kvm->arch.vttbr, vttbr_el2); > } Do we need to set this register for tlb maintenance too? e.g. tlbi for a 3-level-stage2 vm when a 2-level-stage2 vm's vtcr is loaded... (The ARM-ARM has 'Any of the bits of VTCR_EL2 are permitted to be cached in a TLB'.) Thanks, James