Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp897376pxj; Wed, 16 Jun 2021 16:38:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzqkNQLXUBzFRO82STHtvTiQ5LjnOs9IYdE290EitIjTMhvwMXLO/WjfAOi5wrd3SB4//QX X-Received: by 2002:a5d:9e41:: with SMTP id i1mr1416676ioi.72.1623886708658; Wed, 16 Jun 2021 16:38:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623886708; cv=none; d=google.com; s=arc-20160816; b=RwU5bkr7tw/LiThw87+RZ3LWNq0IStxHPaFjcIggSuC/lyGBwVZbcoBj12INwIaaAx n3n+lQC+0BusCvCGIrUZ192sC3eEn8GeEhzWmgTtWMF/puks48ZjZM3wFv6bj9Oebe9L U19/33CrOPt+thG1XIw4wlGKinXDD5fhrCTJQX20IhLRtqRhd5ZodoFi/MV5H+LZYTF+ AlywAMngyHHzOJnh7RA5rK0dum6raCegEcG7a7T4Dwbe8L44tXJHOzdzZLqjYTvlhJRW CyvoXDUxRHmhQaGM2Y7XUURjL9JSHz6BPA61vuJNjWGv9MXU27Z1vWmVesumo5+bKRvz rQKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=aYMOgWXLGDXFVEbX7WxQQJfXsD7j196e7lrJp4jcufg=; b=WH+548JzJTEalrJInaNyJJC2t/5eWoLeGj12GXKtZh8AgydCy8JsrIE/Hq3ScaCmJy y9cQIZyN25Etnkpb7Ds17CriUOIueC4Ksst5G8JBB+kBjQkqi2KpZxHZbhoRqcptV2OU UMbdsth5WLkbq3n32kW3ckqA3YcMwWIZNuQElSki0xcCgkkmDLN6Ph80y8Pmy2lANd0g wvNOybF9vMH0x1AHfDOJQ0o1WCxN4u3WHKc/ZisztasHbzyoTAjYdoUyebtnJEJJWgFE V98/uCtKzsGbEVOrp03jSQ6EOGWhodqS0qHe8R8IfJnX6m/G2N+dQXSgpZ5X7DUoKYER SV5w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i9si3753605ila.58.2021.06.16.16.37.38; Wed, 16 Jun 2021 16:38:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234841AbhFPP77 (ORCPT + 99 others); Wed, 16 Jun 2021 11:59:59 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:3253 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234724AbhFPP70 (ORCPT ); Wed, 16 Jun 2021 11:59:26 -0400 Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4G4qMF2gQ0z6K6RF; Wed, 16 Jun 2021 23:47:37 +0800 (CST) Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Wed, 16 Jun 2021 17:57:18 +0200 Received: from A2006125610.china.huawei.com (10.47.83.191) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 16 Jun 2021 16:57:11 +0100 From: Shameer Kolothum To: , , CC: , , , , , , , , Subject: [PATCH v2 1/3] arch/arm64: Introduce a capability to tell whether 16-bit VMID is available Date: Wed, 16 Jun 2021 16:56:04 +0100 Message-ID: <20210616155606.2806-2-shameerali.kolothum.thodi@huawei.com> X-Mailer: git-send-email 2.12.0.windows.1 In-Reply-To: <20210616155606.2806-1-shameerali.kolothum.thodi@huawei.com> References: <20210616155606.2806-1-shameerali.kolothum.thodi@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.47.83.191] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To lhreml710-chm.china.huawei.com (10.201.108.61) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Julien Grall At the moment, the function kvm_get_vmid_bits() is looking up for the sanitized value of ID_AA64MMFR1_EL1 and extract the information regarding the number of VMID bits supported. This is fine as the function is mainly used during VMID roll-over. New use in a follow-up patch will require the function to be called a every context switch so we want the function to be more efficient. A new capability is introduced to tell whether 16-bit VMID is available. Signed-off-by: Julien Grall Signed-off-by: Shameer Kolothum --- arch/arm64/include/asm/kvm_mmu.h | 4 +--- arch/arm64/kernel/cpufeature.c | 9 +++++++++ arch/arm64/tools/cpucaps | 1 + 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/arch/arm64/include/asm/kvm_mmu.h b/arch/arm64/include/asm/kvm_mmu.h index 25ed956f9af1..2abdea7dcb43 100644 --- a/arch/arm64/include/asm/kvm_mmu.h +++ b/arch/arm64/include/asm/kvm_mmu.h @@ -223,9 +223,7 @@ void kvm_toggle_cache(struct kvm_vcpu *vcpu, bool was_enabled); static inline unsigned int kvm_get_vmid_bits(void) { - int reg = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1); - - return get_vmid_bits(reg); + return cpus_have_const_cap(ARM64_HAS_16BIT_VMID) ? 16 : 8; } /* diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index efed2830d141..0642ebe118b0 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -2218,6 +2218,15 @@ static const struct arm64_cpu_capabilities arm64_features[] = { .matches = has_cpuid_feature, .min_field_value = 1, }, + { + .capability = ARM64_HAS_16BIT_VMID, + .type = ARM64_CPUCAP_SYSTEM_FEATURE, + .sys_reg = SYS_ID_AA64MMFR1_EL1, + .field_pos = ID_AA64MMFR1_VMIDBITS_SHIFT, + .sign = FTR_UNSIGNED, + .min_field_value = ID_AA64MMFR1_VMIDBITS_16, + .matches = has_cpuid_feature, + }, {}, }; diff --git a/arch/arm64/tools/cpucaps b/arch/arm64/tools/cpucaps index 21fbdda7086e..456b4cf1ba27 100644 --- a/arch/arm64/tools/cpucaps +++ b/arch/arm64/tools/cpucaps @@ -3,6 +3,7 @@ # Internal CPU capabilities constants, keep this list sorted BTI +HAS_16BIT_VMID HAS_32BIT_EL0 HAS_32BIT_EL1 HAS_ADDRESS_AUTH -- 2.17.1