Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp870698rwr; Thu, 20 Apr 2023 07:19:10 -0700 (PDT) X-Google-Smtp-Source: AKy350Y0p1cNXg+EEwGLCQ/cp9aygZc5HE9kkxeS1R1qDMCIPaQ2AeRei/WEhXlbJJSr5/WwM1Dq X-Received: by 2002:a05:6a00:808:b0:63d:38db:60ef with SMTP id m8-20020a056a00080800b0063d38db60efmr1549544pfk.26.1682000349648; Thu, 20 Apr 2023 07:19:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682000349; cv=none; d=google.com; s=arc-20160816; b=JTCS2drTXhL58MwGNx1jV5Csl5B+8+7oH6PMiKao5gSlskhzszZ5adKCwWlIOqaAEM bQZV/b5FPJWlOnyLopkFMZT7hzC3c581wQjVoN+lYcgUWcTeBKLkuSfBjS2zRlyYa2C8 Do2D5VxTdrX4m7lvJeNWDFV9LhLSu0zIClVL2jZRxlgQo6qTv4bGg+todPdrmBce0HK4 qt734wEOQIzgUDRqfIA2lJ4jAZeumaUknVWvImTqHSGNlRvVtU/QEixVass0LqhyYdVC ydAcJOmKMaxh6X9YdYdkviSNgwOWRLdy5KYuNMh1ODoZRr5t1sdhow8PtKGZ7gyxQbOI C+Ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from:dkim-signature; bh=K6kMkiob2g08Hj/xrUVhMCA82YbCGmDKJqTKusyQGVc=; b=IgiOScVSfpPYTsTBvBJG0Rbrlx4jCthaGzt7Yip1PBhwG+siDZGy3GbLfUTPwPblsV i0FawnWy3qSf9BLiAXTt4CvLk8J1gJuS4ju49IKdBKF0GwPEYkOPvMOYIYbJB/jd3XYx Lrx8kC2iWLwQpb2e+vp/SDgA81KtHkFNWoTHdQ+Jw/Ak0J0IbadZXW4M+wt6w25IDkPv JaLbbERIPfRNPOvBn9v34wqUm/rmaDDhHIOFh7H877qx3avA/LZ0lfiNAEg7Z8yZFHzx KOabJfOReQQLiUjnum82tXlJy0YdY9pPF8Da9l+XEWAHsLyUXaqP2Su8ljGixGIg0NBP S6CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="ADzl7iY/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 79-20020a621952000000b0063d6708d1c9si1726557pfz.105.2023.04.20.07.18.56; Thu, 20 Apr 2023 07:19:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="ADzl7iY/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232023AbjDTOQ0 (ORCPT + 99 others); Thu, 20 Apr 2023 10:16:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231933AbjDTOQR (ORCPT ); Thu, 20 Apr 2023 10:16:17 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1349A449D; Thu, 20 Apr 2023 07:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1682000176; x=1713536176; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=8vcqBoPnJSsP+PR1vJco3USQMMRGQCpM1hb/P9YwlSA=; b=ADzl7iY/e2QalQndR+u7ksiViYrax1kHYFcrYyBakxt5E6xxOO4UIoDQ ZpCixLwPLvwrQZHj8XVsK4asqZR9riZUcbU5eykkxDn3Ibcupv98kaHkr iwAdL3FyGrKo/KN+vvs4IRvIVLSpG9QBduMS/ff/renm/G4aQ/wO1g0+L VFtvtA+jbmhFR9c6OJPO6eH2NumFywRit6twF73GosmwB1dFws3QMQFxQ GEKmyEWi2aSi8qmgP+qYAXtElo9c3YI1YC7ovSRruAKt312qMuxSXqlRD K3r2o7YAkq9jj3lB19EuLLsayhC2WSodf0hdbTiYbnSrJxrxwz6wfccDW Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10686"; a="343217803" X-IronPort-AV: E=Sophos;i="5.99,212,1677571200"; d="scan'208";a="343217803" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2023 07:16:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10686"; a="816028837" X-IronPort-AV: E=Sophos;i="5.99,212,1677571200"; d="scan'208";a="816028837" Received: from arthur-vostro-3668.sh.intel.com ([10.238.200.53]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2023 07:16:03 -0700 From: Zeng Guang To: Paolo Bonzini , Sean Christopherson , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , H Peter Anvin , kvm@vger.kernel.org Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Gao Chao , Zeng Guang Subject: [PATCH 2/6] KVM: VMX: Add new ops in kvm_x86_ops for LASS violation check Date: Thu, 20 Apr 2023 21:37:20 +0800 Message-Id: <20230420133724.11398-3-guang.zeng@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20230420133724.11398-1-guang.zeng@intel.com> References: <20230420133724.11398-1-guang.zeng@intel.com> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Intel introduce LASS (Linear Address Separation) feature providing an independent mechanism to achieve the mode-based protection. LASS partitions 64-bit linear address space into two halves, user-mode address (LA[bit 63]=0) and supervisor-mode address (LA[bit 63]=1). It stops any code execution or data access 1. from user mode to supervisor-mode address space 2. from supervisor mode to user-mode address space and generates LASS violation fault accordingly. A supervisor mode data access causes a LASS violation only if supervisor mode access protection is enabled (CR4.SMAP = 1) and either RFLAGS.AC = 0 or the access implicitly accesses a system data structure. Following are the rule of LASS violation check on the linear address(LA). User access to supervisor-mode address space: LA[bit 63] && (CPL == 3) Supervisor access to user-mode address space: Instruction fetch: !LA[bit 63] && (CPL < 3) Data access: !LA[bit 63] && (CR4.SMAP==1) && ((RFLAGS.AC == 0 && CPL < 3) || Implicit supervisor access) Add new ops in kvm_x86_ops to do LASS violation check. Signed-off-by: Zeng Guang --- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 5 +++ arch/x86/kvm/vmx/vmx.c | 55 ++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/vmx.h | 2 ++ 4 files changed, 63 insertions(+) diff --git a/arch/x86/include/asm/kvm-x86-ops.h b/arch/x86/include/asm/kvm-x86-ops.h index abccd51dcfca..f76c07f2674b 100644 --- a/arch/x86/include/asm/kvm-x86-ops.h +++ b/arch/x86/include/asm/kvm-x86-ops.h @@ -131,6 +131,7 @@ KVM_X86_OP(msr_filter_changed) KVM_X86_OP(complete_emulated_msr) KVM_X86_OP(vcpu_deliver_sipi_vector) KVM_X86_OP_OPTIONAL_RET0(vcpu_get_apicv_inhibit_reasons); +KVM_X86_OP_OPTIONAL_RET0(check_lass); #undef KVM_X86_OP #undef KVM_X86_OP_OPTIONAL diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h index 8ff89a52ef66..31fb8699a1ff 100644 --- a/arch/x86/include/asm/kvm_host.h +++ b/arch/x86/include/asm/kvm_host.h @@ -69,6 +69,9 @@ #define KVM_X86_NOTIFY_VMEXIT_VALID_BITS (KVM_X86_NOTIFY_VMEXIT_ENABLED | \ KVM_X86_NOTIFY_VMEXIT_USER) +/* x86-specific emulation flags */ +#define KVM_X86_EMULFLAG_SKIP_LASS _BITULL(1) + /* x86-specific vcpu->requests bit members */ #define KVM_REQ_MIGRATE_TIMER KVM_ARCH_REQ(0) #define KVM_REQ_REPORT_TPR_ACCESS KVM_ARCH_REQ(1) @@ -1706,6 +1709,8 @@ struct kvm_x86_ops { * Returns vCPU specific APICv inhibit reasons */ unsigned long (*vcpu_get_apicv_inhibit_reasons)(struct kvm_vcpu *vcpu); + + bool (*check_lass)(struct kvm_vcpu *vcpu, u64 access, u64 la, u64 flags); }; struct kvm_x86_nested_ops { diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c index c923d7599d71..581327ede66a 100644 --- a/arch/x86/kvm/vmx/vmx.c +++ b/arch/x86/kvm/vmx/vmx.c @@ -8070,6 +8070,59 @@ static void vmx_vm_destroy(struct kvm *kvm) free_pages((unsigned long)kvm_vmx->pid_table, vmx_get_pid_table_order(kvm)); } +/* + * Determine whether an access to the linear address causes a LASS violation. + * LASS protection is only effective in long mode. As a prerequisite, caller + * should make sure VM running in long mode and invoke this api to do LASS + * violation check. + */ +bool __vmx_check_lass(struct kvm_vcpu *vcpu, u64 access, u64 la, u64 flags) +{ + bool user_mode, user_as, rflags_ac; + + if (!!(flags & KVM_X86_EMULFLAG_SKIP_LASS) || + !kvm_is_cr4_bit_set(vcpu, X86_CR4_LASS)) + return false; + + WARN_ON_ONCE(!is_long_mode(vcpu)); + + user_as = !(la >> 63); + + /* + * An access is a supervisor-mode access if CPL < 3 or if it implicitly + * accesses a system data structure. For implicit accesses to system + * data structure, the processor acts as if RFLAGS.AC is clear. + */ + if (access & PFERR_IMPLICIT_ACCESS) { + user_mode = false; + rflags_ac = false; + } else { + user_mode = vmx_get_cpl(vcpu) == 3; + if (!user_mode) + rflags_ac = !!(kvm_get_rflags(vcpu) & X86_EFLAGS_AC); + } + + if (user_mode != user_as) { + /* + * Supervisor-mode _data_ accesses to user address space + * cause LASS violations only if SMAP is enabled. + */ + if (!user_mode && !(access & PFERR_FETCH_MASK)) { + return kvm_is_cr4_bit_set(vcpu, X86_CR4_SMAP) && + !rflags_ac; + } else { + return true; + } + } + + return false; +} + +static bool vmx_check_lass(struct kvm_vcpu *vcpu, u64 access, u64 la, u64 flags) +{ + return is_long_mode(vcpu) && __vmx_check_lass(vcpu, access, la, flags); +} + static struct kvm_x86_ops vmx_x86_ops __initdata = { .name = "kvm_intel", @@ -8207,6 +8260,8 @@ static struct kvm_x86_ops vmx_x86_ops __initdata = { .complete_emulated_msr = kvm_complete_insn_gp, .vcpu_deliver_sipi_vector = kvm_vcpu_deliver_sipi_vector, + + .check_lass = vmx_check_lass, }; static unsigned int vmx_handle_intel_pt_intr(void) diff --git a/arch/x86/kvm/vmx/vmx.h b/arch/x86/kvm/vmx/vmx.h index a3da84f4ea45..6569385a5978 100644 --- a/arch/x86/kvm/vmx/vmx.h +++ b/arch/x86/kvm/vmx/vmx.h @@ -433,6 +433,8 @@ void vmx_enable_intercept_for_msr(struct kvm_vcpu *vcpu, u32 msr, int type); u64 vmx_get_l2_tsc_offset(struct kvm_vcpu *vcpu); u64 vmx_get_l2_tsc_multiplier(struct kvm_vcpu *vcpu); +bool __vmx_check_lass(struct kvm_vcpu *vcpu, u64 access, u64 la, u64 flags); + static inline void vmx_set_intercept_for_msr(struct kvm_vcpu *vcpu, u32 msr, int type, bool value) { -- 2.27.0