Received: by 2002:a05:6358:7058:b0:131:369:b2a3 with SMTP id 24csp6889861rwp; Tue, 18 Jul 2023 07:15:21 -0700 (PDT) X-Google-Smtp-Source: APBJJlEH2ShbPWohyB7phe270S8oXnq9b3VIychyELFs0naqPRVJNYg5ww3U/76aY+3svsOfrVac X-Received: by 2002:a05:6a00:855:b0:668:73f5:dce0 with SMTP id q21-20020a056a00085500b0066873f5dce0mr16998233pfk.29.1689689720625; Tue, 18 Jul 2023 07:15:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689689720; cv=none; d=google.com; s=arc-20160816; b=OVh8N1YIRi1FLs0Z55DlH5WffhJUBZ4SjCZFUbcI40t478K8ZYgUpFQFzfX4Ntg5tf 8Y3/AV71oeM/MrEmygGnhYSumuoJ+b9ZteMfjIZBY1R4Mzmzm3zPFnd1yGtAyGVurPUy LCdOy+lWQPEB1toiOx969D0MdzoTH4kY+1zTMwZBiAlz0sHVqADiJ903xLLkf2MLE2qM KepbafcUhJX+htSUTVB7C0EuHCAv/NiSxOqsacztwHPZatT6qtWllkX06cVvB1ewDRbT D44drR+Jv7iTLmDw+aYpXBiXvwWGdsaB1bFIh36TrveTZj39LqLPmPNclwAyELLSOd4X ffIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from :dkim-signature; bh=0hbnAtXIzLm8ZhF4zzzSfel092oo4aj0hfqqGWVouec=; fh=+xhtI/L+Xuj71uPNZC5AflMRtyY3k03T8mZbd4IgqqY=; b=JYrgyRNr/ltQStm2Qd8NL6k4a7hplZW4gDm8f3MqFD9hYAksS3NZ8aKGscs5ZKMpL+ lONAPCR+wOGUo2IpetoUMK9Rr7FlywLjgI3HCEpTjjjn6p26z3YVvy3aSasqSBE0IXRJ sCvyFQWoXEvuijjQKKzotu9iEnJ//F3pfDSopfqnD4g98XTmzfptDOnm06cHFbaETkTe yzKycvGAIK+DbiuFGU0L6yXvkzUqbWbP7XBnaSASrmsLjAXhWNxTODlvwCNQqhkS1Xj5 frNJvcGaPjuZD5Nxk6Ddq3oruIJ1nIANzt1J5NIMkB3Cx6D6gh5ualBjPh6bdxb+3ADt SXCQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TUSasU+h; 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 fj13-20020a056a003a0d00b0066aa7b0e3c8si1579276pfb.322.2023.07.18.07.15.07; Tue, 18 Jul 2023 07:15:20 -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=TUSasU+h; 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 S232728AbjGROAH (ORCPT + 99 others); Tue, 18 Jul 2023 10:00:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233094AbjGRN76 (ORCPT ); Tue, 18 Jul 2023 09:59:58 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22ACA1FD3; Tue, 18 Jul 2023 06:59:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1689688775; x=1721224775; h=from:to:cc:subject:date:message-id; bh=OMyuco3mwvaMDBboxlt2EeivPMikKBGoJTo4Mo4UuMA=; b=TUSasU+hvFVoMT6H/owPWmm9cfq3o7UgLr/njctjM7P0MEJktQm3y7RX 3ucdFQYVyZGCDlcY/vHME5hV/vYG/rT9CdaR5Ew29jDIxh3t8slJIMg9Q 5iZtjqrIHPARL2/2lUvIBdShdul6CBjs4oN3Q0qLNbVffcbtE/fyv8MoK dxB72Nsh/E/v+pNCiuBI/KP+y3FyagxmtuYNxUqU9bss8iWLWVb9/wWIk nZuiU2K1P7A6nNNGv+Jz8hs8BpFRbPsmfuPgyO/I0gJBEaHbCHxMtkaKe TlRLWyFzZ6zVo+HcvXuasWtl5TfI+ZwCQHaxPAhx2KgJMnPpWWDI635i4 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10775"; a="363676063" X-IronPort-AV: E=Sophos;i="6.01,214,1684825200"; d="scan'208";a="363676063" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2023 06:58:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10775"; a="1054291089" X-IronPort-AV: E=Sophos;i="6.01,214,1684825200"; d="scan'208";a="1054291089" Received: from arthur-vostro-3668.sh.intel.com ([10.238.200.123]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2023 06:58:37 -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, Zeng Guang Subject: [PATCH v2 0/8] LASS KVM virtualization support Date: Tue, 18 Jul 2023 21:18:36 +0800 Message-Id: <20230718131844.5706-1-guang.zeng@intel.com> X-Mailer: git-send-email 2.17.1 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED 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 Linear Address Space Separation (LASS)[1] is a new mechanism that enforces the same mode-based protections as paging, i.e. SMAP/SMEP but without traversing the paging structures. Because the protections enforced by LASS are applied before paging, "probes" by malicious software will provide no paging-based timing information. Based on a linear-address organization, 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). LASS aims to prevent any attempt to probe supervisor-mode addresses by user mode, and likewise stop any attempt to access (if SMAP enabled) or execute user-mode addresses from supervisor mode. When platform has LASS capability, KVM requires to expose this feature to guest VM enumerated by CPUID.(EAX=07H.ECX=1):EAX.LASS[bit 6], and allow guest to enable it via CR4.LASS[bit 27] on demand. For instruction executed in the guest directly, hardware will perform the check. But KVM also needs to behave same as hardware to apply LASS to kinds of guest memory accesses when emulating instructions by software. KVM will take following LASS violations check on emulation path. User-mode access to supervisor space address: LA[bit 63] && (CPL == 3) Supervisor-mode access to user space address: Instruction fetch: !LA[bit 63] && (CPL < 3) Data access: !LA[bit 63] && (CR4.SMAP==1) && ((RFLAGS.AC == 0 && CPL < 3) || Implicit supervisor access) This patch series provide a LASS KVM solution and depends on kernel enabling that can be found at https://lore.kernel.org/all/20230609183632.48706-1-alexander.shishkin@linux.intel.com/ We tested the basic function of LASS virtualization including LASS enumeration and enabling in non-root and nested environment. As KVM unittest framework is not compatible to LASS rule, we use kernel module and application test to emulate LASS violation instead. With KVM forced emulation mechanism, we also verified the LASS functionality on some emulation path with instruction fetch and data access to have same behavior as hardware. How to extend kselftest to support LASS is under investigation and experiment. [1] Intel ISE https://cdrdv2.intel.com/v1/dl/getContent/671368 Chapter Linear Address Space Separation (LASS) ------------------------------------------------------------------------ v1->v2 1. refactor and optimize the interface of instruction emulation by introducing new set of operation type definition prefixed with "X86EMUL_F_" to distinguish access. 2. reorganize the patch to make each area of KVM better isolated. 3. refine LASS violation check design with consideration of wraparound access across address space boundary. v0->v1 1. Adapt to new __linearize() API 2. Function refactor of vmx_check_lass() 3. Refine commit message to be more precise 4. Drop LASS kvm cap detection depending on hardware capability Binbin Wu (4): KVM: x86: Consolidate flags for __linearize() KVM: x86: Use a new flag for branch instructions KVM: x86: Add an emulation flag for implicit system access KVM: x86: Add X86EMUL_F_INVTLB and pass it in em_invlpg() Zeng Guang (4): KVM: emulator: Add emulation of LASS violation checks on linear address KVM: VMX: Implement and apply vmx_is_lass_violation() for LASS protection KVM: x86: Virtualize CR4.LASS KVM: x86: Advertise LASS CPUID to user space arch/x86/include/asm/kvm-x86-ops.h | 3 ++- arch/x86/include/asm/kvm_host.h | 5 +++- arch/x86/kvm/cpuid.c | 5 ++-- arch/x86/kvm/emulate.c | 37 ++++++++++++++++++++--------- arch/x86/kvm/kvm_emulate.h | 9 +++++++ arch/x86/kvm/vmx/nested.c | 3 ++- arch/x86/kvm/vmx/sgx.c | 4 ++++ arch/x86/kvm/vmx/vmx.c | 38 ++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/vmx.h | 3 +++ arch/x86/kvm/x86.c | 10 ++++++++ arch/x86/kvm/x86.h | 2 ++ 11 files changed, 102 insertions(+), 17 deletions(-) -- 2.27.0