TDX initialization + vCPU/VM creation
Paolo Bonzini
maintainerv3 cover TDX initialization + vCPU/VM creation
Hi,
Here is v3 of TDX VM/vCPU creation series, which Rick and others from Intel have handed off to me.
The only remaining snag could be the retry loop around some SEAMCALLS. It's likely that it can be dropped but I have left it in place for now, waiting for Yan's patient advice. :)
I dropped support for CET/PT in trusted domains, as well as for TDX modules without MD_FIELD_ID_FEATURES0_TOPOLOGY_ENUM. I have also added to the end a patch that I scavenged from the Intel tree to add support for the misc cgroup.
All non-KVM patches have been acked, except for 07/29 ("x86/virt/tdx:
allocate tdx_sys_info in static memory").
This series is based straight off of Linux 6.14-rc3. It requires TDX module 1.5.06 or later.
Paolo
Isaku Yamahata (13):
x86/virt/tdx: Add tdx_guest_keyid_alloc/free() to alloc and free TDX
guest KeyID
KVM: TDX: Add placeholders for TDX VM/vCPU structures
KVM: TDX: Define TDX architectural definitions
KVM: TDX: Add helper functions to print TDX SEAMCALL error
KVM: TDX: Add place holder for TDX VM specific mem_enc_op ioctl
KVM: TDX: Get system-wide info about TDX module on initialization
KVM: TDX: create/destroy VM structure
KVM: TDX: Support per-VM KVM_CAP_MAX_VCPUS extension check
KVM: TDX: initialize VM with TDX specific parameters
KVM: TDX: Make pmu_intel.c ignore guest TD case
KVM: TDX: Don't offline the last cpu of one package when there's TDX
guest
KVM: TDX: create/free TDX vcpu structure
KVM: TDX: Do TDX specific vcpu initialization
Kai Huang (5):
x86/virt/tdx: Read essential global metadata for KVM
KVM: Export hardware virtualization enabling/disabling functions
KVM: VMX: Refactor VMX module init/exit functions
KVM: VMX: Initialize TDX during KVM module load
KVM: TDX: Get TDX global information
Paolo Bonzini (2):
x86/virt/tdx: allocate tdx_sys_info in static memory
KVM: x86: expose cpuid_entry2_find for TDX
Rick Edgecombe (6):
x86/virt/tdx: Add SEAMCALL wrappers for TDX KeyID management x86/virt/tdx: Add SEAMCALL wrappers for TDX TD creation x86/virt/tdx: Add SEAMCALL wrappers for TDX vCPU creation x86/virt/tdx: Add SEAMCALL wrappers for TDX page cache management x86/virt/tdx: Add SEAMCALL wrappers for TDX VM/vCPU field access x86/virt/tdx: Add SEAMCALL wrappers for TDX flush operations
Sean Christopherson (1):
KVM: TDX: Add TDX "architectural" error codes
Xiaoyao Li (2):
KVM: x86: Introduce KVM_TDX_GET_CPUID
KVM: x86/mmu: Taking guest pa into consideration when calculate tdp
level
Zhiming Hu (1):
KVM: TDX: Register TDX host key IDs to cgroup misc controller
arch/x86/include/asm/kvm-x86-ops.h | 4 +-
arch/x86/include/asm/kvm_host.h | 2 +
arch/x86/include/asm/shared/tdx.h | 7 +-
arch/x86/include/asm/tdx.h | 59 +
.../tdx => include/asm}/tdx_global_metadata.h | 19 +
arch/x86/include/uapi/asm/kvm.h | 60 +
arch/x86/kvm/Kconfig | 12 +
arch/x86/kvm/Makefile | 1 +
arch/x86/kvm/cpuid.c | 33 +-
arch/x86/kvm/cpuid.h | 3 +
arch/x86/kvm/lapic.c | 1 +
arch/x86/kvm/mmu/mmu.c | 9 +-
arch/x86/kvm/vmx/main.c | 180 +-
arch/x86/kvm/vmx/pmu_intel.c | 52 +-
arch/x86/kvm/vmx/pmu_intel.h | 28 +
arch/x86/kvm/vmx/tdx.c | 1557 +++++++++++++++++
arch/x86/kvm/vmx/tdx.h | 90 +
arch/x86/kvm/vmx/tdx_arch.h | 130 ++
arch/x86/kvm/vmx/tdx_errno.h | 37 +
arch/x86/kvm/vmx/vmx.c | 25 +-
arch/x86/kvm/vmx/vmx.h | 37 +-
arch/x86/kvm/vmx/x86_ops.h | 24 +
arch/x86/kvm/x86.c | 14 +-
arch/x86/virt/vmx/tdx/tdx.c | 276 ++-
arch/x86/virt/vmx/tdx/tdx.h | 39 +-
arch/x86/virt/vmx/tdx/tdx_global_metadata.c | 50 +
include/linux/kvm_host.h | 9 +
include/linux/misc_cgroup.h | 4 +
kernel/cgroup/misc.c | 4 +
virt/kvm/kvm_main.c | 21 +-
30 files changed, 2681 insertions(+), 106 deletions(-)
rename arch/x86/{virt/vmx/tdx => include/asm}/tdx_global_metadata.h (58%)
create mode 100644 arch/x86/kvm/vmx/pmu_intel.h
create mode 100644 arch/x86/kvm/vmx/tdx.c
create mode 100644 arch/x86/kvm/vmx/tdx.h
create mode 100644 arch/x86/kvm/vmx/tdx_arch.h
create mode 100644 arch/x86/kvm/vmx/tdx_errno.hSignature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 1/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX KeyID management
From: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. Pre-TDX Intel hardware has support for a memory encryption architecture called MK-TME, which repurposes several high bits of physical address as "KeyID". TDX ends up with reserving a sub-range of MK-TME KeyIDs as "TDX private KeyIDs".
Like MK-TME, these KeyIDs can be associated with an ephemeral key. For TDX this association is done by the TDX module. It also has its own tracking for which KeyIDs are in use. To do this ephemeral key setup and manipulate the TDX module's internal tracking, KVM will use the following SEAMCALLs:
TDH.MNG.KEY.CONFIG: Mark the KeyID as in use, and initialize its
ephemeral key.
TDH.MNG.KEY.FREEID: Mark the KeyID as not in use.
These SEAMCALLs both operate on TDR structures, which are setup using the previously added TDH.MNG.CREATE SEAMCALL. KVM's use of these operations will go like:
- tdx_guest_keyid_alloc()
- Initialize TD and TDR page with TDH.MNG.CREATE (not yet-added), passing KeyID
- TDH.MNG.KEY.CONFIG to initialize the key
- TD runs, teardown is started
- TDH.MNG.KEY.FREEID
- tdx_guest_keyid_free()
Don't try to combine the tdx_guest_keyid_alloc() and TDH.MNG.KEY.CONFIG operations because TDH.MNG.CREATE and some locking need to be done in the middle. Don't combine TDH.MNG.KEY.FREEID and tdx_guest_keyid_free() so they are symmetrical with the creation path.
So implement tdh_mng_key_config() and tdh_mng_key_freeid() as separate functions than tdx_guest_keyid_alloc() and tdx_guest_keyid_free().
The TDX module provides SEAMCALLs to hand pages to the TDX module for storing TDX controlled state. SEAMCALLs that operate on this state are directed to the appropriate TD VM using references to the pages originally provided for managing the TD's state. So the host kernel needs to track these pages, both as an ID for specifying which TD to operate on, and to allow them to be eventually reclaimed. The TD VM associated pages are called TDR (Trust Domain Root) and TDCS (Trust Domain Control Structure).
Introduce "struct tdx_td" for holding references to pages provided to the TDX module for this TD VM associated state. Don't plan for any TD associated state that is controlled by KVM to live in this struct. Only expect it to hold data for concepts specific to the TDX architecture, for which there can't already be preexisting storage for in KVM.
Add both the TDR page and an array of TDCS pages, even though the SEAMCALL wrappers will only need to know about the TDR pages for directing the SEAMCALLs to the right TD. Adding the TDCS pages to this struct will let all of the TD VM associated pages handed to the TDX module be tracked in one location. For a type to specify physical pages, use KVM's hpa_t type. Do this for KVM's benefit This is the common type used to hold physical addresses in KVM, so will make interoperability easier.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 12 ++++++++++++ arch/x86/virt/vmx/tdx/tdx.c | 25 +++++++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 16 +++++++++------- 3 files changed, 46 insertions(+), 7 deletions(-)
arch/x86/include/asm/tdx.h +12 -0
@@ -119,6 +119,18 @@ static inline u64 sc_retry(sc_func_t func, u64 fn,int tdx_cpu_enable (void );int tdx_enable (void );const char *tdx_dump_mce_info (struct mce *m); + +struct tdx_td { +/* TD root structure: */ +struct page *tdr_page; + +int tdcs_nr_pages; +/* TD control structure: */ +struct page **tdcs_pages; +}; + +u64 tdh_mng_key_config (struct tdx_td *td); +u64 tdh_mng_key_freeid (struct tdx_td *td);#else static inline void tdx_init (void ) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }
arch/x86/virt/vmx/tdx/tdx.c +25 -0
@@ -1456,3 +1456,28 @@ void __init tdx_init(void)check_tdx_erratum (); } + +static inline u64 tdx_tdr_pa (struct tdx_td *td) +{ +return page_to_phys (td->tdr_page); +} + +u64 tdh_mng_key_config (struct tdx_td *td) +{ +struct tdx_module_args args = { + .rcx =tdx_tdr_pa (td), + }; + +return seamcall (TDH_MNG_KEY_CONFIG , &args); +} +EXPORT_SYMBOL_GPL (tdh_mng_key_config); + +u64 tdh_mng_key_freeid (struct tdx_td *td) +{ +struct tdx_module_args args = { + .rcx =tdx_tdr_pa (td), + }; + +return seamcall (TDH_MNG_KEY_FREEID , &args); +} +EXPORT_SYMBOL_GPL (tdh_mng_key_freeid);
arch/x86/virt/vmx/tdx/tdx.h +9 -7
@@ -15,13 +15,15 @@/* * TDX module SEAMCALL leaf functions */ -#define TDH_PHYMEM_PAGE_RDMD 24 -#define TDH_SYS_KEY_CONFIG 31 -#define TDH_SYS_INIT 33 -#define TDH_SYS_RD 34 -#define TDH_SYS_LP_INIT 35 -#define TDH_SYS_TDMR_INIT 36 -#define TDH_SYS_CONFIG 45 +#define TDH_MNG_KEY_CONFIG 8 +#define TDH_MNG_KEY_FREEID 20 +#define TDH_PHYMEM_PAGE_RDMD 24 +#define TDH_SYS_KEY_CONFIG 31 +#define TDH_SYS_INIT 33 +#define TDH_SYS_RD 34 +#define TDH_SYS_LP_INIT 35 +#define TDH_SYS_TDMR_INIT 36 +#define TDH_SYS_CONFIG 45/* TDX page types */ #define PT_NDA 0x0
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 2/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX TD creation
In reply to Paolo BonziniFrom: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious hosts and certain physical attacks. It defines various control structures that hold state for things like TDs or vCPUs. These control structures are stored in pages given to the TDX module and encrypted with either the global KeyID or the guest KeyIDs.
To manipulate these control structures the TDX module defines a few SEAMCALLs. KVM will use these during the process of creating a TD as follows:
1) Allocate a unique TDX KeyID for a new guest.
1) Call TDH.MNG.CREATE to create a "TD Root" (TDR) page, together with the new allocated KeyID. Unlike the rest of the TDX guest, the TDR page is crypto-protected by the 'global KeyID'.
2) Call the previously added TDH.MNG.KEY.CONFIG on each package to configure the KeyID for the guest. After this step, the KeyID to protect the guest is ready and the rest of the guest will be protected by this KeyID.
3) Call TDH.MNG.ADDCX to add TD Control Structure (TDCS) pages.
4) Call TDH.MNG.INIT to initialize the TDCS.
To reclaim these pages for use by the kernel other SEAMCALLs are needed, which will be added in future patches.
Add tdh_mng_addcx(), tdh_mng_create() and tdh_mng_init() to export these SEAMCALLs so that KVM can use them to create TDs.
For SEAMCALLs that give a page to the TDX module to be encrypted, CLFLUSH the page mapped with KeyID 0, such that any dirty cache lines don't write back later and clobber TD memory or control structures. Don't worry about the other MK-TME KeyIDs because the kernel doesn't use them. The TDX docs specify that this flush is not needed unless the TDX module exposes the CLFLUSH_BEFORE_ALLOC feature bit. Be conservative and always flush. Add a helper function to facilitate this.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 3 +++ arch/x86/virt/vmx/tdx/tdx.c | 51 +++++++++++++++++++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 3 +++ 3 files changed, 57 insertions(+)
arch/x86/include/asm/tdx.h +3 -0
@@ -129,8 +129,11 @@ struct tdx_td { struct page **tdcs_pages; }; +u64 tdh_mng_addcx (struct tdx_td *td,struct page *tdcs_page);u64 tdh_mng_key_config (struct tdx_td *td); +u64 tdh_mng_create (struct tdx_td *td,u16 hkid);u64 tdh_mng_key_freeid (struct tdx_td *td); +u64 tdh_mng_init (struct tdx_td *td,u64 td_params,u64 *extended_err);#else static inline void tdx_init (void ) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }
arch/x86/virt/vmx/tdx/tdx.c +51 -0
66 lines not on this page · raw message
arch/x86/virt/vmx/tdx/tdx.h +3 -0
@@ -15,8 +15,11 @@/* * TDX module SEAMCALL leaf functions */ +#define TDH_MNG_ADDCX 1#define TDH_MNG_KEY_CONFIG 8 +#define TDH_MNG_CREATE 9#define TDH_MNG_KEY_FREEID 20 +#define TDH_MNG_INIT 21#define TDH_PHYMEM_PAGE_RDMD 24#define TDH_SYS_KEY_CONFIG 31#define TDH_SYS_INIT 33
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 3/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX vCPU creation
In reply to Paolo BonziniFrom: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. It defines various control structures that hold state for virtualized components of the TD (i.e. VMs or vCPUs) These control structures are stored in pages given to the TDX module and encrypted with either the global KeyID or the guest KeyIDs.
To manipulate these control structures the TDX module defines a few SEAMCALLs. KVM will use these during the process of creating a vCPU as follows:
1) Call TDH.VP.CREATE to create a TD vCPU Root (TDVPR) page for each vCPU.
2) Call TDH.VP.ADDCX to add per-vCPU control pages (TDCX) for each vCPU.
3) Call TDH.VP.INIT to initialize the TDCX for each vCPU.
To reclaim these pages for use by the kernel other SEAMCALLs are needed, which will be added in future patches.
Export functions to allow KVM to make these SEAMCALLs. Export two variants for TDH.VP.CREATE, in order to support the planned logic of KVM to support TDX modules with and without the ENUM_TOPOLOGY feature. If KVM can drop support for the !ENUM_TOPOLOGY case, this could go down a single version. Leave that for later discussion.
The TDX module provides SEAMCALLs to hand pages to the TDX module for storing TDX controlled state. SEAMCALLs that operate on this state are directed to the appropriate TD vCPU using references to the pages originally provided for managing the vCPU's state. So the host kernel needs to track these pages, both as an ID for specifying which vCPU to operate on, and to allow them to be eventually reclaimed. The vCPU associated pages are called TDVPR (Trust Domain Virtual Processor Root) and TDCX (Trust Domain Control Extension).
Introduce "struct tdx_vp" for holding references to pages provided to the TDX module for the TD vCPU associated state. Don't plan for any vCPU associated state that is controlled by KVM to live in this struct. Only expect it to hold data for concepts specific to the TDX architecture, for which there can't already be preexisting storage for in KVM.
Add both the TDVPR page and an array of TDCX pages, even though the SEAMCALL wrappers will only need to know about the TDVPR pages for directing the SEAMCALLs to the right vCPU. Adding the TDCX pages to this struct will let all of the vCPU associated pages handed to the TDX module be tracked in one location. For a type to specify physical pages, use KVM's hpa_t type. Do this for KVM's benefit This is the common type used to hold physical addresses in KVM, so will make interoperability easier.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 14 ++++++++++++ arch/x86/virt/vmx/tdx/tdx.c | 43 +++++++++++++++++++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 11 ++++++++++ 3 files changed, 68 insertions(+)
arch/x86/include/asm/tdx.h +14 -0
@@ -127,13 +127,27 @@ struct tdx_td {int tdcs_nr_pages;/* TD control structure: */ struct page **tdcs_pages; + +/* Size of `tdcx_pages` in struct tdx_vp */ +int tdcx_nr_pages; +}; + +struct tdx_vp { +/* TDVP root page */ +struct page *tdvpr_page; + +/* TD vCPU control structure: */ +struct page **tdcx_pages; };u64 tdh_mng_addcx (struct tdx_td *td,struct page *tdcs_page); +u64 tdh_vp_addcx (struct tdx_vp *vp,struct page *tdcx_page);u64 tdh_mng_key_config (struct tdx_td *td);u64 tdh_mng_create (struct tdx_td *td,u16 hkid); +u64 tdh_vp_create (struct tdx_td *td,struct tdx_vp *vp);u64 tdh_mng_key_freeid (struct tdx_td *td);u64 tdh_mng_init (struct tdx_td *td,u64 td_params,u64 *extended_err); +u64 tdh_vp_init (struct tdx_vp *vp,u64 initial_rcx,u32 x2apicid);#else static inline void tdx_init (void ) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }
arch/x86/virt/vmx/tdx/tdx.c +43 -0
70 lines not on this page · raw message
arch/x86/virt/vmx/tdx/tdx.h +11 -0
@@ -16,10 +16,13 @@* TDX module SEAMCALL leaf functions */ #define TDH_MNG_ADDCX 1 +#define TDH_VP_ADDCX 4#define TDH_MNG_KEY_CONFIG 8#define TDH_MNG_CREATE 9 +#define TDH_VP_CREATE 10#define TDH_MNG_KEY_FREEID 20#define TDH_MNG_INIT 21 +#define TDH_VP_INIT 22#define TDH_PHYMEM_PAGE_RDMD 24#define TDH_SYS_KEY_CONFIG 31#define TDH_SYS_INIT 33
@@ -28,6 +31,14 @@#define TDH_SYS_TDMR_INIT 36#define TDH_SYS_CONFIG 45 +/* +* SEAMCALL leaf: +* +* Bit 15:0 Leaf number +* Bit 23:16 Version number +*/ +#define TDX_VERSION_SHIFT 16 +/* TDX page types */ #define PT_NDA 0x0#define PT_RSVD 0x1
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 4/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX page cache management
In reply to Paolo BonziniFrom: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. The TDX module uses pages provided by the host for both control structures and for TD guest pages. These pages are encrypted using the MK-TME encryption engine, with its special requirements around cache invalidation. For its own security, the TDX module ensures pages are flushed properly and track which usage they are currently assigned. For creating and tearing down TD VMs and vCPUs KVM will need to use the TDH.PHYMEM.PAGE.RECLAIM, TDH.PHYMEM.CACHE.WB, and TDH.PHYMEM.PAGE.WBINVD SEAMCALLs.
Add tdh_phymem_page_reclaim() to enable KVM to call TDH.PHYMEM.PAGE.RECLAIM to reclaim the page for use by the host kernel. This effectively resets its state in the TDX module's page tracking (PAMT), if the page is available to be reclaimed. This will be used by KVM to reclaim the various types of pages owned by the TDX module. It will have a small wrapper in KVM that retries in the case of a relevant error code. Don't implement this wrapper in arch/x86 because KVM's solution around retrying SEAMCALLs will be better located in a single place.
Add tdh_phymem_cache_wb() to enable KVM to call TDH.PHYMEM.CACHE.WB to do a cache write back in a way that the TDX module can verify, before it allows a KeyID to be freed. The KVM code will use this to have a small wrapper that handles retries. Since the TDH.PHYMEM.CACHE.WB operation is interruptible, have tdh_phymem_cache_wb() take a resume argument to pass this info to the TDX module for restarts. It is worth noting that this SEAMCALL uses a SEAM specific MSR to do the write back in sections. In this way it does export some new functionality that affects CPU state.
Add tdh_phymem_page_wbinvd_tdr() to enable KVM to call TDH.PHYMEM.PAGE.WBINVD to do a cache write back and invalidate of a TDR, using the global KeyID. The underlying TDH.PHYMEM.PAGE.WBINVD SEAMCALL requires the related KeyID to be encoded into the SEAMCALL args. Since the global KeyID is not exposed to KVM, a dedicated wrapper is needed for TDR focused TDH.PHYMEM.PAGE.WBINVD operations.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 17 +++++++++++++++ arch/x86/virt/vmx/tdx/tdx.c | 42 +++++++++++++++++++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 3 +++ 3 files changed, 62 insertions(+)
arch/x86/include/asm/tdx.h +17 -0
@@ -33,6 +33,7 @@#ifndef __ASSEMBLY__#include <uapi/asm/mce.h> +#include <linux/pgtable.h> /* * Used by the #VE exception handler to gather the #VE exception
@@ -140,6 +141,19 @@ struct tdx_vp {struct page **tdcx_pages; }; + +static inline u64 mk_keyed_paddr (u16 hkid,struct page *page) +{ +u64 ret; + + ret =page_to_phys (page); +/* KeyID bits are just above the physical address bits: */ + ret |= (u64 )hkid << boot_cpu_data.x86_phys_bits; + +return ret; + +} +u64 tdh_mng_addcx (struct tdx_td *td,struct page *tdcs_page);u64 tdh_vp_addcx (struct tdx_vp *vp,struct page *tdcx_page);u64 tdh_mng_key_config (struct tdx_td *td);
@@ -148,6 +162,9 @@ u64 tdh_vp_create(struct tdx_td *td, struct tdx_vp *vp);u64 tdh_mng_key_freeid (struct tdx_td *td);u64 tdh_mng_init (struct tdx_td *td,u64 td_params,u64 *extended_err);u64 tdh_vp_init (struct tdx_vp *vp,u64 initial_rcx,u32 x2apicid); +u64 tdh_phymem_page_reclaim (struct page *page,u64 *tdx_pt,u64 *tdx_owner,u64 *tdx_size); +u64 tdh_phymem_cache_wb (bool resume); +u64 tdh_phymem_page_wbinvd_tdr (struct tdx_td *td);#else static inline void tdx_init (void ) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }
arch/x86/virt/vmx/tdx/tdx.c +42 -0
45 lines not on this page · raw message
arch/x86/virt/vmx/tdx/tdx.h +3 -0
@@ -24,11 +24,14 @@#define TDH_MNG_INIT 21#define TDH_VP_INIT 22#define TDH_PHYMEM_PAGE_RDMD 24 +#define TDH_PHYMEM_PAGE_RECLAIM 28#define TDH_SYS_KEY_CONFIG 31#define TDH_SYS_INIT 33#define TDH_SYS_RD 34#define TDH_SYS_LP_INIT 35#define TDH_SYS_TDMR_INIT 36 +#define TDH_PHYMEM_CACHE_WB 40 +#define TDH_PHYMEM_PAGE_WBINVD 41#define TDH_SYS_CONFIG 45/*
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 5/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX VM/vCPU field access
In reply to Paolo BonziniFrom: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. The TDX module has TD scoped and vCPU scoped "metadata fields". These fields are a bit like VMCS fields, and stored in data structures maintained by the TDX module. Export 3 SEAMCALLs for use in reading and writing these fields:
Make tdh_mng_rd() use MNG.VP.RD to read the TD scoped metadata.
Make tdh_vp_rd()/tdh_vp_wr() use TDH.VP.RD/WR to read/write the vCPU scoped metadata.
KVM will use these by creating inline helpers that target various metadata sizes. Export the raw SEAMCALL leaf, to avoid exporting the large number of various sized helpers.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 3 +++ arch/x86/virt/vmx/tdx/tdx.c | 47 +++++++++++++++++++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 3 +++ 3 files changed, 53 insertions(+)
arch/x86/include/asm/tdx.h +3 -0
@@ -159,9 +159,12 @@ u64 tdh_vp_addcx(struct tdx_vp *vp, struct page *tdcx_page);u64 tdh_mng_key_config (struct tdx_td *td);u64 tdh_mng_create (struct tdx_td *td,u16 hkid);u64 tdh_vp_create (struct tdx_td *td,struct tdx_vp *vp); +u64 tdh_mng_rd (struct tdx_td *td,u64 field,u64 *data);u64 tdh_mng_key_freeid (struct tdx_td *td);u64 tdh_mng_init (struct tdx_td *td,u64 td_params,u64 *extended_err);u64 tdh_vp_init (struct tdx_vp *vp,u64 initial_rcx,u32 x2apicid); +u64 tdh_vp_rd (struct tdx_vp *vp,u64 field,u64 *data); +u64 tdh_vp_wr (struct tdx_vp *vp,u64 field,u64 data,u64 mask);u64 tdh_phymem_page_reclaim (struct page *page,u64 *tdx_pt,u64 *tdx_owner,u64 *tdx_size);u64 tdh_phymem_cache_wb (bool resume);u64 tdh_phymem_page_wbinvd_tdr (struct tdx_td *td);
arch/x86/virt/vmx/tdx/tdx.c +47 -0
59 lines not on this page · raw message
arch/x86/virt/vmx/tdx/tdx.h +3 -0
@@ -19,11 +19,13 @@#define TDH_VP_ADDCX 4#define TDH_MNG_KEY_CONFIG 8#define TDH_MNG_CREATE 9 +#define TDH_MNG_RD 11#define TDH_VP_CREATE 10#define TDH_MNG_KEY_FREEID 20#define TDH_MNG_INIT 21#define TDH_VP_INIT 22#define TDH_PHYMEM_PAGE_RDMD 24 +#define TDH_VP_RD 26#define TDH_PHYMEM_PAGE_RECLAIM 28#define TDH_SYS_KEY_CONFIG 31#define TDH_SYS_INIT 33
@@ -32,6 +34,7 @@#define TDH_SYS_TDMR_INIT 36#define TDH_PHYMEM_CACHE_WB 40#define TDH_PHYMEM_PAGE_WBINVD 41 +#define TDH_VP_WR 43#define TDH_SYS_CONFIG 45/*
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 6/30 x86/virt/tdx: Add SEAMCALL wrappers for TDX flush operations
In reply to Paolo BonziniFrom: Rick Edgecombe <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. The TDX module has the concept of flushing vCPUs. These flushes include both a flush of the translation caches and also any other state internal to the TDX module. Before freeing a KeyID, this flush operation needs to be done. KVM will need to perform the flush on each pCPU associated with the TD, and also perform a TD scoped operation that checks if the flush has been done on all vCPU's associated with the TD.
Add a tdh_vp_flush() function to be used to call TDH.VP.FLUSH on each pCPU associated with the TD during TD teardown. It will also be called when disabling TDX and during vCPU migration between pCPUs.
Add tdh_mng_vpflushdone() to be used by KVM to call TDH.MNG.VPFLUSHDONE. KVM will use this during TD teardown to verify that TDH.VP.FLUSH has been called sufficiently, and advance the state machine that will allow for reclaiming the TD's KeyID.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 2 ++ arch/x86/virt/vmx/tdx/tdx.c | 20 ++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx.h | 2 ++ 3 files changed, 24 insertions(+)
arch/x86/include/asm/tdx.h +2 -0
@@ -160,6 +160,8 @@ u64 tdh_mng_key_config(struct tdx_td *td);u64 tdh_mng_create (struct tdx_td *td,u16 hkid);u64 tdh_vp_create (struct tdx_td *td,struct tdx_vp *vp);u64 tdh_mng_rd (struct tdx_td *td,u64 field,u64 *data); +u64 tdh_vp_flush (struct tdx_vp *vp); +u64 tdh_mng_vpflushdone (struct tdx_td *td);u64 tdh_mng_key_freeid (struct tdx_td *td);u64 tdh_mng_init (struct tdx_td *td,u64 td_params,u64 *extended_err);u64 tdh_vp_init (struct tdx_vp *vp,u64 initial_rcx,u32 x2apicid);
arch/x86/virt/vmx/tdx/tdx.c +20 -0
@@ -1554,6 +1554,26 @@ u64 tdh_mng_rd(struct tdx_td *td, u64 field, u64 *data) }EXPORT_SYMBOL_GPL (tdh_mng_rd); +u64 tdh_vp_flush (struct tdx_vp *vp) +{ +struct tdx_module_args args = { + .rcx =tdx_tdvpr_pa (vp), + }; + +return seamcall (TDH_VP_FLUSH , &args); +} +EXPORT_SYMBOL_GPL (tdh_vp_flush); + +u64 tdh_mng_vpflushdone (struct tdx_td *td) +{ +struct tdx_module_args args = { + .rcx =tdx_tdr_pa (td), + }; + +return seamcall (TDH_MNG_VPFLUSHDONE , &args); +} +EXPORT_SYMBOL_GPL (tdh_mng_vpflushdone); +u64 tdh_mng_key_freeid (struct tdx_td *td) {struct tdx_module_args args = {
arch/x86/virt/vmx/tdx/tdx.h +2 -0
@@ -20,6 +20,8 @@#define TDH_MNG_KEY_CONFIG 8#define TDH_MNG_CREATE 9#define TDH_MNG_RD 11 +#define TDH_VP_FLUSH 18 +#define TDH_MNG_VPFLUSHDONE 19#define TDH_VP_CREATE 10#define TDH_MNG_KEY_FREEID 20#define TDH_MNG_INIT 21
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 7/30 x86/virt/tdx: allocate tdx_sys_info in static memory
In reply to Paolo BonziniAdding all the information that KVM needs increases the size of struct tdx_sys_info, to the point that you can get warnings about the stack size of init_tdx_module(). Since KVM also needs to read the TDX metadata after init_tdx_module() returns, make the variable a global.
--- arch/x86/virt/vmx/tdx/tdx.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
arch/x86/virt/vmx/tdx/tdx.c +6 -5
@@ -53,6 +53,8 @@ static DEFINE_MUTEX(tdx_module_lock);/* All TDX-usable memory regions. Protected by mem_hotplug_lock. */ static LIST_HEAD (tdx_memlist); +static struct tdx_sys_info tdx_sysinfo; +typedef void (*sc_err_func_t )(u64 fn,u64 err,struct tdx_module_args *args);static inline void seamcall_err (u64 fn,u64 err,struct tdx_module_args *args)
@@ -1061,15 +1063,14 @@ static int init_tdmrs(struct tdmr_info_list *tdmr_list)static int init_tdx_module (void ) { -struct tdx_sys_info sysinfo;int ret; - ret =get_tdx_sys_info (&sysinfo); + ret =get_tdx_sys_info (&tdx_sysinfo);if (ret)return ret;/* Check whether the kernel can support this module */ - ret =check_features (&sysinfo); + ret =check_features (&tdx_sysinfo);if (ret)return ret;
@@ -1090,12 +1091,12 @@ static int init_tdx_module(void) goto out_put_tdxmem;/* Allocate enough space for constructing TDMRs */ - ret =alloc_tdmr_list (&tdx_tdmr_list, &sysinfo.tdmr); + ret =alloc_tdmr_list (&tdx_tdmr_list, &tdx_sysinfo.tdmr);if (ret) goto err_free_tdxmem;/* Cover all TDX-usable memory regions in TDMRs */ - ret =construct_tdmrs (&tdx_memlist, &tdx_tdmr_list, &sysinfo.tdmr); + ret =construct_tdmrs (&tdx_memlist, &tdx_tdmr_list, &tdx_sysinfo.tdmr);if (ret) goto err_free_tdmrs;
Signature · 1 line
2.43.5
Re: [PATCH 07/30] x86/virt/tdx: allocate tdx_sys_info in static memory
Quoted 7 lines · Paolo Bonzini
Adding all the information that KVM needs increases the size of struct
tdx_sys_info, to the point that you can get warnings about the stack size ofinit_tdx_module(). Since KVM also needs to read the TDX metadata afterinit_tdx_module()returns, make the variable a global.Signed-off-by Paolo Bonzini <[email protected]>
Re: [PATCH 07/30] x86/virt/tdx: allocate tdx_sys_info in static memory
In reply to Paolo BonziniQuoted 6 lines · Paolo Bonzini
Adding all the information that KVM needs increases the size of struct
tdx_sys_info, to the point that you can get warnings about the stack size of init_tdx_module(). Since KVM also needs to read the TDX metadata afterinit_tdx_module()returns, make the variable a global.Signed-off-by Paolo Bonzini <[email protected]>
It looks like the same code just lifted and moved earlier out of the already acked patch.
Paolo Bonzini
maintainerPATCH v3 8/30 x86/virt/tdx: Read essential global metadata for KVM
In reply to Paolo BonziniFrom: Kai Huang <[email protected]>
KVM needs two classes of global metadata to create and run TDX guests:
- "TD Control Structures"
- "TD Configurability"
The first class contains the sizes of TDX guest per-VM and per-vCPU control structures. KVM will need to use them to allocate enough space for those control structures.
The second class contains info which reports things like which features are configurable to TDX guest etc. KVM will need to use them to properly configure TDX guests.
Read them for KVM TDX to use.
The code change is auto-generated by re-running the script in [1] after uncommenting the "td_conf" and "td_ctrl" part to regenerate the tdx_global_metadata.{hc} and update them to the existing ones in the kernel.
#python tdx.py global_metadata.json tdx_global_metadata.h \
tdx_global_metadata.c
The 'global_metadata.json' can be fetched from [2].
Note that as of this writing, the JSON file only allows a maximum of 32 CPUID entries. While this is enough for current contents of the CPUID leaves, there were plans to change the JSON per TDX module release which would change the ABI and potentially prevent future versions of the TDX module from working with older kernels.
While discussions are ongoing with the TDX module team on what exactly constitutes an ABI breakage, in the meantime the TDX module team has agreed to not increase the number of CPUID entries beyond 128 without an opt in. Therefore the file was tweaked by hand to change the maximum number of CPUID_CONFIGs.
Message-ID: <[email protected]>
--- arch/x86/virt/vmx/tdx/tdx_global_metadata.c | 50 +++++++++++++++++++++ arch/x86/virt/vmx/tdx/tdx_global_metadata.h | 19 ++++++++ 2 files changed, 69 insertions(+)
arch/x86/virt/vmx/tdx/tdx_global_metadata.c +50 -0
@@ -37,12 +37,62 @@ static int get_tdx_sys_info_tdmr(struct tdx_sys_info_tdmr *sysinfo_tdmr)return ret; } +static int get_tdx_sys_info_td_ctrl (struct tdx_sys_info_td_ctrl *sysinfo_td_ctrl) +{ +int ret =0 ; +u64 val; + +if (!ret && !(ret =read_sys_metadata_field (0x9800000100000000 , &val))) + sysinfo_td_ctrl->tdr_base_size = val; +if (!ret && !(ret =read_sys_metadata_field (0x9800000100000100 , &val))) + sysinfo_td_ctrl->tdcs_base_size = val; +if (!ret && !(ret =read_sys_metadata_field (0x9800000100000200 , &val))) + sysinfo_td_ctrl->tdvps_base_size = val; + +return ret; +} + +static int get_tdx_sys_info_td_conf (struct tdx_sys_info_td_conf *sysinfo_td_conf) +{ +int ret =0 ; +u64 val; +int i, j; + +if (!ret && !(ret =read_sys_metadata_field (0x1900000300000000 , &val))) + sysinfo_td_conf->attributes_fixed0 = val; +if (!ret && !(ret =read_sys_metadata_field (0x1900000300000001 , &val))) + sysinfo_td_conf->attributes_fixed1 = val; +if (!ret && !(ret =read_sys_metadata_field (0x1900000300000002 , &val))) + sysinfo_td_conf->xfam_fixed0 = val; +if (!ret && !(ret =read_sys_metadata_field (0x1900000300000003 , &val))) + sysinfo_td_conf->xfam_fixed1 = val; +if (!ret && !(ret =read_sys_metadata_field (0x9900000100000004 , &val))) + sysinfo_td_conf->num_cpuid_config = val; +if (!ret && !(ret =read_sys_metadata_field (0x9900000100000008 , &val))) + sysinfo_td_conf->max_vcpus_per_td = val; +if (sysinfo_td_conf->num_cpuid_config >ARRAY_SIZE (sysinfo_td_conf->cpuid_config_leaves)) +return -EINVAL ; +for (i =0 ; i < sysinfo_td_conf->num_cpuid_config; i++) +if (!ret && !(ret =read_sys_metadata_field (0x9900000300000400 + i, &val))) + sysinfo_td_conf->cpuid_config_leaves[i] = val; +if (sysinfo_td_conf->num_cpuid_config >ARRAY_SIZE (sysinfo_td_conf->cpuid_config_values)) +return -EINVAL ; +for (i =0 ; i < sysinfo_td_conf->num_cpuid_config; i++) +for (j =0 ; j <2 ; j++) +if (!ret && !(ret =read_sys_metadata_field (0x9900000300000500 + i *2 + j, &val))) + sysinfo_td_conf->cpuid_config_values[i][j] = val; + +return ret; +} +static int get_tdx_sys_info (struct tdx_sys_info *sysinfo) {int ret =0 ; ret = ret ?:get_tdx_sys_info_features (&sysinfo->features); ret = ret ?:get_tdx_sys_info_tdmr (&sysinfo->tdmr); + ret = ret ?:get_tdx_sys_info_td_ctrl (&sysinfo->td_ctrl); + ret = ret ?:get_tdx_sys_info_td_conf (&sysinfo->td_conf);return ret; }
arch/x86/virt/vmx/tdx/tdx_global_metadata.h +19 -0
@@ -17,9 +17,28 @@ struct tdx_sys_info_tdmr { u16 pamt_1g_entry_size; }; +struct tdx_sys_info_td_ctrl { +u16 tdr_base_size; +u16 tdcs_base_size; +u16 tdvps_base_size; +}; + +struct tdx_sys_info_td_conf { +u64 attributes_fixed0; +u64 attributes_fixed1; +u64 xfam_fixed0; +u64 xfam_fixed1; +u16 num_cpuid_config; +u16 max_vcpus_per_td; +u64 cpuid_config_leaves[128 ]; +u64 cpuid_config_values[128 ][2 ]; +}; +struct tdx_sys_info {struct tdx_sys_info_features features;struct tdx_sys_info_tdmr tdmr; +struct tdx_sys_info_td_ctrl td_ctrl; +struct tdx_sys_info_td_conf td_conf; };#endif
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 9/30 x86/virt/tdx: Add tdx_guest_keyid_alloc/free() to alloc and free TDX guest KeyID
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Intel TDX protects guest VMs from malicious host and certain physical attacks. Pre-TDX Intel hardware has support for a memory encryption architecture called MK-TME, which repurposes several high bits of physical address as "KeyID". The BIOS reserves a sub-range of MK-TME KeyIDs as "TDX private KeyIDs".
Each TDX guest must be assigned with a unique TDX KeyID when it is created. The kernel reserves the first TDX private KeyID for crypto-protection of specific TDX module data which has a lifecycle that exceeds the KeyID reserved for the TD's use. The rest of the KeyIDs are left for TDX guests to use.
Create a small KeyID allocator. Export tdx_guest_keyid_alloc()/tdx_guest_keyid_free() to allocate and free TDX guest KeyID for KVM to use.
Don't provide the stub functions when CONFIG_INTEL_TDX_HOST=n since they are not supposed to be called in this case.
Message-ID: <[email protected]>
--- arch/x86/include/asm/tdx.h | 3 +++ arch/x86/virt/vmx/tdx/tdx.c | 17 +++++++++++++++++ 2 files changed, 20 insertions(+)
arch/x86/include/asm/tdx.h +3 -0
@@ -121,6 +121,9 @@ int tdx_cpu_enable(void);int tdx_enable (void );const char *tdx_dump_mce_info (struct mce *m); +int tdx_guest_keyid_alloc (void ); +void tdx_guest_keyid_free (unsigned int keyid); +struct tdx_td {/* TD root structure: */ struct page *tdr_page;
arch/x86/virt/vmx/tdx/tdx.c +17 -0
@@ -28,6 +28,7 @@#include <linux/log2.h> #include <linux/acpi.h> #include <linux/suspend.h> +#include <linux/idr.h> #include <asm/page.h> #include <asm/special_insns.h> #include <asm/msr-index.h>
@@ -43,6 +44,8 @@ static u32 tdx_global_keyid __ro_after_init;static u32 tdx_guest_keyid_start__ro_after_init ;static u32 tdx_nr_guest_keyids__ro_after_init ; +static DEFINE_IDA (tdx_guest_keyid_pool); + static DEFINE_PER_CPU(bool, tdx_lp_initialized);static struct tdmr_info_list tdx_tdmr_list;
@@ -1459,6 +1462,20 @@ void __init tdx_init(void)check_tdx_erratum (); } +int tdx_guest_keyid_alloc (void ) +{ +return ida_alloc_range (&tdx_guest_keyid_pool, tdx_guest_keyid_start, + tdx_guest_keyid_start + tdx_nr_guest_keyids -1 , +GFP_KERNEL ); +} +EXPORT_SYMBOL_GPL (tdx_guest_keyid_alloc); + +void tdx_guest_keyid_free (unsigned int keyid) +{ +ida_free (&tdx_guest_keyid_pool, keyid); +} +EXPORT_SYMBOL_GPL (tdx_guest_keyid_free); +static inline u64 tdx_tdr_pa (struct tdx_td *td) {return page_to_phys (td->tdr_page);
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 10/30 KVM: Export hardware virtualization enabling/disabling functions
In reply to Paolo BonziniFrom: Kai Huang <[email protected]>
To support TDX, KVM will need to enable TDX during KVM module loading time. Enabling TDX requires enabling hardware virtualization first so that all online CPUs (and the new CPU going online) are in post-VMXON state.
KVM by default enables hardware virtualization but that is done in kvm_init(), which must be the last step after all initialization is done thus is too late for enabling TDX.
Export functions to enable/disable hardware virtualization so that TDX code can use them to handle hardware virtualization enabling before kvm_init().
Message-ID: <dfe17314c0d9978b7bc3b0833dff6f167fbd28f5.1731664295.git.kai.huang@intel.com>
--- include/linux/kvm_host.h | 8 ++++++++ virt/kvm/kvm_main.c | 18 ++++-------------- 2 files changed, 12 insertions(+), 14 deletions(-)
include/linux/kvm_host.h +8 -0
@@ -2571,4 +2571,12 @@ long kvm_arch_vcpu_pre_fault_memory(struct kvm_vcpu *vcpu, struct kvm_pre_fault_memory *range);#endif +#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING +int kvm_enable_virtualization (void ); +void kvm_disable_virtualization (void ); +#else +static inline int kvm_enable_virtualization (void ) {return 0 ; } +static inline void kvm_disable_virtualization (void ) { } +#endif +#endif
virt/kvm/kvm_main.c +4 -14
@@ -143,8 +143,6 @@ static int kvm_no_compat_open(struct inode *inode, struct file *file)#define KVM_COMPAT (c) .compat_ioctl = kvm_no_compat_ioctl, \ .open = kvm_no_compat_open#endif -static int kvm_enable_virtualization (void ); -static void kvm_disable_virtualization (void );static void kvm_io_bus_destroy (struct kvm_io_bus *bus);
@@ -5576,7 +5574,7 @@ static struct syscore_ops kvm_syscore_ops = { .shutdown = kvm_shutdown, }; -static int kvm_enable_virtualization (void ) +int kvm_enable_virtualization (void ) {int r;
@@ -5621,8 +5619,9 @@ static int kvm_enable_virtualization(void) --kvm_usage_count;return r; } +EXPORT_SYMBOL_GPL (kvm_enable_virtualization); -static void kvm_disable_virtualization (void ) +void kvm_disable_virtualization (void ) {guard (mutex)(&kvm_usage_lock);
@@ -5633,6 +5632,7 @@ static void kvm_disable_virtualization(void)cpuhp_remove_state (CPUHP_AP_KVM_ONLINE );kvm_arch_disable_virtualization (); } +EXPORT_SYMBOL_GPL (kvm_disable_virtualization);static int kvm_init_virtualization (void ) {
@@ -5648,21 +5648,11 @@ static void kvm_uninit_virtualization(void) kvm_disable_virtualization(); }#else /* CONFIG_KVM_GENERIC_HARDWARE_ENABLING */ -static int kvm_enable_virtualization (void ) -{ -return 0 ; -} -static int kvm_init_virtualization (void ) {return 0 ; } -static void kvm_disable_virtualization (void ) -{ - -} -static void kvm_uninit_virtualization (void ) {
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 11/30 KVM: VMX: Refactor VMX module init/exit functions
In reply to Paolo BonziniFrom: Kai Huang <[email protected]>
Add vt_init() and vt_exit() as the new module init/exit functions and refactor existing vmx_init()/vmx_exit() as helper to make room for TDX specific initialization and teardown.
To support TDX, KVM will need to enable TDX during KVM module loading time. Enabling TDX requires enabling hardware virtualization first so that all online CPUs (and the new CPU going online) are in post-VMXON state.
Currently, the vmx_init() flow is:
1) hv_init_evmcs(),
2) kvm_x86_vendor_init(),
3) Other VMX specific initialization,
4) kvm_init()
The kvm_x86_vendor_init() invokes kvm_x86_init_ops::hardware_setup() to do VMX specific hardware setup and calls kvm_update_ops() to initialize kvm_x86_ops to VMX's version.
TDX will have its own version for most of kvm_x86_ops callbacks. It would be nice if kvm_x86_init_ops::hardware_setup() could also be used for TDX, but in practice it cannot. The reason is, as mentioned above, TDX initialization requires hardware virtualization having been enabled, which must happen after kvm_update_ops(), but hardware_setup() is done before that.
Also, TDX is based on VMX, and it makes sense to only initialize TDX after VMX has been initialized. If VMX fails to initialize, TDX is likely broken anyway.
So the new flow of KVM module init function will be:
1) Current VMX initialization code in vmx_init() before kvm_init(),
2) TDX initialization,
3) kvm_init()
Split vmx_init() into two parts based on above 1) and 3) so that TDX initialization can fit in between. Make part 1) as the new helper vmx_init(). Introduce vt_init() as the new module init function which calls vmx_init() and kvm_init(). TDX initialization will be added later.
Do the same thing for vmx_exit()/vt_exit().
Message-ID: <3f23f24098bdcf42e213798893ffff7cdc7103be.1731664295.git.kai.huang@intel.com>
--- arch/x86/kvm/vmx/main.c | 32 ++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/vmx.c | 25 +++---------------------- arch/x86/kvm/vmx/vmx.h | 3 +++ 3 files changed, 38 insertions(+), 22 deletions(-)
arch/x86/kvm/vmx/main.c +32 -0
@@ -168,3 +168,35 @@ struct kvm_x86_init_ops vt_init_ops __initdata = { .runtime_ops = &vt_x86_ops, .pmu_ops = &intel_pmu_ops, }; + +static void __exit vt_exit(void) +{ +kvm_exit (); +vmx_exit (); +} +module_exit (vt_exit); + +static int __init vt_init (void ) +{ +int r; + + r =vmx_init (); +if (r) +return r; + +/* +* Common KVM initialization _must_ come last, after this, /dev/kvm is +* exposed to userspace! +*/ + r =kvm_init (sizeof (struct vcpu_vmx ), __alignof__(struct vcpu_vmx ), +THIS_MODULE ); +if (r) + goto err_kvm_init; + +return 0 ; + +err_kvm_init: +vmx_exit (); +return r; +} +module_init (vt_init);
arch/x86/kvm/vmx/vmx.c +3 -22
@@ -8588,7 +8588,7 @@ __init int vmx_hardware_setup(void)return r; } -static void vmx_cleanup_l1d_flush (void ) +static void __exit vmx_cleanup_l1d_flush(void) {if (vmx_l1d_flush_pages) {free_pages ((unsigned long )vmx_l1d_flush_pages,L1D_CACHE_ORDER );
@@ -8598,23 +8598,16 @@ static void vmx_cleanup_l1d_flush(void) l1tf_vmx_mitigation =VMENTER_L1D_FLUSH_AUTO ; } -static void __vmx_exit (void ) +void __exit vmx_exit(void) { allow_smaller_maxphyaddr = false;vmx_cleanup_l1d_flush (); -} -static void __exit vmx_exit(void) -{ -kvm_exit (); -__vmx_exit ();kvm_x86_vendor_exit (); - } -module_exit (vmx_exit); -static int __init vmx_init (void ) +int __init vmx_init (void ) {int r, cpu;
@@ -8658,21 +8651,9 @@ static int __init vmx_init(void)if (!enable_ept) allow_smaller_maxphyaddr = true; -/* -* Common KVM initialization _must_ come last, after this, /dev/kvm is -* exposed to userspace! -*/ - r =kvm_init (sizeof (struct vcpu_vmx ), __alignof__(struct vcpu_vmx ), -THIS_MODULE ); -if (r) - goto err_kvm_init; -return 0 ; -err_kvm_init: -__vmx_exit (); err_l1d_flush:kvm_x86_vendor_exit ();return r; } -module_init (vmx_init);
arch/x86/kvm/vmx/vmx.h +3 -0
@@ -760,4 +760,7 @@ static inline void vmx_segment_cache_clear(struct vcpu_vmx *vmx) vmx->segment_cache.bitmask = 0; } +int vmx_init (void ); +void vmx_exit (void ); +#endif /* __KVM_X86_VMX_H */
Signature · 1 line
2.43.5
Re: [PATCH 11/30] KVM: VMX: Refactor VMX module init/exit functions
Quoted 56 lines
arch/x86/kvm/vmx/main.c +31
-0+static void __exit vt_exit(void) +{ +kvm_exit (); +vmx_exit (); +} +module_exit (vt_exit); + +static int __init vt_init (void ) +{ +int r; + + r =vmx_init (); +if (r) +return r; + +/* +* Common KVM initialization _must_ come last, after this, /dev/kvm is +* exposed to userspace! +*/ + r =kvm_init (sizeof (struct vcpu_vmx ), __alignof__(struct vcpu_vmx ), +THIS_MODULE ); +if (r) + goto err_kvm_init; + +return 0 ; + +err_kvm_init: +vmx_exit (); +return r; +} +module_init (vt_init);arch/x86/kvm/vmx/vmx.c +2
-3@@ -8588,7 +8588,7 @@ __init int vmx_hardware_setup(void)return r; } -static void vmx_cleanup_l1d_flush (void ) +static void __exit vmx_cleanup_l1d_flush(void) {if (vmx_l1d_flush_pages) {free_pages ((unsigned long )vmx_l1d_flush_pages,L1D_CACHE_ORDER );@@ -8598,23 +8598,16 @@ static void vmx_cleanup_l1d_flush(void) l1tf_vmx_mitigation =VMENTER_L1D_FLUSH_AUTO ; } -static void __vmx_exit (void ) +void __exit vmx_exit(void) { allow_smaller_maxphyaddr = false;vmx_cleanup_l1d_flush (); -}
arch/x86/kvm/vmx/vmx.c static void vmx_cleanup_l1d_flush(void) · line 8609
Quoted 10 lines
arch/x86/kvm/vmx/vmx.c +0
-6-static void __exit vmx_exit(void) -{ -kvm_exit (); -__vmx_exit ();kvm_x86_vendor_exit (); - } -module_exit (vmx_exit);
Hi Paolo,
I think you will still meet the "section mismatch in reference: vt_init ..." warning reported by LKP, for which I posted a diff to address:
Paolo Bonzini
maintainerPATCH v3 12/30 KVM: VMX: Initialize TDX during KVM module load
In reply to Paolo BonziniFrom: Kai Huang <[email protected]>
Before KVM can use TDX to create and run TDX guests, TDX needs to be initialized from two perspectives: 1) TDX module must be initialized properly to a working state; 2) A per-cpu TDX initialization, a.k.a the TDH.SYS.LP.INIT SEAMCALL must be done on any logical cpu before it can run any other TDX SEAMCALLs.
The TDX host core-kernel provides two functions to do the above two
respectively: tdx_enable() and tdx_cpu_enable().
There are two options in terms of when to initialize TDX: initialize TDX at KVM module loading time, or when creating the first TDX guest.
Choose to initialize TDX during KVM module loading time:
Initializing TDX module is both memory and CPU time consuming: 1) the kernel needs to allocate a non-trivial size(~1/256) of system memory as metadata used by TDX module to track each TDX-usable memory page's status; 2) the TDX module needs to initialize this metadata, one entry for each TDX-usable memory page.
Also, the kernel uses alloc_contig_pages() to allocate those metadata chunks, because they are large and need to be physically contiguous. alloc_contig_pages() can fail. If initializing TDX when creating the first TDX guest, then there's chance that KVM won't be able to run any TDX guests albeit KVM _declares_ to be able to support TDX.
This isn't good for the user.
On the other hand, initializing TDX at KVM module loading time can make sure KVM is providing a consistent view of whether KVM can support TDX to the user.
Always only try to initialize TDX after VMX has been initialized. TDX is based on VMX, and if VMX fails to initialize then TDX is likely to be broken anyway. Also, in practice, supporting TDX will require part of VMX and common x86 infrastructure in working order, so TDX cannot be enabled alone w/o VMX support.
There are two cases that can result in failure to initialize TDX: 1) TDX cannot be supported (e.g., because of TDX is not supported or enabled by hardware, or module is not loaded, or missing some dependency in KVM's configuration); 2) Any unexpected error during TDX bring-up. For the first case only mark TDX is disabled but still allow KVM module to be loaded. For the second case just fail to load the KVM module so that the user can be aware.
Because TDX costs additional memory, don't enable TDX by default. Add a new module parameter 'enable_tdx' to allow the user to opt-in.
Note, the name tdx_init() has already been taken by the early boot code. Use tdx_bringup() for initializing TDX (and tdx_cleanup() since KVM doesn't actually teardown TDX). They don't match vt_init()/vt_exit(), vmx_init()/vmx_exit() etc but it's not end of the world.
Also, once initialized, the TDX module cannot be disabled and enabled again w/o the TDX module runtime update, which isn't supported by the kernel. After TDX is enabled, nothing needs to be done when KVM disables hardware virtualization, e.g., when offlining CPU, or during suspend/resume. TDX host core-kernel code internally tracks TDX status and can handle "multiple enabling" scenario.
Similar to KVM_AMD_SEV, add a new KVM_INTEL_TDX Kconfig to guide KVM TDX code. Make it depend on INTEL_TDX_HOST but not replace INTEL_TDX_HOST because in the longer term there's a use case that requires making SEAMCALLs w/o KVM as mentioned by Dan [1].
Message-ID: <162f9dee05c729203b9ad6688db1ca2960b4b502.1731664295.git.kai.huang@intel.com>
---
arch/x86/include/asm/tdx.h | 3 +
.../tdx => include/asm}/tdx_global_metadata.h | 0
arch/x86/kvm/Kconfig | 10 ++
arch/x86/kvm/Makefile | 1 +
arch/x86/kvm/vmx/main.c | 9 +
arch/x86/kvm/vmx/tdx.c | 160 ++++++++++++++++++
arch/x86/kvm/vmx/tdx.h | 13 ++
arch/x86/virt/vmx/tdx/tdx.c | 14 ++
arch/x86/virt/vmx/tdx/tdx.h | 1 -
include/linux/kvm_host.h | 1 +
virt/kvm/kvm_main.c | 3 +-
11 files changed, 213 insertions(+), 2 deletions(-)
rename arch/x86/{virt/vmx/tdx => include/asm}/tdx_global_metadata.h (100%)
create mode 100644 arch/x86/kvm/vmx/tdx.c
create mode 100644 arch/x86/kvm/vmx/tdx.harch/x86/include/asm/tdx.h +3 -0
@@ -33,6 +33,7 @@#ifndef __ASSEMBLY__#include <uapi/asm/mce.h> +#include <asm/tdx_global_metadata.h> #include <linux/pgtable.h> /*
@@ -120,6 +121,7 @@ static inline u64 sc_retry(sc_func_t func, u64 fn,int tdx_cpu_enable (void );int tdx_enable (void );const char *tdx_dump_mce_info (struct mce *m); +const struct tdx_sys_info *tdx_get_sysinfo (void );int tdx_guest_keyid_alloc (void );void tdx_guest_keyid_free (unsigned int keyid);
@@ -178,6 +180,7 @@ static inline void tdx_init(void) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }static inline int tdx_enable (void ) {return -ENODEV ; }static inline const char *tdx_dump_mce_info (struct mce *m) {return NULL ; } +static inline const struct tdx_sys_info *tdx_get_sysinfo (void ) {return NULL ; }#endif /* CONFIG_INTEL_TDX_HOST */ #endif /* !__ASSEMBLY__ */
arch/x86/include/asm/tdx_global_metadata.h renamed from arch/x86/virt/vmx/tdx/tdx_global_metadata.h +0 -0
arch/x86/kvm/Kconfig +10 -0
@@ -128,6 +128,16 @@ config X86_SGX_KVM If unsure, say N. +config KVM_INTEL_TDX + bool "Intel Trust Domain Extensions (TDX) support" + default y + depends on INTEL_TDX_HOST + help + Provides support for launching Intel Trust Domain Extensions (TDX) + confidential VMs on Intel processors. + + If unsure, say N. + config KVM_AMD tristate "KVM for AMD processors support" depends on KVM && (CPU_SUP_AMD || CPU_SUP_HYGON)
arch/x86/kvm/Makefile +1 -0
@@ -20,6 +20,7 @@ kvm-intel-y += vmx/vmx.o vmx/vmenter.o vmx/pmu_intel.o vmx/vmcs12.o \ kvm-intel-$(CONFIG_X86_SGX_KVM) += vmx/sgx.o kvm-intel-$(CONFIG_KVM_HYPERV) += vmx/hyperv.o vmx/hyperv_evmcs.o +kvm-intel-$(CONFIG_KVM_INTEL_TDX) += vmx/tdx.o kvm-amd-y += svm/svm.o svm/vmenter.o svm/pmu.o svm/nested.o svm/avic.o
arch/x86/kvm/vmx/main.c +9 -0
@@ -6,6 +6,7 @@#include "nested.h" #include "pmu.h" #include "posted_intr.h" +#include "tdx.h" #define VMX_REQUIRED_APICV_INHIBITS \ (BIT(APICV_INHIBIT_REASON_DISABLED) | \
@@ -172,6 +173,7 @@ struct kvm_x86_init_ops vt_init_ops __initdata = { static void __exit vt_exit(void) {kvm_exit (); +tdx_cleanup ();vmx_exit (); }module_exit (vt_exit);
@@ -184,6 +186,11 @@ static int __init vt_init(void)if (r)return r; +/* tdx_init() has been taken */ + r =tdx_bringup (); +if (r) + goto err_tdx_bringup; +/* * Common KVM initialization _must_ come last, after this, /dev/kvm is * exposed to userspace!
@@ -196,6 +203,8 @@ static int __init vt_init(void)return 0 ; err_kvm_init: +tdx_cleanup (); +err_tdx_bringup:vmx_exit ();return r; }
arch/x86/kvm/vmx/tdx.c new file +160 -0
160 lines not on this page · raw message
arch/x86/kvm/vmx/tdx.h new file +13 -0
@@ -0,0 +1,13 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef __KVM_X86_VMX_TDX_H +#define __KVM_X86_VMX_TDX_H + +#ifdef CONFIG_INTEL_TDX_HOST +int tdx_bringup (void ); +void tdx_cleanup (void ); +#else +static inline int tdx_bringup (void ) {return 0 ; } +static inline void tdx_cleanup (void ) {} +#endif + +#endif
arch/x86/virt/vmx/tdx/tdx.c +14 -0
@@ -1462,6 +1462,20 @@ void __init tdx_init(void)check_tdx_erratum (); } +const struct tdx_sys_info *tdx_get_sysinfo (void ) +{ +const struct tdx_sys_info *p =NULL ; + +/* Make sure all fields in @tdx_sysinfo have been populated */ +mutex_lock (&tdx_module_lock); +if (tdx_module_status ==TDX_MODULE_INITIALIZED ) + p = (const struct tdx_sys_info *)&tdx_sysinfo; +mutex_unlock (&tdx_module_lock); + +return p; +} +EXPORT_SYMBOL_GPL (tdx_get_sysinfo); +int tdx_guest_keyid_alloc (void ) { return ida_alloc_range(&tdx_guest_keyid_pool, tdx_guest_keyid_start,
arch/x86/virt/vmx/tdx/tdx.h +0 -1
@@ -3,7 +3,6 @@#define _X86_VIRT_TDX_H#include <linux/bits.h> -#include "tdx_global_metadata.h" /* * This file contains both macros and data structures defined by the TDX
include/linux/kvm_host.h +1 -0
@@ -2284,6 +2284,7 @@ static inline bool kvm_check_request(int req, struct kvm_vcpu *vcpu) }#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING +extern bool enable_virt_at_load;extern bool kvm_rebooting;#endif
virt/kvm/kvm_main.c +2 -1
@@ -5464,8 +5464,9 @@ static struct miscdevice kvm_dev = { };#ifdef CONFIG_KVM_GENERIC_HARDWARE_ENABLING -static bool enable_virt_at_load = true; +bool enable_virt_at_load = true;module_param (enable_virt_at_load, bool,0444 ); +EXPORT_SYMBOL_GPL (enable_virt_at_load); __visible bool kvm_rebooting;EXPORT_SYMBOL_GPL (kvm_rebooting);
Signature · 1 line
2.43.5
Re: [PATCH 12/30] KVM: VMX: Initialize TDX during KVM module load
Quoted 40 lines
(quoted diff) +38
-0+ +static void __do_tdx_cleanup(void) +{ + /* + * Once TDX module is initialized, it cannot be disabled and + * re-initialized again w/o runtime update (which isn't + * supported by kernel). Only need to remove the cpuhp here. + * The TDX host core code tracks TDX status and can handle + * 'multiple enabling' scenario. + */ + WARN_ON_ONCE(!tdx_cpuhp_state); + cpuhp_remove_state_nocalls(tdx_cpuhp_state); + tdx_cpuhp_state = 0; +} + +static int __init __do_tdx_bringup(void) +{ + int r; + + /* + * TDX-specific cpuhp callback to call tdx_cpu_enable() on all + * online CPUs before calling tdx_enable(), and on any new + * going-online CPU to make sure it is ready for TDX guest. + */ + r = cpuhp_setup_state_cpuslocked(CPUHP_AP_ONLINE_DYN, + "kvm/cpu/tdx:online", + tdx_online_cpu, NULL); + if (r < 0) + return r; + + tdx_cpuhp_state = r; + + r = tdx_enable(); + if (r) + __do_tdx_cleanup(); + + return r; +}
[...]
Quoted 6 lines
(quoted diff) +6
-0+static int __init __tdx_bringup(void) +{ + int r; + + /* + * Enabling TDX requires enabling hardware virtualization first,
Review
Quoted 10 lines
(quoted diff) +10
-0+ * as making SEAMCALLs requires CPU being in post-VMXON state. + */ + r = kvm_enable_virtualization(); + if (r) + return r; + + cpus_read_lock(); + r = __do_tdx_bringup(); + cpus_read_unlock(); +
Hi Paolo,
This patch still doesn't address a bug Chao pointed out, that the __do_tdx_cleanup() can be called from __do_tdx_bringup() with cpus_read_lock() being hold, so we need to use cpuhp_remove_state_nocalls_cpuslocked() in __do_tdx_cleanup().
I posted a diff to address here:
https://lore.kernel.org/lkml/[email protected]/T/#m1e86328e69b27e6cc9978f90df923144d699c350
It would be great if you could squash to the kvm-coco-queue. There will be some minor rebase conflict to the rest patches, though, so if you want me to send out fixup patch(es) for you to squash please do let me know.
Btw, the diff also moves the 'enable_virt_at_load' check to kvm_can_support_tdx(), which isn't related to this issue. Below is the diff (also attached) w/o this code change but only to address the above bug if you prefer.
arch/x86/kvm/vmx/tdx.c +9 -2
@@ -38,10 +38,17 @@ static void __do_tdx_cleanup(void)* 'multiple enabling' scenario. */ WARN_ON_ONCE (!tdx_cpuhp_state); -cpuhp_remove_state_nocalls (tdx_cpuhp_state); +cpuhp_remove_state_nocalls_cpuslocked (tdx_cpuhp_state); tdx_cpuhp_state =0 ; } +static void __tdx_cleanup (void ) +{ +cpus_read_lock (); +__do_tdx_cleanup (); +cpus_read_unlock (); +} +static int __init __do_tdx_bringup (void ) {int r;
@@ -103,7 +110,7 @@ static int __init __tdx_bringup(void)void tdx_cleanup (void ) {if (enable_tdx) { -__do_tdx_cleanup (); +__tdx_cleanup ();kvm_disable_virtualization (); } }
arch/x86/kvm/vmx/tdx.c +9 -2
@@ -38,10 +38,17 @@ static void __do_tdx_cleanup(void)* 'multiple enabling' scenario. */ WARN_ON_ONCE (!tdx_cpuhp_state); -cpuhp_remove_state_nocalls (tdx_cpuhp_state); +cpuhp_remove_state_nocalls_cpuslocked (tdx_cpuhp_state); tdx_cpuhp_state =0 ; } +static void __tdx_cleanup (void ) +{ +cpus_read_lock (); +__do_tdx_cleanup (); +cpus_read_unlock (); +} +static int __init __do_tdx_bringup (void ) {int r;
@@ -103,7 +110,7 @@ static int __init __tdx_bringup(void)void tdx_cleanup (void ) {if (enable_tdx) { -__do_tdx_cleanup (); +__tdx_cleanup ();kvm_disable_virtualization (); } }
Paolo Bonzini
maintainerRe: [PATCH 12/30] KVM: VMX: Initialize TDX during KVM module load
Quoted 11 lines · Kai
Hi Paolo,
This patch still doesn't address a bug Chao pointed out, that the
__do_tdx_cleanup()can be called from__do_tdx_bringup()withcpus_read_lock()being hold, so we need to usecpuhp_remove_state_nocalls_cpuslocked()in__do_tdx_cleanup().I posted a diff to address here:
https://lore.kernel.org/lkml/[email protected]/T/#m1e86328e69b27e6cc9978f90df923144d699c350
Quoted 8 lines
It would be great if you could squash to the kvm-coco-queue. There will be some minor rebase conflict to the rest patches, though, so if you want me to send out fixup patch(es) for you to squash please do let me know.
Btw, the diff also moves the '
enable_virt_at_load' check tokvm_can_support_tdx(), which isn't related to this issue. Below is the diff (also attached) w/o this code change but only to address the above bug if you prefer.
Thank, I applied this one. In fact I think we can remove kvm_can_support_tdx() altogether and inline it in tdx_bringup(), since there are other checks like MOVDIR64B.
The conflicts are not problematic so I'm happy to solve them for you.
Paolo
Re: [PATCH 12/30] KVM: VMX: Initialize TDX during KVM module load
Quoted 16 lines · Paolo Bonzini
Quoted 15 lines · Kai
Hi Paolo,
This patch still doesn't address a bug Chao pointed out, that the
__do_tdx_cleanup()can be called from__do_tdx_bringup()withcpus_read_lock()being hold, so we need to usecpuhp_remove_state_nocalls_cpuslocked()in__do_tdx_cleanup().I posted a diff to address here:
https://lore.kernel.org/lkml/[email protected]/T/#m1e86328e69b27e6cc9978f90df923144d699c350
It would be great if you could squash to the kvm-coco-queue. There will be some minor rebase conflict to the rest patches, though, so if you want me to send out fixup patch(es) for you to squash please do let me know.
Quoted 7 lines
Quoted 4 lines
Btw, the diff also moves the '
enable_virt_at_load' check tokvm_can_support_tdx(), which isn't related to this issue. Below is the diff (also attached) w/o this code change but only to address the above bug if you prefer.Thank, I applied this one.
Thanks!
Quoted 3 lines
In fact I think we can remove
kvm_can_support_tdx()altogether and inline it intdx_bringup(), since there are other checks like MOVDIR64B.
Or we can put all the pre-requirement checks to kvm_can_support_tdx() -- both work for me :-)
Quoted 2 lines
The conflicts are not problematic so I'm happy to solve them for you.
Thanks Paolo!
Paolo Bonzini
maintainerPATCH v3 13/30 KVM: TDX: Get TDX global information
In reply to Paolo BonziniFrom: Kai Huang <[email protected]>
KVM will need to consult some essential TDX global information to create and run TDX guests. Get the global information after initializing TDX.
Message-ID: <[email protected]>
--- arch/x86/kvm/vmx/tdx.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
arch/x86/kvm/vmx/tdx.c +11 -0
@@ -13,6 +13,8 @@ module_param_named(tdx, enable_tdx, bool, 0444);static enum cpuhp_state tdx_cpuhp_state; +static const struct tdx_sys_info *tdx_sysinfo; +static int tdx_online_cpu (unsigned int cpu) {unsigned long flags;
@@ -90,11 +92,20 @@ static int __init __tdx_bringup(void)if (r) goto tdx_bringup_err; +/* Get TDX global information for later use */ + tdx_sysinfo =tdx_get_sysinfo (); +if (WARN_ON_ONCE (!tdx_sysinfo)) { + r = -EINVAL ; + goto get_sysinfo_err; + } +/* * Leave hardware virtualization enabled after TDX is enabled * successfully. TDX CPU hotplug depends on this. */ return 0 ; +get_sysinfo_err: +__do_tdx_cleanup (); tdx_bringup_err:kvm_disable_virtualization ();return r;
Signature · 1 line
2.43.5
Re: [PATCH 13/30] KVM: TDX: Get TDX global information
Quoted 34 lines · Paolo Bonzini
From: Kai Huang <[email protected]>
KVM will need to consult some essential TDX global information to create and run TDX guests. Get the global information after initializing TDX.
Signed-off-by Kai Huang <[email protected]>Signed-off-by Rick Edgecombe <[email protected]>Message-ID: <[email protected]>
Signed-off-by Paolo Bonzini <[email protected]>--- arch/x86/kvm/vmx/tdx.c | 11 +++++++++++ 1 file changed, 11 insertions(+)arch/x86/kvm/vmx/tdx.c +6
-0@@ -13,6 +13,8 @@ module_param_named(tdx, enable_tdx, bool, 0444);static enum cpuhp_state tdx_cpuhp_state; +static const struct tdx_sys_info *tdx_sysinfo; +static int tdx_online_cpu (unsigned int cpu) {unsigned long flags;@@ -90,11 +92,20 @@ static int __init __tdx_bringup(void)if (r) goto tdx_bringup_err; +/* Get TDX global information for later use */ + tdx_sysinfo =tdx_get_sysinfo (); +if (WARN_ON_ONCE (!tdx_sysinfo)) { + r = -EINVAL ;
arch/x86/kvm/vmx/tdx.c static int __init __tdx_bringup(void) · line 108
Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +5
-0+ goto get_sysinfo_err; + } +/* * Leave hardware virtualization enabled after TDX is enabled * successfully. TDX CPU hotplug depends on this. */ return 0 ; +get_sysinfo_err: +__do_tdx_cleanup ();
We need to call __tdx_cleanup() after we fix the bug in the previous patch using the diff I provided:
arch/x86/kvm/vmx/tdx.c +1 -1
@@ -112,7 +112,7 @@ static int __init __tdx_bringup(void)*/ return 0 ; get_sysinfo_err: -__do_tdx_cleanup (); +__tdx_cleanup (); tdx_bringup_err:kvm_disable_virtualization ();return r;
Paolo Bonzini
maintainerPATCH v3 14/30 KVM: TDX: Add placeholders for TDX VM/vCPU structures
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Add TDX's own VM and vCPU structures as placeholder to manage and run TDX guests. Also add helper functions to check whether a VM/vCPU is TDX or normal VMX one, and add helpers to convert between TDX VM/vCPU and KVM VM/vCPU.
TDX protects guest VMs from malicious host. Unlike VMX guests, TDX guests are crypto-protected. KVM cannot access TDX guests' memory and vCPU states directly. Instead, TDX requires KVM to use a set of TDX architecture-defined firmware APIs (a.k.a TDX module SEAMCALLs) to manage and run TDX guests.
In fact, the way to manage and run TDX guests and normal VMX guests are quite different. Because of that, the current structures ('struct kvm_vmx' and 'struct vcpu_vmx') to manage VMX guests are not quite suitable for TDX guests. E.g., the majority of the members of 'struct vcpu_vmx' don't apply to TDX guests.
Introduce TDX's own VM and vCPU structures ('struct kvm_tdx' and 'struct vcpu_tdx' respectively) for KVM to manage and run TDX guests. And instead of building TDX's VM and vCPU structures based on VMX's, build them directly based on 'struct kvm'.
As a result, TDX and VMX guests will have different VM size and vCPU size/alignment.
Currently, kvm_arch_alloc_vm() uses 'kvm_x86_ops::vm_size' to allocate enough space for the VM structure when creating guest. With TDX guests, ideally, KVM should allocate the VM structure based on the VM type so that the precise size can be allocated for VMX and TDX guests. But this requires more extensive code change. For now, simply choose the maximum size of 'struct kvm_tdx' and 'struct kvm_vmx' for VM structure allocation for both VMX and TDX guests. This would result in small memory waste for each VM which has smaller VM structure size but this is acceptable.
For simplicity, use the same way for vCPU allocation too. Otherwise KVM would need to maintain a separate 'kvm_vcpu_cache' for each VM type.
Note, updating the 'vt_x86_ops::vm_size' needs to be done before calling kvm_ops_update(), which copies vt_x86_ops to kvm_x86_ops. However this happens before TDX module initialization. Therefore theoretically it is possible that 'kvm_x86_ops::vm_size' is set to size of 'struct kvm_tdx' (when it's larger) but TDX actually fails to initialize at a later time.
Again the worst case of this is wasting couple of bytes memory for each VM. KVM could choose to update 'kvm_x86_ops::vm_size' at a later time depending on TDX's status but that would require base KVM module to export either kvm_x86_ops or kvm_ops_update().
---
- Make to_kvm_tdx() and to_tdx() private to tdx.c (Francesco, Tony)
- Add pragma poison for to_vmx() (Paolo)
--- arch/x86/kvm/vmx/main.c | 53 ++++++++++++++++++++++++++++++++++++++--- arch/x86/kvm/vmx/tdx.c | 14 ++++++++++- arch/x86/kvm/vmx/tdx.h | 37 ++++++++++++++++++++++++++++ 3 files changed, 100 insertions(+), 4 deletions(-)
arch/x86/kvm/vmx/main.c +50 -3
@@ -8,6 +8,39 @@#include "posted_intr.h" #include "tdx.h" +static __init int vt_hardware_setup (void ) +{ +int ret; + + ret =vmx_hardware_setup (); +if (ret) +return ret; + +/* +* Update vt_x86_ops::vm_size here so it is ready before +* kvm_ops_update() is called in kvm_x86_vendor_init(). +* +* Note, the actual bringing up of TDX must be done after +* kvm_ops_update() because enabling TDX requires enabling +* hardware virtualization first, i.e., all online CPUs must +* be in post-VMXON state. This means the @vm_size here +* may be updated to TDX's size but TDX may fail to enable +* at later time. +* +* The VMX/VT code could update kvm_x86_ops::vm_size again +* after bringing up TDX, but this would require exporting +* either kvm_x86_ops or kvm_ops_update() from the base KVM +* module, which looks overkill. Anyway, the worst case here +* is KVM may allocate couple of more bytes than needed for +* each VM. +*/ +if (enable_tdx) + vt_x86_ops.vm_size = max_t(unsigned int, vt_x86_ops.vm_size, +sizeof (struct kvm_tdx )); + +return 0 ; +} +#define VMX_REQUIRED_APICV_INHIBITS \ (BIT(APICV_INHIBIT_REASON_DISABLED) | \ BIT(APICV_INHIBIT_REASON_ABSENT) | \
@@ -163,7 +196,7 @@ struct kvm_x86_ops vt_x86_ops __initdata = { };struct kvm_x86_init_ops vt_init_ops__initdata = { - .hardware_setup = vmx_hardware_setup, + .hardware_setup = vt_hardware_setup, .handle_intel_pt_intr =NULL , .runtime_ops = &vt_x86_ops,
@@ -180,6 +213,7 @@ module_exit(vt_exit);static int __init vt_init (void ) { +unsigned vcpu_size, vcpu_align;int r; r =vmx_init ();
@@ -191,12 +225,25 @@ static int __init vt_init(void)if (r) goto err_tdx_bringup; +/* +* TDX and VMX have different vCPU structures. Calculate the +* maximum size/align so that kvm_init() can use the larger +* values to create the kmem_vcpu_cache. +*/ + vcpu_size =sizeof (struct vcpu_vmx ); + vcpu_align = __alignof__(struct vcpu_vmx ); +if (enable_tdx) { + vcpu_size =max_t (unsigned, vcpu_size, +sizeof (struct vcpu_tdx )); + vcpu_align =max_t (unsigned, vcpu_align, + __alignof__(struct vcpu_tdx )); + } +/* * Common KVM initialization _must_ come last, after this, /dev/kvm is * exposed to userspace! */ - r =kvm_init (sizeof (struct vcpu_vmx ), __alignof__(struct vcpu_vmx ), -THIS_MODULE ); + r =kvm_init (vcpu_size, vcpu_align,THIS_MODULE );if (r) goto err_kvm_init;
arch/x86/kvm/vmx/tdx.c +13 -1
@@ -5,16 +5,28 @@#include "capabilities.h" #include "tdx.h" +#pragma GCC poison to_vmx +#undef pr_fmt#define pr_fmt (fmt) KBUILD_MODNAME ": " fmt -static bool enable_tdx__ro_after_init ; +bool enable_tdx__ro_after_init ;module_param_named (tdx, enable_tdx, bool,0444 );static enum cpuhp_state tdx_cpuhp_state;static const struct tdx_sys_info *tdx_sysinfo; +static __always_inline struct kvm_tdx *to_kvm_tdx(struct kvm *kvm) +{ + return container_of(kvm, struct kvm_tdx, kvm); +} + +static __always_inline struct vcpu_tdx *to_tdx(struct kvm_vcpu *vcpu) +{ + return container_of(vcpu, struct vcpu_tdx, vcpu); +} +static int tdx_online_cpu (unsigned int cpu) {unsigned long flags;
arch/x86/kvm/vmx/tdx.h +37 -0
@@ -5,9 +5,46 @@#ifdef CONFIG_INTEL_TDX_HOST int tdx_bringup (void );void tdx_cleanup (void ); + +extern bool enable_tdx; + +struct kvm_tdx { +struct kvm kvm; +/* TDX specific members follow. */ +}; + +struct vcpu_tdx { +struct kvm_vcpu vcpu; +/* TDX specific members follow. */ +}; + +static inline bool is_td (struct kvm *kvm) +{ +return kvm->arch.vm_type ==KVM_X86_TDX_VM ; +} + +static inline bool is_td_vcpu (struct kvm_vcpu *vcpu) +{ +return is_td (vcpu->kvm); +} +#else static inline int tdx_bringup (void ) {return 0 ; }static inline void tdx_cleanup (void ) {} + +#define enable_tdx 0 + +struct kvm_tdx { +struct kvm kvm; +}; + +struct vcpu_tdx { +struct kvm_vcpu vcpu; +}; + +static inline bool is_td (struct kvm *kvm) {return false; } +static inline bool is_td_vcpu (struct kvm_vcpu *vcpu) {return false; } +#endif #endif
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 15/30 KVM: TDX: Define TDX architectural definitions
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Define architectural definitions for KVM to issue the TDX SEAMCALLs.
Structures and values that are architecturally defined in the TDX module specifications the chapter of ABI Reference.
---
- Drop old duplicate defines, the x86 core exports what's needed (Kai)
--- arch/x86/kvm/vmx/tdx.h | 2 + arch/x86/kvm/vmx/tdx_arch.h | 123 ++++++++++++++++++++++++++++++++++++ 2 files changed, 125 insertions(+) create mode 100644 arch/x86/kvm/vmx/tdx_arch.h
arch/x86/kvm/vmx/tdx.h +2 -0
@@ -2,6 +2,8 @@#ifndef __KVM_X86_VMX_TDX_H#define __KVM_X86_VMX_TDX_H +#include "tdx_arch.h" +#ifdef CONFIG_INTEL_TDX_HOST int tdx_bringup (void );void tdx_cleanup (void );
arch/x86/kvm/vmx/tdx_arch.h new file +123 -0
123 lines not on this page · raw message
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 16/30 KVM: TDX: Add TDX "architectural" error codes
In reply to Paolo BonziniFrom: Sean Christopherson <[email protected]>
Add error codes for the TDX SEAMCALLs both for TDX VMM side for TDH SEAMCALL and TDX guest side for TDG.VP.VMCALL. KVM issues the TDX SEAMCALLs and checks its error code. KVM handles hypercall from the TDX guest and may return an error. So error code for the TDX guest is also needed.
TDX SEAMCALL uses bits 31:0 to return more information, so these error codes will only exactly match RAX[63:32]. Error codes for TDG.VP.VMCALL is defined by TDX Guest-Host-Communication interface spec.
Message-ID: <[email protected]>
--- arch/x86/include/asm/shared/tdx.h | 7 +++++- arch/x86/kvm/vmx/tdx.h | 1 + arch/x86/kvm/vmx/tdx_errno.h | 36 +++++++++++++++++++++++++++++++ 3 files changed, 43 insertions(+), 1 deletion(-) create mode 100644 arch/x86/kvm/vmx/tdx_errno.h
arch/x86/include/asm/shared/tdx.h +6 -1
@@ -71,7 +71,12 @@#define TDVMCALL_GET_QUOTE 0x10002#define TDVMCALL_REPORT_FATAL_ERROR 0x10003 -#define TDVMCALL_STATUS_RETRY 1 +/* +* TDG.VP.VMCALL Status Codes (returned in R10) +*/ +#define TDVMCALL_STATUS_SUCCESS 0x0000000000000000ULL +#define TDVMCALL_STATUS_RETRY 0x0000000000000001ULL +#define TDVMCALL_STATUS_INVALID_OPERAND 0x8000000000000000ULL/* * Bitmasks of exposed registers (with VMM).
arch/x86/kvm/vmx/tdx.h +1 -0
@@ -3,6 +3,7 @@#define __KVM_X86_VMX_TDX_H#include "tdx_arch.h" +#include "tdx_errno.h" #ifdef CONFIG_INTEL_TDX_HOST int tdx_bringup (void );
arch/x86/kvm/vmx/tdx_errno.h new file +36 -0
@@ -0,0 +1,36 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* architectural status code for SEAMCALL */ + +#ifndef __KVM_X86_TDX_ERRNO_H +#define __KVM_X86_TDX_ERRNO_H + +#define TDX_SEAMCALL_STATUS_MASK 0xFFFFFFFF00000000ULL + +/* +* TDX SEAMCALL Status Codes (returned in RAX) +*/ +#define TDX_NON_RECOVERABLE_VCPU 0x4000000100000000ULL +#define TDX_INTERRUPTED_RESUMABLE 0x8000000300000000ULL +#define TDX_OPERAND_INVALID 0xC000010000000000ULL +#define TDX_OPERAND_BUSY 0x8000020000000000ULL +#define TDX_PREVIOUS_TLB_EPOCH_BUSY 0x8000020100000000ULL +#define TDX_PAGE_METADATA_INCORRECT 0xC000030000000000ULL +#define TDX_VCPU_NOT_ASSOCIATED 0x8000070200000000ULL +#define TDX_KEY_GENERATION_FAILED 0x8000080000000000ULL +#define TDX_KEY_STATE_INCORRECT 0xC000081100000000ULL +#define TDX_KEY_CONFIGURED 0x0000081500000000ULL +#define TDX_NO_HKID_READY_TO_WBCACHE 0x0000082100000000ULL +#define TDX_FLUSHVP_NOT_DONE 0x8000082400000000ULL +#define TDX_EPT_WALK_FAILED 0xC0000B0000000000ULL +#define TDX_EPT_ENTRY_STATE_INCORRECT 0xC0000B0D00000000ULL + +/* +* TDX module operand ID, appears in 31:0 part of error code as +* detail information +*/ +#define TDX_OPERAND_ID_RCX 0x01 +#define TDX_OPERAND_ID_TDR 0x80 +#define TDX_OPERAND_ID_SEPT 0x92 +#define TDX_OPERAND_ID_TD_EPOCH 0xa9 + +#endif /* __KVM_X86_TDX_ERRNO_H */
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 17/30 KVM: TDX: Add helper functions to print TDX SEAMCALL error
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Add helper functions to print out errors from the TDX module in a uniform manner.
--- arch/x86/kvm/vmx/tdx.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
arch/x86/kvm/vmx/tdx.c +15 -0
@@ -10,6 +10,21 @@#undef pr_fmt#define pr_fmt (fmt) KBUILD_MODNAME ": " fmt +#define pr_tdx_error (__fn, __err) \ + pr_err_ratelimited("SEAMCALL %s failed: 0x%llx\n", #__fn, __err) + +#define __pr_tdx_error_N (__fn_str, __err, __fmt, ...) \ + pr_err_ratelimited("SEAMCALL " __fn_str " failed: 0x%llx, " __fmt, __err, __VA_ARGS__) + +#define pr_tdx_error_1 (__fn, __err, __rcx) \ + __pr_tdx_error_N(#__fn, __err, "rcx 0x%llx\n", __rcx) + +#define pr_tdx_error_2 (__fn, __err, __rcx, __rdx) \ + __pr_tdx_error_N(#__fn, __err, "rcx 0x%llx, rdx 0x%llx\n", __rcx, __rdx) + +#define pr_tdx_error_3 (__fn, __err, __rcx, __rdx, __r8) \ + __pr_tdx_error_N(#__fn, __err, "rcx 0x%llx, rdx 0x%llx, r8 0x%llx\n", __rcx, __rdx, __r8) +bool enable_tdx__ro_after_init ;module_param_named (tdx, enable_tdx, bool,0444 );
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 18/30 KVM: TDX: Add place holder for TDX VM specific mem_enc_op ioctl
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
KVM_MEMORY_ENCRYPT_OP was introduced for VM-scoped operations specific for guest state-protected VM. It defined subcommands for technology-specific operations under KVM_MEMORY_ENCRYPT_OP. Despite its name, the subcommands are not limited to memory encryption, but various technology-specific operations are defined. It's natural to repurpose KVM_MEMORY_ENCRYPT_OP for TDX specific operations and define subcommands.
Add a place holder function for TDX specific VM-scoped ioctl as mem_enc_op. TDX specific sub-commands will be added to retrieve/pass TDX specific parameters. Make mem_enc_ioctl non-optional as it's always filled.
---
- Drop the misleading "defined for consistency" line. It's a copy-paste error introduced in the earlier patches. Earlier there was padding at the end to match struct kvm_sev_cmd size. (Tony)
--- arch/x86/include/asm/kvm-x86-ops.h | 2 +- arch/x86/include/uapi/asm/kvm.h | 23 +++++++++++++++++++++ arch/x86/kvm/vmx/main.c | 10 ++++++++++ arch/x86/kvm/vmx/tdx.c | 32 ++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/x86_ops.h | 6 ++++++ arch/x86/kvm/x86.c | 4 ---- 6 files changed, 72 insertions(+), 5 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +1 -1
@@ -125,7 +125,7 @@ KVM_X86_OP(leave_smm) KVM_X86_OP(enable_smi_window) #endif KVM_X86_OP_OPTIONAL(dev_get_attr) -KVM_X86_OP_OPTIONAL(mem_enc_ioctl) +KVM_X86_OP(mem_enc_ioctl) KVM_X86_OP_OPTIONAL(mem_enc_register_region) KVM_X86_OP_OPTIONAL(mem_enc_unregister_region) KVM_X86_OP_OPTIONAL(vm_copy_enc_context_from)
arch/x86/include/uapi/asm/kvm.h +23 -0
@@ -927,4 +927,27 @@ struct kvm_hyperv_eventfd {#define KVM_X86_SNP_VM 4#define KVM_X86_TDX_VM 5 +/* Trust Domain eXtension sub-ioctl() commands. */ +enum kvm_tdx_cmd_id { +KVM_TDX_CMD_NR_MAX , +}; + +struct kvm_tdx_cmd { +/* enum kvm_tdx_cmd_id */ +__u32 id; +/* flags for sub-commend. If sub-command doesn't use this, set zero. */ +__u32 flags; +/* +* data for each sub-command. An immediate or a pointer to the actual +* data in process virtual address. If sub-command doesn't use it, +* set zero. +*/ +__u64 data; +/* +* Auxiliary error code. The sub-command may return TDX SEAMCALL +* status code in addition to -Exxx. +*/ +__u64 hw_error; +}; +#endif /* _ASM_X86_KVM_H */
arch/x86/kvm/vmx/main.c +10 -0
@@ -41,6 +41,14 @@ static __init int vt_hardware_setup(void)return 0 ; } +static int vt_mem_enc_ioctl (struct kvm *kvm,void __user *argp) +{ +if (!is_td (kvm)) +return -ENOTTY ; + +return tdx_vm_ioctl (kvm, argp); +} +#define VMX_REQUIRED_APICV_INHIBITS \ (BIT(APICV_INHIBIT_REASON_DISABLED) | \ BIT(APICV_INHIBIT_REASON_ABSENT) | \
@@ -193,6 +201,8 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .vcpu_deliver_sipi_vector = kvm_vcpu_deliver_sipi_vector, .get_untagged_addr = vmx_get_untagged_addr, + + .mem_enc_ioctl = vt_mem_enc_ioctl, };struct kvm_x86_init_ops vt_init_ops__initdata = {
arch/x86/kvm/vmx/tdx.c +32 -0
@@ -3,6 +3,7 @@#include <asm/cpufeature.h> #include <asm/tdx.h> #include "capabilities.h" +#include "x86_ops.h" #include "tdx.h" #pragma GCC poison to_vmx
@@ -42,6 +43,37 @@ static __always_inline struct vcpu_tdx *to_tdx(struct kvm_vcpu *vcpu) return container_of(vcpu, struct vcpu_tdx, vcpu); } +int tdx_vm_ioctl (struct kvm *kvm,void __user *argp) +{ +struct kvm_tdx_cmd tdx_cmd; +int r; + +if (copy_from_user (&tdx_cmd, argp,sizeof (struct kvm_tdx_cmd ))) +return -EFAULT ; + +/* +* Userspace should never set hw_error. It is used to fill +* hardware-defined error by the kernel. +*/ +if (tdx_cmd.hw_error) +return -EINVAL ; + +mutex_lock (&kvm->lock); + +switch (tdx_cmd.id) { +default : + r = -EINVAL ; + goto out; + } + +if (copy_to_user (argp, &tdx_cmd,sizeof (struct kvm_tdx_cmd ))) + r = -EFAULT ; + +out: +mutex_unlock (&kvm->lock); +return r; +} +static int tdx_online_cpu (unsigned int cpu) {unsigned long flags;
arch/x86/kvm/vmx/x86_ops.h +6 -0
@@ -121,4 +121,10 @@ void vmx_cancel_hv_timer(struct kvm_vcpu *vcpu);#endif void vmx_setup_mce (struct kvm_vcpu *vcpu); +#ifdef CONFIG_INTEL_TDX_HOST +int tdx_vm_ioctl (struct kvm *kvm,void __user *argp); +#else +static inline int tdx_vm_ioctl (struct kvm *kvm,void __user *argp) {return -EOPNOTSUPP ; } +#endif +#endif /* __KVM_X86_VMX_X86_OPS_H */
arch/x86/kvm/x86.c +0 -4
@@ -7277,10 +7277,6 @@ int kvm_arch_vm_ioctl(struct file *filp, unsigned int ioctl, unsigned long arg) goto out; }case KVM_MEMORY_ENCRYPT_OP : { - r = -ENOTTY ; -if (!kvm_x86_ops.mem_enc_ioctl) - goto out; - r =kvm_x86_call (mem_enc_ioctl)(kvm, argp);break ; }
Signature · 1 line
2.43.5
Re: [PATCH 18/30] KVM: TDX: Add place holder for TDX VM specific mem_enc_op ioctl
Quoted 49 lines · Paolo Bonzini
From: Isaku Yamahata <[email protected]>
KVM_MEMORY_ENCRYPT_OPwas introduced for VM-scoped operations specific for guest state-protected VM. It defined subcommands for technology-specific operations underKVM_MEMORY_ENCRYPT_OP. Despite its name, the subcommands are not limited to memory encryption, but various technology-specific operations are defined. It's natural to repurposeKVM_MEMORY_ENCRYPT_OPfor TDX specific operations and define subcommands.Add a place holder function for TDX specific VM-scoped ioctl as
mem_enc_op. TDX specific sub-commands will be added to retrieve/pass TDX specific parameters. Makemem_enc_ioctlnon-optional as it's always filled.Signed-off-by Isaku Yamahata <[email protected]>Co-developed-by Tony Lindgren <[email protected]>Signed-off-by Tony Lindgren <[email protected]>Signed-off-by Rick Edgecombe <[email protected]>---
- Drop the misleading "defined for consistency" line. It's a copy-paste error introduced in the earlier patches. Earlier there was padding at the end to match structkvm_sev_cmdsize. (Tony)Signed-off-by Paolo Bonzini <[email protected]>--- arch/x86/include/asm/kvm-x86-ops.h | 2 +- arch/x86/include/uapi/asm/kvm.h | 23 +++++++++++++++++++++ arch/x86/kvm/vmx/main.c | 10 ++++++++++ arch/x86/kvm/vmx/tdx.c | 32 ++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/x86_ops.h | 6 ++++++ arch/x86/kvm/x86.c | 4 ---- 6 files changed, 72 insertions(+), 5 deletions(-)arch/x86/include/asm/kvm-x86-ops.h +1
-1@@ -125,7 +125,7 @@ KVM_X86_OP(leave_smm) KVM_X86_OP(enable_smi_window) #endif KVM_X86_OP_OPTIONAL(dev_get_attr) -KVM_X86_OP_OPTIONAL(mem_enc_ioctl) +KVM_X86_OP(mem_enc_ioctl) KVM_X86_OP_OPTIONAL(mem_enc_register_region) KVM_X86_OP_OPTIONAL(mem_enc_unregister_region) KVM_X86_OP_OPTIONAL(vm_copy_enc_context_from)arch/x86/include/uapi/asm/kvm.h +0
-0
arch/x86/include/uapi/asm/kvm.h struct kvm_hyperv_eventfd { · line 930
Quoted 4 lines
arch/x86/include/uapi/asm/kvm.h +1
-0@@ -927,4 +927,27 @@ struct kvm_hyperv_eventfd {#define KVM_X86_SNP_VM 4#define KVM_X86_TDX_VM 5 +/* Trust Domain eXtension sub-ioctl() commands. */
(came from reviewing the KVM TDX documentation patch)
Nitpickings:
eXtension -> Extensions, since the latter is used widely in other places (and already used in the upstream kernel).
'sub-command(s)' is used in the changelog, and in below as well. For consistency I think we can change 'sub-ioctl() commands' to 'sub-commands'.
arch/x86/include/uapi/asm/kvm.h struct kvm_hyperv_eventfd { · line 938
Quoted 8 lines
arch/x86/include/uapi/asm/kvm.h +8
-0+enum kvm_tdx_cmd_id { +KVM_TDX_CMD_NR_MAX , +}; + +struct kvm_tdx_cmd { +/* enum kvm_tdx_cmd_id */ +__u32 id; +/* flags for sub-commend. If sub-command doesn't use this, set zero. */
^ sub-command.
Quoted 13 lines
arch/x86/include/uapi/asm/kvm.h +13
-0+__u32 flags; +/* +* data for each sub-command. An immediate or a pointer to the actual +* data in process virtual address. If sub-command doesn't use it, +* set zero. +*/ +__u64 data; +/* +* Auxiliary error code. The sub-command may return TDX SEAMCALL +* status code in addition to -Exxx. +*/ +__u64 hw_error; +};
Paolo Bonzini
maintainerPATCH v3 19/30 KVM: TDX: Get system-wide info about TDX module on initialization
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
TDX KVM needs system-wide information about the TDX module. Generate the data based on tdx_sysinfo td_conf CPUID data.
---
- Clarify comment about EAX[23:16] in td_init_cpuid_entry2() (Xiaoyao)
- Add comment for configurable CPUID bits (Xiaoyao)
--- arch/x86/include/uapi/asm/kvm.h | 11 +++ arch/x86/kvm/vmx/tdx.c | 137 ++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/tdx_arch.h | 2 + 3 files changed, 150 insertions(+)
arch/x86/include/uapi/asm/kvm.h +11 -0
@@ -929,6 +929,8 @@ struct kvm_hyperv_eventfd {/* Trust Domain eXtension sub-ioctl() commands. */ enum kvm_tdx_cmd_id { +KVM_TDX_CAPABILITIES =0 , +KVM_TDX_CMD_NR_MAX , };
@@ -950,4 +952,13 @@ struct kvm_tdx_cmd { __u64 hw_error; }; +struct kvm_tdx_capabilities { +__u64 supported_attrs; +__u64 supported_xfam; +__u64 reserved[254 ]; + +/* Configurable CPUID bits for userspace */ +struct kvm_cpuid2 cpuid; +}; +#endif /* _ASM_X86_KVM_H */
arch/x86/kvm/vmx/tdx.c +137 -0
166 lines not on this page · raw message
arch/x86/kvm/vmx/tdx_arch.h +2 -0
@@ -120,4 +120,6 @@ struct td_params {#define TDX_MIN_TSC_FREQUENCY_KHZ (100 * 1000)#define TDX_MAX_TSC_FREQUENCY_KHZ (10 * 1000 * 1000) +#define MD_FIELD_ID_FEATURES0_TOPOLOGY_ENUM BIT_ULL(20) +#endif /* __KVM_X86_TDX_ARCH_H */
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 20/30 KVM: TDX: create/destroy VM structure
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Implement managing the TDX private KeyID to implement, create, destroy and free for a TDX guest.
When creating at TDX guest, assign a TDX private KeyID for the TDX guest for memory encryption, and allocate pages for the guest. These are used for the Trust Domain Root (TDR) and Trust Domain Control Structure (TDCS).
On destruction, free the allocated pages, and the KeyID.
Before tearing down the private page tables, TDX requires the guest TD to be destroyed by reclaiming the KeyID. Do it at vm_destroy() kvm_x86_ops hook.
Add a call for vm_free() at the end of kvm_arch_destroy_vm() because the per-VM TDR needs to be freed after the KeyID.
---
- Fix build issue in kvm-coco-queue
- Init ret earlier to fix __tdx_td_init() error handling. (Chao)
- Standardize -EAGAIN for __tdx_td_init() retry errors (Rick)
--- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/Kconfig | 2 + arch/x86/kvm/vmx/main.c | 28 +- arch/x86/kvm/vmx/tdx.c | 450 +++++++++++++++++++++++++++++ arch/x86/kvm/vmx/tdx.h | 4 +- arch/x86/kvm/vmx/x86_ops.h | 6 + arch/x86/kvm/x86.c | 1 + 8 files changed, 490 insertions(+), 3 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +1 -0
@@ -21,6 +21,7 @@ KVM_X86_OP(has_emulated_msr) KVM_X86_OP(vcpu_after_set_cpuid) KVM_X86_OP(vm_init) KVM_X86_OP_OPTIONAL(vm_destroy) +KVM_X86_OP_OPTIONAL(vm_free) KVM_X86_OP_OPTIONAL_RET0(vcpu_precreate) KVM_X86_OP(vcpu_create) KVM_X86_OP(vcpu_free)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1663,6 +1663,7 @@ struct kvm_x86_ops {unsigned int vm_size;int (*vm_init)(struct kvm *kvm);void (*vm_destroy)(struct kvm *kvm); +void (*vm_free)(struct kvm *kvm);/* Create, but do not attach this VCPU */ int (*vcpu_precreate)(struct kvm *kvm);
arch/x86/kvm/Kconfig +2 -0
@@ -94,6 +94,8 @@ config KVM_SW_PROTECTED_VM config KVM_INTEL tristate "KVM for Intel (and compatible) processors support" depends on KVM && IA32_FEAT_CTL + select KVM_GENERIC_PRIVATE_MEM if INTEL_TDX_HOST + select KVM_GENERIC_MEMORY_ATTRIBUTES if INTEL_TDX_HOST help Provides support for KVM on processors equipped with Intel's VT extensions, a.k.a. Virtual Machine Extensions (VMX).
arch/x86/kvm/vmx/main.c +26 -2
@@ -41,6 +41,28 @@ static __init int vt_hardware_setup(void)return 0 ; } +static int vt_vm_init (struct kvm *kvm) +{ +if (is_td (kvm)) +return tdx_vm_init (kvm); + +return vmx_vm_init (kvm); +} + +static void vt_vm_destroy (struct kvm *kvm) +{ +if (is_td (kvm)) +return tdx_mmu_release_hkid (kvm); + +vmx_vm_destroy (kvm); +} + +static void vt_vm_free (struct kvm *kvm) +{ +if (is_td (kvm)) +tdx_vm_free (kvm); +} +static int vt_mem_enc_ioctl (struct kvm *kvm,void __user *argp) {if (!is_td (kvm))
@@ -72,8 +94,10 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .has_emulated_msr = vmx_has_emulated_msr, .vm_size = sizeof(struct kvm_vmx), - .vm_init = vmx_vm_init, - .vm_destroy = vmx_vm_destroy, + + .vm_init = vt_vm_init, + .vm_destroy = vt_vm_destroy, + .vm_free = vt_vm_free, .vcpu_precreate = vmx_vcpu_precreate, .vcpu_create = vmx_vcpu_create,
arch/x86/kvm/vmx/tdx.c +450 -0
468 lines not on this page · raw message
arch/x86/kvm/vmx/tdx.h +3 -1
@@ -13,7 +13,9 @@ extern bool enable_tdx;struct kvm_tdx {struct kvm kvm; -/* TDX specific members follow. */ +int hkid; + +struct tdx_td td; };struct vcpu_tdx {
arch/x86/kvm/vmx/x86_ops.h +6 -0
@@ -122,8 +122,14 @@ void vmx_cancel_hv_timer(struct kvm_vcpu *vcpu);void vmx_setup_mce (struct kvm_vcpu *vcpu);#ifdef CONFIG_INTEL_TDX_HOST +int tdx_vm_init (struct kvm *kvm); +void tdx_mmu_release_hkid (struct kvm *kvm); +void tdx_vm_free (struct kvm *kvm);int tdx_vm_ioctl (struct kvm *kvm,void __user *argp);#else +static inline int tdx_vm_init (struct kvm *kvm) {return -EOPNOTSUPP ; } +static inline void tdx_mmu_release_hkid (struct kvm *kvm) {} +static inline void tdx_vm_free (struct kvm *kvm) {}static inline int tdx_vm_ioctl (struct kvm *kvm,void __user *argp) {return -EOPNOTSUPP ; }#endif
arch/x86/kvm/x86.c +1 -0
@@ -12884,6 +12884,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm)kvm_page_track_cleanup (kvm);kvm_xen_destroy_vm (kvm);kvm_hv_destroy_vm (kvm); +static_call_cond (kvm_x86_vm_free)(kvm); }static void memslot_rmap_free (struct kvm_memory_slot *slot)
Signature · 1 line
2.43.5
Sean Christopherson
maintainerRe: [PATCH 20/30] KVM: TDX: create/destroy VM structure
TL;DR: Please don't merge this patch to kvm/next or kvm/queue.
Quoted 13 lines · Paolo Bonzini
arch/x86/kvm/vmx/main.c +4
-2@@ -72,8 +94,10 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .has_emulated_msr = vmx_has_emulated_msr, .vm_size = sizeof(struct kvm_vmx), - .vm_init = vmx_vm_init, - .vm_destroy = vmx_vm_destroy, + + .vm_init = vt_vm_init, + .vm_destroy = vt_vm_destroy, + .vm_free = vt_vm_free, .vcpu_precreate = vmx_vcpu_precreate, .vcpu_create = vmx_vcpu_create,
...
arch/x86/kvm/x86.c void kvm_arch_destroy_vm(struct kvm *kvm) · line 12888
Quoted 10 lines
arch/x86/kvm/x86.c +1
-0@@ -12884,6 +12884,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm)kvm_page_track_cleanup (kvm);kvm_xen_destroy_vm (kvm);kvm_hv_destroy_vm (kvm); +static_call_cond (kvm_x86_vm_free)(kvm); }
Sorry to throw a wrench in things, but I have a fix that I want to send for 6.14[1], i.e. before this code, and to land that fix I need/want to destroy vCPUs before calling kvm_x86_ops.vm_destroy(). *sigh*
The underlying issue is that both nVMX and nSVM suck and access all manner of VM-wide state when destroying a vCPU that is currently in nested guest mode, and I want to fix the most pressing issue of destroying vCPUs at a random time once and for all. nVMX and nSVM also need to be cleaned up to not access so much darn state, but I'm worried that "fixing" the nested cases will only whack the biggest mole.
Commit 6fcee03df6a1 ("KVM: x86: avoid loading a vCPU after .vm_destroy was called") papered over an AVIC case, but there are issues, e.g. with the MSR filters[2], and the NULL pointer deref that's blocking the aforementioned fix is a nVMX access to the PIC.
I haven't fully tested destroying vCPUs before calling vm_destroy(), but I can't see anything in vmx_vm_destroy() or svm_vm_destroy() that expects to run while vCPUs are still alive. If anything, it's opposite, e.g. freeing VMX's IPIv PID table before vCPUs are destroyed is blatantly unsafe.
The good news is, I think it'll lead to a better approach (and naming). KVM already frees MMU state before vCPU state, because while MMUs are largely VM-scoped, all of the common MMU state needs to be freed before any one vCPU is freed.
And so my plan is to carved out a kvm_destroy_mmus() helper, which can then call the TDX hook to release/reclaim the HKID, which I assume needs to be done after KVM's general MMU destruction, but before vCPUs are freed.
I'll make sure to Cc y'all on the series (typing and testing furiously to try and get it out asap). But to try and avoid posting code that's not usable for TDX, will this work?
static void kvm_destroy_mmus(struct kvm *kvm)
{
struct kvm_vcpu *vcpu;
unsigned long i;
if (current->mm == kvm->mm) {
/*
* Free memory regions allocated on behalf of userspace,
* unless the memory map has changed due to process exit
* or fd copying.
*/
mutex_lock(&kvm->slots_lock);
__x86_set_memory_region(kvm, APIC_ACCESS_PAGE_PRIVATE_MEMSLOT,
0, 0);
__x86_set_memory_region(kvm, IDENTITY_PAGETABLE_PRIVATE_MEMSLOT,
0, 0);
__x86_set_memory_region(kvm, TSS_PRIVATE_MEMSLOT, 0, 0);
mutex_unlock(&kvm->slots_lock);
}
kvm_for_each_vcpu(i, vcpu, kvm) {
kvm_clear_async_pf_completion_queue(vcpu);
kvm_unload_vcpu_mmu(vcpu);
}
kvm_x86_call(mmu_destroy)(kvm);
}void kvm_arch_pre_destroy_vm(struct kvm *kvm)
{
kvm_mmu_pre_destroy_vm(kvm);
}void kvm_arch_destroy_vm(struct kvm *kvm)
{
/*
* WARNING! MMUs must be destroyed before vCPUs, and vCPUs must be
* destroyed before any VM state. Most MMU state is VM-wide, but is
* tracked per-vCPU, and so must be unloaded/freed in its entirety
* before any one vCPU is destroyed. For all other VM state, vCPUs
* expect to be able to access VM state until the vCPU is freed.
*/
kvm_destroy_mmus(kvm);
kvm_destroy_vcpus(kvm);
kvm_x86_call(vm_destroy)(kvm);
...
}[1] https://lore.kernel.org/all/[email protected]
[2] https://lore.kernel.org/all/[email protected]
Sean Christopherson
maintainerRe: [PATCH 20/30] KVM: TDX: create/destroy VM structure
Quoted 39 lines · Sean Christopherson
TL;DR: Please don't merge this patch to kvm/next or kvm/queue.
Quoted 13 lines · Paolo Bonzini
arch/x86/kvm/vmx/main.c +4
-2@@ -72,8 +94,10 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .has_emulated_msr = vmx_has_emulated_msr, .vm_size = sizeof(struct kvm_vmx), - .vm_init = vmx_vm_init, - .vm_destroy = vmx_vm_destroy, + + .vm_init = vt_vm_init, + .vm_destroy = vt_vm_destroy, + .vm_free = vt_vm_free, .vcpu_precreate = vmx_vcpu_precreate, .vcpu_create = vmx_vcpu_create,...
arch/x86/kvm/x86.c void kvm_arch_destroy_vm(struct kvm *kvm) · line 12888
Quoted 10 lines
arch/x86/kvm/x86.c +1
-0@@ -12884,6 +12884,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm)kvm_page_track_cleanup (kvm);kvm_xen_destroy_vm (kvm);kvm_hv_destroy_vm (kvm); +static_call_cond (kvm_x86_vm_free)(kvm); }Sorry to throw a wrench in things, but I have a fix that I want to send for 6.14[1], i.e. before this code, and to land that fix I need/want to destroy vCPUs before calling
kvm_x86_ops.vm_destroy(). *sigh*The underlying issue is that both nVMX and nSVM suck and access all manner of VM-wide state when destroying a vCPU that is currently in nested guest mode, and I want to fix the most pressing issue of destroying vCPUs at a random time once and for all. nVMX and nSVM also need to be cleaned up to not access so much darn state, but I'm worried that "fixing" the nested cases will only whack the biggest mole.
...
Quoted 3 lines
And so my plan is to carved out a
kvm_destroy_mmus()helper, which can then call the TDX hook to release/reclaim the HKID, which I assume needs to be done after KVM's general MMU destruction, but before vCPUs are freed.
...
Quoted 7 lines
void
kvm_arch_destroy_vm(struct kvm *kvm)
{
/*
* WARNING! MMUs must be destroyed before vCPUs, and vCPUs must be
* destroyed before any VM state. Most MMU state is VM-wide, but is
* tracked per-vCPU, and so must be unloaded/freed in its entirety
* before any one vCPU is destroyed.
Argh, after digging more, this isn't actually true. The separate "unload MMUs" code is leftover from when KVM rather stupidly tried to free all MMU pages when freeing a vCPU.
Commit 7b53aa565084 ("KVM: Fix vcpu freeing for guest smp") "fixed" things by unloading MMUs before destroying vCPUs, but the underlying problem was trying to free _all_ MMU pages when destroying a single vCPU. That eventually got fixed for good (haven't checked when), but the separate MMU unloading never got cleaned up.
So, scratch the mmu_destroy() idea. But I still want/need to move vCPU destruction before vm_destroy.
Now that kvm_arch_pre_destroy_vm() is a thing, one idea would be to add kvm_x86_ops.pre_destroy_vm(), which would pair decently well with the existing call to kvm_mmu_pre_destroy_vm().
Edgecombe, Rick P
maintainerRe: [PATCH 20/30] KVM: TDX: create/destroy VM structure
Quoted 10 lines · Sean Christopherson
Argh, after digging more, this isn't actually true. The separate "unload MMUs" code is leftover from when KVM rather stupidly tried to free all MMU pages when freeing a vCPU.
Commit
7b53aa565084("KVM: Fix vcpu freeing for guest smp") "fixed" things by unloading MMUs before destroying vCPUs, but the underlying problem was trying to free _all_ MMU pages when destroying a single vCPU. That eventually got fixed for good (haven't checked when), but the separate MMU unloading never got cleaned up.
Quoted 6 lines
So, scratch the
mmu_destroy()idea. But I still want/need to move vCPU destruction beforevm_destroy.Now that
kvm_arch_pre_destroy_vm()is a thing, one idea would be to addkvm_x86_ops.pre_destroy_vm(), which would pair decently well with the existing call tokvm_mmu_pre_destroy_vm().
So:
kvm_x86_call(vm_destroy)(kvm); -> tdx_mmu_release_hkid() kvm_destroy_vcpus(kvm); -> tdx_vcpu_free() -> reclaim static_call_cond(kvm_x86_vm_free)(kvm); -> reclaim
To:
(pre_destroy_vm)() -> tdx_mmu_release_hkid() kvm_destroy_vcpus(kvm); -> reclaim kvm_x86_call(vm_destroy)(kvm); -> nothing static_call_cond(kvm_x86_vm_free)(kvm); -> reclaim
I'm not seeing a problem. We can follow up with a real check once you post the patches. I'm not 100% confident on the shape of the proposal. But in general if we can add more callbacks it seems likely that we can reproduce the current order. At this stage it seems safer to do that then anything more clever
Sean Christopherson
maintainerRe: [PATCH 20/30] KVM: TDX: create/destroy VM structure
Quoted 23 lines · Rick P Edgecombe
Quoted 10 lines · Sean Christopherson
Argh, after digging more, this isn't actually true. The separate "unload MMUs" code is leftover from when KVM rather stupidly tried to free all MMU pages when freeing a vCPU.
Commit
7b53aa565084("KVM: Fix vcpu freeing for guest smp") "fixed" things by unloading MMUs before destroying vCPUs, but the underlying problem was trying to free _all_ MMU pages when destroying a single vCPU. That eventually got fixed for good (haven't checked when), but the separate MMU unloading never got cleaned up.Quoted 6 lines
So, scratch the
mmu_destroy()idea. But I still want/need to move vCPU destruction beforevm_destroy.Now that
kvm_arch_pre_destroy_vm()is a thing, one idea would be to addkvm_x86_ops.pre_destroy_vm(), which would pair decently well with the existing call tokvm_mmu_pre_destroy_vm().So:
kvm_x86_call(vm_destroy)(kvm); ->tdx_mmu_release_hkid()kvm_destroy_vcpus(kvm); ->tdx_vcpu_free()-> reclaim static_call_cond(kvm_x86_vm_free)(kvm); -> reclaim
Quoted 5 lines
To:
(pre_destroy_vm)() ->tdx_mmu_release_hkid()kvm_destroy_vcpus(kvm); -> reclaim kvm_x86_call(vm_destroy)(kvm); -> nothing static_call_cond(kvm_x86_vm_free)(kvm); -> reclaim
I was thinking this last one could go away, and TDX could reclaim at vm_destroy? Or is that not possible because it absolutely must come dead last?
Quoted 2 lines
I'm not seeing a problem. We can follow up with a real check once you post the patches.
Ya. That ain't happening today. Got demolished but KVM-Unit-Tests. :-/
Quoted 3 lines
I'm not 100% confident on the shape of the proposal. But in general if we can add more callbacks it seems likely that we can reproduce the current order. At this stage it seems safer to do that then anything more clever
Re: [PATCH 20/30] KVM: TDX: create/destroy VM structure
Quoted 24 lines · Sean Christopherson
Quoted 23 lines · Rick P Edgecombe
Quoted 10 lines · Sean Christopherson
Argh, after digging more, this isn't actually true. The separate "unload MMUs" code is leftover from when KVM rather stupidly tried to free all MMU pages when freeing a vCPU.
Commit
7b53aa565084("KVM: Fix vcpu freeing for guest smp") "fixed" things by unloading MMUs before destroying vCPUs, but the underlying problem was trying to free _all_ MMU pages when destroying a single vCPU. That eventually got fixed for good (haven't checked when), but the separate MMU unloading never got cleaned up.Quoted 6 lines
So, scratch the
mmu_destroy()idea. But I still want/need to move vCPU destruction beforevm_destroy.Now that
kvm_arch_pre_destroy_vm()is a thing, one idea would be to addkvm_x86_ops.pre_destroy_vm(), which would pair decently well with the existing call tokvm_mmu_pre_destroy_vm().So:
kvm_x86_call(vm_destroy)(kvm); ->tdx_mmu_release_hkid()kvm_destroy_vcpus(kvm); ->tdx_vcpu_free()-> reclaim static_call_cond(kvm_x86_vm_free)(kvm); -> reclaim
Quoted 8 lines
Quoted 5 lines
To:
(pre_destroy_vm)() ->tdx_mmu_release_hkid()kvm_destroy_vcpus(kvm); -> reclaim kvm_x86_call(vm_destroy)(kvm); -> nothing static_call_cond(kvm_x86_vm_free)(kvm); -> reclaimI was thinking this last one could go away, and TDX could reclaim at
vm_destroy? Or is that not possible because it absolutely must come dead last?
Hmm, below change works on my end.
arch/x86/include/asm/kvm-x86-ops.h +1 -1
@@ -21,7 +21,7 @@ KVM_X86_OP(has_emulated_msr) KVM_X86_OP(vcpu_after_set_cpuid) KVM_X86_OP(vm_init) KVM_X86_OP_OPTIONAL(vm_destroy) -KVM_X86_OP_OPTIONAL(vm_free) +KVM_X86_OP_OPTIONAL(vm_pre_destroy) KVM_X86_OP_OPTIONAL_RET0(vcpu_precreate) KVM_X86_OP(vcpu_create) KVM_X86_OP(vcpu_free)
arch/x86/include/asm/kvm_host.h +1 -1
@@ -1677,7 +1677,7 @@ struct kvm_x86_ops {unsigned int vm_size;int (*vm_init)(struct kvm *kvm);void (*vm_destroy)(struct kvm *kvm); -void (*vm_free)(struct kvm *kvm); +void (*vm_pre_destroy)(struct kvm *kvm);/* Create, but do not attach this VCPU */ int (*vcpu_precreate)(struct kvm *kvm);
arch/x86/kvm/vmx/main.c +6 -5
@@ -76,18 +76,19 @@ static int vt_vm_init(struct kvm *kvm)return vmx_vm_init (kvm); } -static void vt_vm_destroy (struct kvm *kvm) +static void vt_vm_pre_destroy (struct kvm *kvm) {if (is_td (kvm))return tdx_mmu_release_hkid (kvm); -vmx_vm_destroy (kvm); } -static void vt_vm_free (struct kvm *kvm) +static void vt_vm_destroy (struct kvm *kvm) {if (is_td (kvm)) -tdx_vm_free (kvm); +return tdx_vm_free (kvm); + +vmx_vm_destroy (kvm); }static int vt_vcpu_precreate (struct kvm *kvm)
@@ -914,7 +915,7 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .vm_init = vt_vm_init, .vm_destroy = vt_vm_destroy, - .vm_free = vt_vm_free, + .vm_pre_destroy = vt_vm_pre_destroy, .vcpu_precreate = vt_vcpu_precreate, .vcpu_create = vt_vcpu_create,
arch/x86/kvm/x86.c +2 -2
@@ -12889,6 +12889,7 @@ EXPORT_SYMBOL_GPL(__x86_set_memory_region);void kvm_arch_pre_destroy_vm (struct kvm *kvm) {kvm_mmu_pre_destroy_vm (kvm); +static_call_cond (kvm_x86_vm_pre_destroy)(kvm); }void kvm_arch_destroy_vm (struct kvm *kvm)
@@ -12908,7 +12909,6 @@ void kvm_arch_destroy_vm(struct kvm *kvm)mutex_unlock (&kvm->slots_lock); }kvm_unload_vcpu_mmus (kvm); -kvm_x86_call (vm_destroy)(kvm);kvm_free_msr_filter (srcu_dereference_check (kvm->arch.msr_filter, &kvm->srcu,1 ));kvm_pic_destroy (kvm);kvm_ioapic_destroy (kvm);
@@ -12919,7 +12919,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm)kvm_page_track_cleanup (kvm);kvm_xen_destroy_vm (kvm);kvm_hv_destroy_vm (kvm); -static_call_cond (kvm_x86_vm_free)(kvm); +kvm_x86_call (vm_destroy)(kvm); }static void memslot_rmap_free (struct kvm_memory_slot *slot)
Re: [PATCH 20/30] KVM: TDX: create/destroy VM structure
In reply to Sean ChristophersonQuoted 45 lines · Sean Christopherson
TL;DR: Please don't merge this patch to kvm/next or kvm/queue.
Quoted 13 lines · Paolo Bonzini
arch/x86/kvm/vmx/main.c +4
-2@@ -72,8 +94,10 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .has_emulated_msr = vmx_has_emulated_msr, .vm_size = sizeof(struct kvm_vmx), - .vm_init = vmx_vm_init, - .vm_destroy = vmx_vm_destroy, + + .vm_init = vt_vm_init, + .vm_destroy = vt_vm_destroy, + .vm_free = vt_vm_free, .vcpu_precreate = vmx_vcpu_precreate, .vcpu_create = vmx_vcpu_create,...
arch/x86/kvm/x86.c void kvm_arch_destroy_vm(struct kvm *kvm) · line 12888
Quoted 10 lines
arch/x86/kvm/x86.c +1
-0@@ -12884,6 +12884,7 @@ void kvm_arch_destroy_vm(struct kvm *kvm)kvm_page_track_cleanup (kvm);kvm_xen_destroy_vm (kvm);kvm_hv_destroy_vm (kvm); +static_call_cond (kvm_x86_vm_free)(kvm); }Sorry to throw a wrench in things, but I have a fix that I want to send for 6.14[1], i.e. before this code, and to land that fix I need/want to destroy vCPUs before calling
kvm_x86_ops.vm_destroy(). *sigh*The underlying issue is that both nVMX and nSVM suck and access all manner of VM-wide state when destroying a vCPU that is currently in nested guest mode, and I want to fix the most pressing issue of destroying vCPUs at a random time once and for all. nVMX and nSVM also need to be cleaned up to not access so much darn state, but I'm worried that "fixing" the nested cases will only whack the biggest mole.
Commit
6fcee03df6a1("KVM: x86: avoid loading a vCPU after .vm_destroy was called") papered over an AVIC case, but there are issues, e.g. with the MSR filters[2], and the NULL pointer deref that's blocking the aforementioned fix is a nVMX access to the PIC.
Quoted 4 lines
I haven't fully tested destroying vCPUs before calling
vm_destroy(), but I can't see anything invmx_vm_destroy()orsvm_vm_destroy()that expects to run while vCPUs are still alive. If anything, it's opposite, e.g. freeing VMX's IPIv PID table before vCPUs are destroyed is blatantly unsafe.
Is it possible to simply move the code like freeing PID table from vmx_vm_destroy() to static_call_cond(kvm_x86_vm_free)(kvm) ?
Quoted 31 lines
The good news is, I think it'll lead to a better approach (and naming). KVM already frees MMU state before vCPU state, because while MMUs are largely VM-scoped, all of the common MMU state needs to be freed before any one vCPU is freed.
And so my plan is to carved out a
kvm_destroy_mmus()helper, which can then call the TDX hook to release/reclaim the HKID, which I assume needs to be done after KVM's general MMU destruction, but before vCPUs are freed.I'll make sure to Cc y'all on the series (typing and testing furiously to try and get it out asap). But to try and avoid posting code that's not usable for TDX, will this work?
static void
kvm_destroy_mmus(struct kvm *kvm){ struct kvm_vcpu *vcpu; unsigned long i; if (current->mm == kvm->mm) { /* * Free memory regions allocated on behalf of userspace, * unless the memory map has changed due to process exit * or fd copying. */ mutex_lock(&kvm->slots_lock); __x86_set_memory_region(kvm, APIC_ACCESS_PAGE_PRIVATE_MEMSLOT, 0, 0); __x86_set_memory_region(kvm, IDENTITY_PAGETABLE_PRIVATE_MEMSLOT, 0, 0); __x86_set_memory_region(kvm, TSS_PRIVATE_MEMSLOT, 0, 0); mutex_unlock(&kvm->slots_lock);
Quoted 8 lines
}
kvm_for_each_vcpu(i, vcpu, kvm) {
kvm_clear_async_pf_completion_queue(vcpu);
kvm_unload_vcpu_mmu(vcpu);
}
kvm_x86_call(mmu_destroy)(kvm);I suppose this will hook tdx_mmu_release_hkid() ?
Quoted 25 lines
}
void
kvm_arch_pre_destroy_vm(struct kvm *kvm){ kvm_mmu_pre_destroy_vm(kvm); }void
kvm_arch_destroy_vm(struct kvm *kvm){ /* * WARNING! MMUs must be destroyed before vCPUs, and vCPUs must be * destroyed before any VM state. Most MMU state is VM-wide, but is * tracked per-vCPU, and so must be unloaded/freed in its entirety * before any one vCPU is destroyed. For all other VM state, vCPUs * expect to be able to access VM state until the vCPU is freed. */ kvm_destroy_mmus(kvm); kvm_destroy_vcpus(kvm); kvm_x86_call(vm_destroy)(kvm); ... }[1] https://lore.kernel.org/all/[email protected]
[2] https://lore.kernel.org/all/[email protected]
Sean Christopherson
maintainerRe: [PATCH 20/30] KVM: TDX: create/destroy VM structure
Quoted 2 lines · Yan Zhao
Quoted 1 line · Sean Christopherson
TL;DR: Please don't merge this patch to kvm/next or kvm/queue.
...
Quoted 11 lines
Quoted 9 lines
Commit
6fcee03df6a1("KVM: x86: avoid loading a vCPU after .vm_destroy was called") papered over an AVIC case, but there are issues, e.g. with the MSR filters[2], and the NULL pointer deref that's blocking the aforementioned fix is a nVMX access to the PIC.I haven't fully tested destroying vCPUs before calling
vm_destroy(), but I can't see anything invmx_vm_destroy()orsvm_vm_destroy()that expects to run while vCPUs are still alive. If anything, it's opposite, e.g. freeing VMX's IPIv PID table before vCPUs are destroyed is blatantly unsafe.Is it possible to simply move the code like freeing PID table from
vmx_vm_destroy()to static_call_cond(kvm_x86_vm_free)(kvm) ?
That would fix the potential PID table problem, but not the other issues with freeing VM state before destroying vCPUs.
Quoted 32 lines
Quoted 32 lines
The good news is, I think it'll lead to a better approach (and naming). KVM already frees MMU state before vCPU state, because while MMUs are largely VM-scoped, all of the common MMU state needs to be freed before any one vCPU is freed.
And so my plan is to carved out a
kvm_destroy_mmus()helper, which can then call the TDX hook to release/reclaim the HKID, which I assume needs to be done after KVM's general MMU destruction, but before vCPUs are freed.I'll make sure to Cc y'all on the series (typing and testing furiously to try and get it out asap). But to try and avoid posting code that's not usable for TDX, will this work?
static void
kvm_destroy_mmus(struct kvm *kvm){ struct kvm_vcpu *vcpu; unsigned long i; if (current->mm == kvm->mm) { /* * Free memory regions allocated on behalf of userspace, * unless the memory map has changed due to process exit * or fd copying. */ mutex_lock(&kvm->slots_lock); __x86_set_memory_region(kvm, APIC_ACCESS_PAGE_PRIVATE_MEMSLOT, 0, 0); __x86_set_memory_region(kvm, IDENTITY_PAGETABLE_PRIVATE_MEMSLOT, 0, 0); __x86_set_memory_region(kvm, TSS_PRIVATE_MEMSLOT, 0, 0); mutex_unlock(&kvm->slots_lock); }
Quoted 7 lines
Quoted 6 lines
kvm_for_each_vcpu(i, vcpu, kvm) { kvm_clear_async_pf_completion_queue(vcpu); kvm_unload_vcpu_mmu(vcpu); } kvm_x86_call(mmu_destroy)(kvm);I suppose this will hook
tdx_mmu_release_hkid()?
Please see my follow-up idea[1] to hook into kvm_arch_pre_destroy_vm(). Turns out there isn't a hard requirement to unload MMUs prior to destroying vCPUs (at least, not AFAICT).
Re: [PATCH 20/30] KVM: TDX: create/destroy VM structure
In reply to Paolo Bonziniarch/x86/kvm/vmx/tdx.c static int init_kvm_tdx_caps(const struct tdx_sys_info_td_conf *td_conf, · line 168
Quoted 7 lines
arch/x86/kvm/vmx/tdx.c +7
-0+/* TDH.PHYMEM.PAGE.RECLAIM is allowed only when destroying the TD. */ +static int __tdx_reclaim_page (struct page *page) +{ +u64 err, rcx, rdx, r8; +int i; + +for (i =TDX_SEAMCALL_RETRIES ; i >0 ; i--) {
Yes, the retries can be dropped according to the previous analysis at
https://lore.kernel.org/kvm/ZyMAD0tSZiadZ%[email protected].
Currently, all TD pages are 4K and even freed before the hkid is released, before the control of tdh_phymem_page_reclaim().
Non-TD control pages are also 4K and are guaranteed to be reclaimed before TDR pages are reclaimed.
So, for basic TDX, contentions in tdh_phymem_page_reclaim() are not expected.
Quoted 26 lines
arch/x86/kvm/vmx/tdx.c +26
-0+ err =tdh_phymem_page_reclaim (page, &rcx, &rdx, &r8); + +/* +* TDH.PHYMEM.PAGE.RECLAIM is allowed only when TD is shutdown. +* state. i.e. destructing TD. +* TDH.PHYMEM.PAGE.RECLAIM requires TDR and target page. +* Because we're destructing TD, it's rare to contend with TDR. +*/ +switch (err) { +case TDX_OPERAND_BUSY |TDX_OPERAND_ID_RCX : +case TDX_OPERAND_BUSY |TDX_OPERAND_ID_TDR : +cond_resched (); +continue ; +default : + goto out; + } + } + +out: +if (WARN_ON_ONCE (err)) { +pr_tdx_error_3 (TDH_PHYMEM_PAGE_RECLAIM , err, rcx, rdx, r8); +return -EIO ; + } +return 0 ; +} +
...
Quoted 8 lines
arch/x86/kvm/vmx/tdx.c +8
-0+static void smp_func_do_phymem_cache_wb (void *unused) +{ +u64 err =0 ; +bool resume; +int i; + +/* +* TDH.PHYMEM.CACHE.WB flushes caches associated with any TDX private
arch/x86/kvm/vmx/tdx.c static int init_kvm_tdx_caps(const struct tdx_sys_info_td_conf *td_conf, · line 240
Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +10
-0+* KeyID on the package or core. The TDX module may not finish the +* cache flush but return TDX_INTERRUPTED_RESUMEABLE instead. The +* kernel should retry it until it returns success w/o rescheduling. +*/ +for (i =TDX_SEAMCALL_RETRIES ; i >0 ; i--) { + resume = !!err; + err =tdh_phymem_cache_wb (resume); +switch (err) { +case TDX_INTERRUPTED_RESUMABLE : +continue ;
These retries may not be removable as tdh_phymem_cache_wb() is an interruptible and restartable function. If a pending interrupt is detected during operation, tdh_phymem_cache_wb() returns with a TDX_INTERRUPED_RESUMABLE status in RAX. KVM needs complete the cache write-back operation by resuming tdh_phymem_cache_wb().
Quoted 49 lines
arch/x86/kvm/vmx/tdx.c +49
-0+case TDX_NO_HKID_READY_TO_WBCACHE : + err =TDX_SUCCESS ;/* Already done by other thread */ + fallthrough; +default : + goto out; + } + } + +out: +if (WARN_ON_ONCE (err)) +pr_tdx_error (TDH_PHYMEM_CACHE_WB , err); +} + +void tdx_mmu_release_hkid (struct kvm *kvm) +{ +bool packages_allocated, targets_allocated; +struct kvm_tdx *kvm_tdx =to_kvm_tdx (kvm); +cpumask_var_t packages, targets; +u64 err; +int i; + +if (!is_hkid_assigned (kvm_tdx)) +return ; + +/* KeyID has been allocated but guest is not yet configured */ +if (!kvm_tdx->td.tdr_page) { +tdx_hkid_free (kvm_tdx); +return ; + } + + packages_allocated =zalloc_cpumask_var (&packages,GFP_KERNEL ); + targets_allocated =zalloc_cpumask_var (&targets,GFP_KERNEL ); +cpus_read_lock (); + +/* +* TDH.PHYMEM.CACHE.WB tries to acquire the TDX module global lock +* and can fail with TDX_OPERAND_BUSY when it fails to get the lock. +* Multiple TDX guests can be destroyed simultaneously. Take the +* mutex to prevent it from getting error. +*/ +mutex_lock (&tdx_lock); + +/* +* Releasing HKID is in vm_destroy(). +* After the above flushing vps, there should be no more vCPU +* associations, as all vCPU fds have been released at this stage. +*/ +for_each_online_cpu (i) { + if (packages_allocated &&
arch/x86/kvm/vmx/tdx.c static int init_kvm_tdx_caps(const struct tdx_sys_info_td_conf *td_conf, · line 299
Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +10
-0+cpumask_test_and_set_cpu (topology_physical_package_id (i), + packages)) + continue; +if (targets_allocated) +cpumask_set_cpu (i, targets); + } +if (targets_allocated) +on_each_cpu_mask (targets, smp_func_do_phymem_cache_wb,NULL , true); +else +on_each_cpu (smp_func_do_phymem_cache_wb,NULL , true);
If either packages_allocated or targets_allocated is false, tdh_phymem_cache_wb() will be executed on each core. Then TDX_OPERAND_BUSY is possible since tdh_phymem_cache_wb() needs to acquire a per package wbt_entries.
So, should we add the retries for this rare case or just simply leave it to the WARN_ON()?
Quoted 19 lines
arch/x86/kvm/vmx/tdx.c +19
-0+/* +* In the case of error in smp_func_do_phymem_cache_wb(), the following +* tdh_mng_key_freeid() will fail. +*/ + err =tdh_mng_key_freeid (&kvm_tdx->td); +if (KVM_BUG_ON (err, kvm)) { +pr_tdx_error (TDH_MNG_KEY_FREEID , err); +pr_err ("tdh_mng_key_freeid() failed. HKID %d is leaked.\n" , + kvm_tdx->hkid); + }else { +tdx_hkid_free (kvm_tdx); + } + +mutex_unlock (&tdx_lock); +cpus_read_unlock (); +free_cpumask_var (targets); +free_cpumask_var (packages); +} +
Re: [PATCH 20/30] KVM: TDX: create/destroy VM structure
In reply to Paolo BonziniOn 2/21/2025 1:05 AM, Paolo Bonzini wrote:
...
arch/x86/kvm/vmx/tdx.c static int init_kvm_tdx_caps(const struct tdx_sys_info_td_conf *td_conf, · line 391
Quoted 3 lines
arch/x86/kvm/vmx/tdx.c +3
-0+int tdx_vm_init (struct kvm *kvm) +{ + kvm->arch.has_private_mem = true;
If it's going to have a next version, I think we can squash below patch into current:
Quoted 4 lines
arch/x86/kvm/vmx/tdx.c +4
-0+/* Place holder for TDX specific logic. */ +return __tdx_td_init (kvm); +} +
Paolo Bonzini
maintainerPATCH v3 21/30 KVM: TDX: Support per-VM KVM_CAP_MAX_VCPUS extension check
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Change to report the KVM_CAP_MAX_VCPUS extension from globally to per-VM to allow userspace to be able to query maximum vCPUs for TDX guest via checking the KVM_CAP_MAX_VCPU extension on per-VM basis.
Today KVM x86 reports KVM_MAX_VCPUS as guest's maximum vCPUs for all guests globally, and userspace, i.e. Qemu, queries the KVM_MAX_VCPUS extension globally but not on per-VM basis.
TDX has its own limit of maximum vCPUs it can support for all TDX guests in addition to KVM_MAX_VCPUS. TDX module reports this limit via the MAX_VCPU_PER_TD global metadata. Different modules may report different values. In practice, the reported value reflects the maximum logical CPUs that ALL the platforms that the module supports can possibly have.
Note some old modules may also not support this metadata, in which case the limit is U16_MAX.
The current way to always report KVM_MAX_VCPUS in the KVM_CAP_MAX_VCPUS extension is not enough for TDX. To accommodate TDX, change to report the KVM_CAP_MAX_VCPUS extension on per-VM basis.
Specifically, override kvm->max_vcpus in tdx_vm_init() for TDX guest, and report kvm->max_vcpus in the KVM_CAP_MAX_VCPUS extension check.
Change to report "the number of logical CPUs the platform has" as the maximum vCPUs for TDX guest. Simply forwarding the MAX_VCPU_PER_TD reported by the TDX module would result in an unpredictable ABI because the reported value to userspace would be depending on whims of TDX modules.
This works in practice because of the MAX_VCPU_PER_TD reported by the TDX module will never be smaller than the one reported to userspace. But to make sure KVM never reports an unsupported value, sanity check the MAX_VCPU_PER_TD reported by TDX module is not smaller than the number of logical CPUs the platform has, otherwise refuse to use TDX.
Note, when creating a TDX guest, TDX actually requires the "maximum vCPUs for _this_ TDX guest" as an input to initialize the TDX guest. But TDX guest's maximum vCPUs is not part of TDREPORT thus not part of attestation, thus there's no need to allow userspace to explicitly _configure_ the maximum vCPUs on per-VM basis. KVM will simply use kvm->max_vcpus as input when initializing the TDX guest.
--- arch/x86/kvm/vmx/main.c | 1 + arch/x86/kvm/vmx/tdx.c | 51 +++++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 2 ++ 3 files changed, 54 insertions(+)
arch/x86/kvm/vmx/main.c +1 -0
@@ -7,6 +7,7 @@#include "pmu.h" #include "posted_intr.h" #include "tdx.h" +#include "tdx_arch.h" static __init int vt_hardware_setup (void ) {
arch/x86/kvm/vmx/tdx.c +51 -0
69 lines not on this page · raw message
arch/x86/kvm/x86.c +2 -0
@@ -4708,6 +4708,8 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)break ;case KVM_CAP_MAX_VCPUS : r =KVM_MAX_VCPUS ; +if (kvm) + r = kvm->max_vcpus;break ;case KVM_CAP_MAX_VCPU_ID : r =KVM_MAX_VCPU_IDS ;
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 22/30 KVM: x86: expose cpuid_entry2_find for TDX
In reply to Paolo Bonzini--- arch/x86/kvm/cpuid.c | 19 +++++++++++-------- arch/x86/kvm/cpuid.h | 2 ++ 2 files changed, 13 insertions(+), 8 deletions(-)
arch/x86/kvm/cpuid.c +11 -8
@@ -86,13 +86,13 @@ u32 xstate_required_size(u64 xstate_bv, bool compacted)* Magic value used by KVM when querying userspace-provided CPUID entries and * doesn't care about the CPIUD index because the index of the function in * question is not significant. Note, this magic value must have at least one -* bit set in bits[63:32] and must be consumed as a u64 by cpuid_entry2_find() +* bit set in bits[63:32] and must be consumed as a u64 by kvm_find_cpuid_entry2() * to avoid false positives when processing guest CPUID input. */ #define KVM_CPUID_INDEX_NOT_SIGNIFICANT -1ull -static struct kvm_cpuid_entry2 *cpuid_entry2_find (struct kvm_vcpu *vcpu, -u32 function,u64 index) +struct kvm_cpuid_entry2 *kvm_find_cpuid_entry2 ( +struct kvm_cpuid_entry2 *entries,int nent,u32 function,u64 index) {struct kvm_cpuid_entry2 *e;int i;
@@ -109,8 +109,8 @@ static struct kvm_cpuid_entry2 *cpuid_entry2_find(struct kvm_vcpu *vcpu,*/ lockdep_assert_irqs_enabled (); -for (i =0 ; i < vcpu->arch.cpuid_nent; i++) { - e = &vcpu->arch.cpuid_entries[i]; +for (i =0 ; i < nent; i++) { + e = &entries[i];if (e->function != function)continue ;
@@ -141,23 +141,26 @@ static struct kvm_cpuid_entry2 *cpuid_entry2_find(struct kvm_vcpu *vcpu,return NULL ; } +EXPORT_SYMBOL_GPL (kvm_find_cpuid_entry2);struct kvm_cpuid_entry2 *kvm_find_cpuid_entry_index (struct kvm_vcpu *vcpu,u32 function,u32 index) { -return cpuid_entry2_find (vcpu, function, index); +return kvm_find_cpuid_entry2 (vcpu->arch.cpuid_entries, vcpu->arch.cpuid_nent, + function, index); }EXPORT_SYMBOL_GPL (kvm_find_cpuid_entry_index);struct kvm_cpuid_entry2 *kvm_find_cpuid_entry (struct kvm_vcpu *vcpu,u32 function) { -return cpuid_entry2_find (vcpu, function,KVM_CPUID_INDEX_NOT_SIGNIFICANT ); +return kvm_find_cpuid_entry2 (vcpu->arch.cpuid_entries, vcpu->arch.cpuid_nent, + function,KVM_CPUID_INDEX_NOT_SIGNIFICANT ); }EXPORT_SYMBOL_GPL (kvm_find_cpuid_entry);/* -* cpuid_entry2_find() and KVM_CPUID_INDEX_NOT_SIGNIFICANT should never be used +* kvm_find_cpuid_entry2() and KVM_CPUID_INDEX_NOT_SIGNIFICANT should never be used * directly outside of kvm_find_cpuid_entry() and kvm_find_cpuid_entry_index(). */ #undef KVM_CPUID_INDEX_NOT_SIGNIFICANT
arch/x86/kvm/cpuid.h +2 -0
@@ -12,6 +12,8 @@ void kvm_set_cpu_caps(void);void kvm_vcpu_after_set_cpuid (struct kvm_vcpu *vcpu);void kvm_update_cpuid_runtime (struct kvm_vcpu *vcpu); +struct kvm_cpuid_entry2 *kvm_find_cpuid_entry2 (struct kvm_cpuid_entry2 *entries, +int nent,u32 function,u64 index);struct kvm_cpuid_entry2 *kvm_find_cpuid_entry_index (struct kvm_vcpu *vcpu,u32 function,u32 index); struct kvm_cpuid_entry2 *kvm_find_cpuid_entry(struct kvm_vcpu *vcpu,
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 23/30 KVM: TDX: initialize VM with TDX specific parameters
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
After the crypto-protection key has been configured, TDX requires a VM-scope initialization as a step of creating the TDX guest. This "per-VM" TDX initialization does the global configurations/features that the TDX guest can support, such as guest's CPUIDs (emulated by the TDX module), the maximum number of vcpus etc.
This "per-VM" TDX initialization must be done before any "vcpu-scope" TDX initialization. To match this better, require the KVM_TDX_INIT_VM IOCTL() to be done before KVM creates any vcpus.
--- arch/x86/include/uapi/asm/kvm.h | 24 +++ arch/x86/kvm/vmx/tdx.c | 258 ++++++++++++++++++++++++++++++-- arch/x86/kvm/vmx/tdx.h | 25 ++++ 3 files changed, 297 insertions(+), 10 deletions(-)
arch/x86/include/uapi/asm/kvm.h +24 -0
@@ -930,6 +930,7 @@ struct kvm_hyperv_eventfd {/* Trust Domain eXtension sub-ioctl() commands. */ enum kvm_tdx_cmd_id {KVM_TDX_CAPABILITIES =0 , +KVM_TDX_INIT_VM ,KVM_TDX_CMD_NR_MAX , };
@@ -961,4 +962,27 @@ struct kvm_tdx_capabilities { struct kvm_cpuid2 cpuid; }; +struct kvm_tdx_init_vm { +__u64 attributes; +__u64 xfam; +__u64 mrconfigid[6 ];/* sha384 digest */ +__u64 mrowner[6 ];/* sha384 digest */ +__u64 mrownerconfig[6 ];/* sha384 digest */ + +/* The total space for TD_PARAMS before the CPUIDs is 256 bytes */ +__u64 reserved[12 ]; + +/* +* Call KVM_TDX_INIT_VM before vcpu creation, thus before +* KVM_SET_CPUID2. +* This configuration supersedes KVM_SET_CPUID2s for VCPUs because the +* TDX module directly virtualizes those CPUIDs without VMM. The user +* space VMM, e.g. qemu, should make KVM_SET_CPUID2 consistent with +* those values. If it doesn't, KVM may have wrong idea of vCPUIDs of +* the guest, and KVM may wrongly emulate CPUIDs or MSRs that the TDX +* module doesn't virtualize. +*/ +struct kvm_cpuid2 cpuid; +}; +#endif /* _ASM_X86_KVM_H */
arch/x86/kvm/vmx/tdx.c +248 -10
316 lines not on this page · raw message
arch/x86/kvm/vmx/tdx.h +25 -0
@@ -11,9 +11,23 @@ void tdx_cleanup(void);extern bool enable_tdx; +/* TDX module hardware states. These follow the TDX module OP_STATEs. */ +enum kvm_tdx_state { +TD_STATE_UNINITIALIZED =0 , +TD_STATE_INITIALIZED , +TD_STATE_RUNNABLE , +}; +struct kvm_tdx {struct kvm kvm; +int hkid; +enum kvm_tdx_state state; + +u64 attributes; +u64 xfam; + +u64 tsc_offset;struct tdx_td td; };
@@ -33,6 +47,17 @@ static inline bool is_td_vcpu(struct kvm_vcpu *vcpu)return is_td (vcpu->kvm); } +static __always_inline u64 td_tdcs_exec_read64(struct kvm_tdx *kvm_tdx, u32 field) +{ +u64 err, data; + + err =tdh_mng_rd (&kvm_tdx->td,TDCS_EXEC (field), &data); +if (unlikely (err)) { +pr_err ("TDH_MNG_RD[EXEC.0x%x] failed: 0x%llx\n" , field, err); +return 0 ; + } +return data; +}#else static inline int tdx_bringup (void ) {return 0 ; }static inline void tdx_cleanup (void ) {}
Signature · 1 line
2.43.5
Re: [PATCH 23/30] KVM: TDX: initialize VM with TDX specific parameters
On 2/21/2025 1:05 AM, Paolo Bonzini wrote:
...
arch/x86/kvm/vmx/tdx.c int tdx_vm_init(struct kvm *kvm) · line 407
Quoted 6 lines
arch/x86/kvm/vmx/tdx.c +0
-2@@ -403,8 +412,9 @@ int tdx_vm_init(struct kvm *kvm)*/ kvm->max_vcpus =min_t (int, kvm->max_vcpus,num_present_cpus ()); -/* Place holder for TDX specific logic. */ -return __tdx_td_init (kvm);
it moves __tdx_td_init() from KVM_CRAETE_VM->tdx_vm_init() to ...
Quoted 56 lines
arch/x86/kvm/vmx/tdx.c +53
-0+ kvm_tdx->state =TD_STATE_UNINITIALIZED ; + +return 0 ; } +static int tdx_td_init (struct kvm *kvm,struct kvm_tdx_cmd *cmd) +{ +struct kvm_tdx *kvm_tdx =to_kvm_tdx (kvm); +struct kvm_tdx_init_vm *init_vm; +struct td_params *td_params =NULL ; +int ret; + + BUILD_BUG_ON(sizeof(*init_vm) != 256 + sizeof_field(struct kvm_tdx_init_vm, cpuid)); +BUILD_BUG_ON (sizeof (struct td_params ) !=1024 ); + +if (kvm_tdx->state !=TD_STATE_UNINITIALIZED ) +return -EINVAL ; + +if (cmd->flags) +return -EINVAL ; + + init_vm =kmalloc (sizeof (*init_vm) + +sizeof (init_vm->cpuid.entries[0 ]) *KVM_MAX_CPUID_ENTRIES , +GFP_KERNEL ); +if (!init_vm) +return -ENOMEM ; + +if (copy_from_user (init_vm,u64_to_user_ptr (cmd->data),sizeof (*init_vm))) { + ret = -EFAULT ; + goto out; + } + +if (init_vm->cpuid.nent >KVM_MAX_CPUID_ENTRIES ) { + ret = -E2BIG ; + goto out; + } + +if (copy_from_user (init_vm->cpuid.entries, +u64_to_user_ptr (cmd->data) +sizeof (*init_vm), +flex_array_size (init_vm, cpuid.entries, init_vm->cpuid.nent))) { + ret = -EFAULT ; + goto out; + } + +if (memchr_inv (init_vm->reserved,0 ,sizeof (init_vm->reserved))) { + ret = -EINVAL ; + goto out; + } + +if (init_vm->cpuid.padding) { + ret = -EINVAL ; + goto out; + } + + td_params =kzalloc (sizeof (struct td_params ),GFP_KERNEL );
arch/x86/kvm/vmx/tdx.c static int __tdx_td_init(struct kvm *kvm) · line 847
Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +10
-0+if (!td_params) { + ret = -ENOMEM ; + goto out; + } + + ret =setup_tdparams (kvm, td_params, init_vm); +if (ret) + goto out; + + ret =__tdx_td_init (kvm, td_params, &cmd->hw_error);
... KVM_TDX_INIT_VM, which moves the keyid allocation, TDR/TDCS page allocation and other works from KVM_CREATE_VM to KVM_TDX_INIT_VM as well.
I'm not sure if it is intentional, or by accident. There is no mentioning and justfication of it.
Quoted 29 lines
arch/x86/kvm/vmx/tdx.c +19
-0+if (ret) + goto out; + + kvm_tdx->tsc_offset =td_tdcs_exec_read64 (kvm_tdx,TD_TDCS_EXEC_TSC_OFFSET ); + kvm_tdx->attributes = td_params->attributes; + kvm_tdx->xfam = td_params->xfam; + + kvm_tdx->state =TD_STATE_INITIALIZED ; +out: +/* kfree() accepts NULL. */ +kfree (init_vm); +kfree (td_params); + +return ret; +} +int tdx_vm_ioctl (struct kvm *kvm,void __user *argp) {struct kvm_tdx_cmd tdx_cmd;@@ -647,6 +882,9 @@ int tdx_vm_ioctl(struct kvm *kvm, void __user *argp)case KVM_TDX_CAPABILITIES : r =tdx_get_capabilities (&tdx_cmd);break ; +case KVM_TDX_INIT_VM : + r =tdx_td_init (kvm, &tdx_cmd); +break ;default : r = -EINVAL ; goto out;
Paolo Bonzini
maintainerRe: [PATCH 23/30] KVM: TDX: initialize VM with TDX specific parameters
Quoted 19 lines · Xiaoyao Li
On 2/21/2025 1:05 AM, Paolo Bonzini wrote:
...
arch/x86/kvm/vmx/tdx.c int tdx_vm_init(struct kvm *kvm) · line 406
Quoted 5 lines
arch/x86/kvm/vmx/tdx.c +0
-2@@ -403,8 +412,9 @@ int tdx_vm_init(struct kvm *kvm)*/ kvm->max_vcpus = min_t(int, kvm->max_vcpus, num_present_cpus()); - /* Place holder for TDX specific logic. */ - return __tdx_td_init(kvm);it moves
__tdx_td_init()fromKVM_CRAETE_VM->tdx_vm_init()to ...Quoted 7 lines
arch/x86/kvm/vmx/tdx.c +5
-0+ kvm_tdx->state = TD_STATE_UNINITIALIZED; + + return 0; } +static int tdx_td_init (struct kvm *kvm,struct kvm_tdx_cmd *cmd) +{
...
Quoted 9 lines
Quoted 5 lines
+ ret =
setup_tdparams(kvm, td_params, init_vm); + if (ret)
+ goto out;
+
+ ret =__tdx_td_init(kvm, td_params, &cmd->hw_error);...
KVM_TDX_INIT_VM, which moves the keyid allocation, TDR/TDCS page allocation and other works fromKVM_CREATE_VMtoKVM_TDX_INIT_VMas well.I'm not sure if it is intentional, or by accident. There is no mentioning and justfication of it.
Until this patch there was no KVM_TDX_INIT_VM ioctl, so there was no separation between uninitialized and initialized TDs - the TD was already initialized right after KVM_CREATE_VM.
I can adjust a bit the commit message.
Paolo
Quoted 32 lines
Quoted 30 lines
+ if (ret)
+ goto out;
+
+kvm_tdx->tsc_offset=td_tdcs_exec_read64(kvm_tdx, TD_TDCS_EXEC_TSC_OFFSET);
+kvm_tdx->attributes=td_params->attributes; +kvm_tdx->xfam=td_params->xfam;arch/x86/kvm/vmx/tdx.c +10
-0+ + kvm_tdx->state = TD_STATE_INITIALIZED; +out: + /* kfree() accepts NULL. */ + kfree(init_vm); + kfree(td_params); + + return ret; +} +int
tdx_vm_ioctl(struct kvm *kvm, void __user *argp){
structkvm_tdx_cmdtdx_cmd;(quoted diff) +0
-0@@ -647,6 +882,9 @@ int tdx_vm_ioctl(struct kvm *kvm, void __user *argp)case
KVM_TDX_CAPABILITIES:
r =tdx_get_capabilities(&tdx_cmd);
break;
+ caseKVM_TDX_INIT_VM:
+ r =tdx_td_init(kvm, &tdx_cmd);
+ break;
default:
r =-EINVAL;
goto out;
Paolo Bonzini
maintainerPATCH v3 24/30 KVM: TDX: Make pmu_intel.c ignore guest TD case
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
TDX KVM doesn't support PMU yet, it's future work of TDX KVM support as another patch series. For now, handle TDX by updating vcpu_to_lbr_desc() and vcpu_to_lbr_records() to return NULL.
---
- Add pragma poison for to_vmx() (Paolo)
--- arch/x86/kvm/vmx/pmu_intel.c | 52 +++++++++++++++++++++++++++++++++++- arch/x86/kvm/vmx/pmu_intel.h | 28 +++++++++++++++++++ arch/x86/kvm/vmx/vmx.h | 34 +---------------------- 3 files changed, 80 insertions(+), 34 deletions(-) create mode 100644 arch/x86/kvm/vmx/pmu_intel.h
arch/x86/kvm/vmx/pmu_intel.c +51 -1
@@ -19,6 +19,7 @@#include "lapic.h" #include "nested.h" #include "pmu.h" +#include "tdx.h" /* * Perf's "BASE" is wildly misleading, architectural PMUs use bits 31:16 of ECX
@@ -34,6 +35,24 @@#define MSR_PMC_FULL_WIDTH_BIT (MSR_IA32_PMC0 - MSR_IA32_PERFCTR0) +static struct lbr_desc *vcpu_to_lbr_desc (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) +return NULL ; + +return &to_vmx (vcpu)->lbr_desc; +} + +static struct x86_pmu_lbr *vcpu_to_lbr_records (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) +return NULL ; + +return &to_vmx (vcpu)->lbr_desc.records; +} + +#pragma GCC poison to_vmx +static void reprogram_fixed_counters (struct kvm_pmu *pmu,u64 data) {struct kvm_pmc *pmc;
@@ -129,6 +148,22 @@ static inline struct kvm_pmc *get_fw_gp_pmc(struct kvm_pmu *pmu, u32 msr)return get_gp_pmc (pmu, msr,MSR_IA32_PMC0 ); } +static bool intel_pmu_lbr_is_compatible (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) +return false; + +return cpuid_model_is_consistent (vcpu); +} + +bool intel_pmu_lbr_is_enabled (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) +return false; + +return !!vcpu_to_lbr_records (vcpu)->nr; +} +static bool intel_pmu_is_valid_lbr_msr (struct kvm_vcpu *vcpu,u32 index) {struct x86_pmu_lbr *records =vcpu_to_lbr_records (vcpu);
@@ -194,6 +229,9 @@ static inline void intel_pmu_release_guest_lbr_event(struct kvm_vcpu *vcpu) {struct lbr_desc *lbr_desc =vcpu_to_lbr_desc (vcpu); +if (!lbr_desc) +return ; +if (lbr_desc->event) {perf_event_release_kernel (lbr_desc->event); lbr_desc->event =NULL ;
@@ -235,6 +273,9 @@ int intel_pmu_create_guest_lbr_event(struct kvm_vcpu *vcpu) PERF_SAMPLE_BRANCH_USER, }; +if (WARN_ON_ONCE (!lbr_desc)) +return 0 ; +if (unlikely (lbr_desc->event)) {__set_bit (INTEL_PMC_IDX_FIXED_VLBR , pmu->pmc_in_use);return 0 ;
@@ -466,6 +507,9 @@ static void intel_pmu_refresh(struct kvm_vcpu *vcpu)u64 perf_capabilities;u64 counter_rsvd; +if (!lbr_desc) +return ; +memset (&lbr_desc->records,0 ,sizeof (lbr_desc->records));/*
@@ -542,7 +586,7 @@ static void intel_pmu_refresh(struct kvm_vcpu *vcpu) INTEL_PMC_MAX_GENERIC, pmu->nr_arch_fixed_counters); perf_capabilities =vcpu_get_perf_capabilities (vcpu); -if (cpuid_model_is_consistent (vcpu) && +if (intel_pmu_lbr_is_compatible (vcpu) && (perf_capabilities &PMU_CAP_LBR_FMT ))memcpy (&lbr_desc->records, &vmx_lbr_caps,sizeof (vmx_lbr_caps));else
@@ -570,6 +614,9 @@ static void intel_pmu_init(struct kvm_vcpu *vcpu)struct kvm_pmu *pmu =vcpu_to_pmu (vcpu);struct lbr_desc *lbr_desc =vcpu_to_lbr_desc (vcpu); +if (!lbr_desc) +return ; +for (i =0 ; i <KVM_MAX_NR_INTEL_GP_COUNTERS ; i++) { pmu->gp_counters[i].type =KVM_PMC_GP ; pmu->gp_counters[i].vcpu = vcpu;
@@ -677,6 +724,9 @@ void vmx_passthrough_lbr_msrs(struct kvm_vcpu *vcpu)struct kvm_pmu *pmu =vcpu_to_pmu (vcpu);struct lbr_desc *lbr_desc =vcpu_to_lbr_desc (vcpu); +if (WARN_ON_ONCE (!lbr_desc)) +return ; +if (!lbr_desc->event) {vmx_disable_lbr_msrs_passthrough (vcpu);if (vmcs_read64 (GUEST_IA32_DEBUGCTL ) &DEBUGCTLMSR_LBR )
arch/x86/kvm/vmx/pmu_intel.h new file +28 -0
@@ -0,0 +1,28 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef __KVM_X86_VMX_PMU_INTEL_H +#define __KVM_X86_VMX_PMU_INTEL_H + +#include <linux/kvm_host.h> + +bool intel_pmu_lbr_is_enabled (struct kvm_vcpu *vcpu); +int intel_pmu_create_guest_lbr_event (struct kvm_vcpu *vcpu); + +struct lbr_desc { +/* Basic info about guest LBR records. */ +struct x86_pmu_lbr records; + +/* +* Emulate LBR feature via passthrough LBR registers when the +* per-vcpu guest LBR event is scheduled on the current pcpu. +* +* The records may be inaccurate if the host reclaims the LBR. +*/ +struct perf_event *event; + +/* True if LBRs are marked as not intercepted in the MSR bitmap */ +bool msr_passthrough; +}; + +extern struct x86_pmu_lbr vmx_lbr_caps; + +#endif /* __KVM_X86_VMX_PMU_INTEL_H */
arch/x86/kvm/vmx/vmx.h +1 -33
@@ -11,6 +11,7 @@#include "capabilities.h" #include "../kvm_cache_regs.h" +#include "pmu_intel.h" #include "vmcs.h" #include "vmx_ops.h" #include "../cpuid.h"
@@ -90,24 +91,6 @@ union vmx_exit_reason {u32 full; }; -struct lbr_desc { -/* Basic info about guest LBR records. */ -struct x86_pmu_lbr records; - -/* -* Emulate LBR feature via passthrough LBR registers when the -* per-vcpu guest LBR event is scheduled on the current pcpu. -* -* The records may be inaccurate if the host reclaims the LBR. -*/ -struct perf_event *event; - -/* True if LBRs are marked as not intercepted in the MSR bitmap */ -bool msr_passthrough; -}; - -extern struct x86_pmu_lbr vmx_lbr_caps; -/* * The nested_vmx structure is part of vcpu_vmx, and holds information we need * for correct emulation of VMX (i.e., nested VMX) on this vcpu.
@@ -664,21 +647,6 @@ static __always_inline struct vcpu_vmx *to_vmx(struct kvm_vcpu *vcpu) return container_of(vcpu, struct vcpu_vmx, vcpu); } -static inline struct lbr_desc *vcpu_to_lbr_desc (struct kvm_vcpu *vcpu) -{ -return &to_vmx (vcpu)->lbr_desc; -} - -static inline struct x86_pmu_lbr *vcpu_to_lbr_records (struct kvm_vcpu *vcpu) -{ -return &vcpu_to_lbr_desc (vcpu)->records; -} - -static inline bool intel_pmu_lbr_is_enabled (struct kvm_vcpu *vcpu) -{ -return !!vcpu_to_lbr_records (vcpu)->nr; -} -void intel_pmu_cross_mapped_check (struct kvm_pmu *pmu);int intel_pmu_create_guest_lbr_event (struct kvm_vcpu *vcpu);void vmx_passthrough_lbr_msrs (struct kvm_vcpu *vcpu);
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 25/30 KVM: TDX: Don't offline the last cpu of one package when there's TDX guest
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Destroying TDX guest requires there's at least one cpu online for each package, because reclaiming the TDX KeyID of the guest (as part of the teardown process) requires to call some SEAMCALL (on any cpu) on all packages.
Do not offline the last cpu of one package when there's any TDX guest running, otherwise KVM may not be able to teardown TDX guest resulting in leaking of TDX KeyID and other resources like TDX guest control structure pages.
Implement the TDX version 'offline_cpu()' to prevent the cpu from going offline if it is the last cpu on the package.
--- arch/x86/kvm/vmx/tdx.c | 43 +++++++++++++++++++++++++++++++++++++++++- 1 file changed, 42 insertions(+), 1 deletion(-)
arch/x86/kvm/vmx/tdx.c +42 -1
@@ -131,6 +131,8 @@ static int init_kvm_tdx_caps(const struct tdx_sys_info_td_conf *td_conf,*/ static DEFINE_MUTEX (tdx_lock); +static atomic_t nr_configured_hkid; +/* Maximum number of retries to attempt for SEAMCALLs. */ #define TDX_SEAMCALL_RETRIES 10000
@@ -138,6 +140,7 @@ static inline void tdx_hkid_free(struct kvm_tdx *kvm_tdx) {tdx_guest_keyid_free (kvm_tdx->hkid); kvm_tdx->hkid =-1 ; +atomic_dec (&nr_configured_hkid); }static inline bool is_hkid_assigned (struct kvm_tdx *kvm_tdx)
@@ -617,6 +620,8 @@ static int __tdx_td_init(struct kvm *kvm, struct td_params *td_params, ret = -ENOMEM ; +atomic_inc (&nr_configured_hkid); + tdr_page =alloc_page (GFP_KERNEL );if (!tdr_page) goto free_hkid;
@@ -913,6 +918,42 @@ static int tdx_online_cpu(unsigned int cpu)return r; } +static int tdx_offline_cpu (unsigned int cpu) +{ +int i; + +/* No TD is running. Allow any cpu to be offline. */ +if (!atomic_read (&nr_configured_hkid)) +return 0 ; + +/* +* In order to reclaim TDX HKID, (i.e. when deleting guest TD), need to +* call TDH.PHYMEM.PAGE.WBINVD on all packages to program all memory +* controller with pconfig. If we have active TDX HKID, refuse to +* offline the last online cpu. +*/ +for_each_online_cpu (i) { +/* +* Found another online cpu on the same package. +* Allow to offline. +*/ +if (i != cpu &&topology_physical_package_id (i) == +topology_physical_package_id (cpu)) +return 0 ; + } + +/* +* This is the last cpu of this package. Don't offline it. +* +* Because it's hard for human operator to understand the +* reason, warn it. +*/ +#define MSG_ALLPKG_ONLINE \ + "TDX requires all packages to have an online CPU. Delete all TDs in order to offline all CPUs of a package.\n" +pr_warn_ratelimited (MSG_ALLPKG_ONLINE ); +return -EBUSY ; +} +static void __do_tdx_cleanup (void ) {/*
@@ -938,7 +979,7 @@ static int __init __do_tdx_bringup(void)*/ r =cpuhp_setup_state_cpuslocked (CPUHP_AP_ONLINE_DYN ,"kvm/cpu/tdx:online" , - tdx_online_cpu,NULL ); + tdx_online_cpu, tdx_offline_cpu);if (r <0 )return r;
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 26/30 KVM: TDX: create/free TDX vcpu structure
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
Implement vcpu related stubs for TDX for create, reset and free.
For now, create only the features that do not require the TDX SEAMCALL. The TDX specific vcpu initialization will be handled by KVM_TDX_INIT_VCPU.
---
- Use lapic_in_kernel() (Nikolay Borisov)
--- arch/x86/kvm/vmx/main.c | 42 ++++++++++++++++++++++++++++++++++---- arch/x86/kvm/vmx/tdx.c | 35 +++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/x86_ops.h | 8 ++++++++ 3 files changed, 81 insertions(+), 4 deletions(-)
arch/x86/kvm/vmx/main.c +38 -4
@@ -64,6 +64,40 @@ static void vt_vm_free(struct kvm *kvm)tdx_vm_free (kvm); } +static int vt_vcpu_precreate (struct kvm *kvm) +{ +if (is_td (kvm)) +return 0 ; + +return vmx_vcpu_precreate (kvm); +} + +static int vt_vcpu_create (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) +return tdx_vcpu_create (vcpu); + +return vmx_vcpu_create (vcpu); +} + +static void vt_vcpu_free (struct kvm_vcpu *vcpu) +{ +if (is_td_vcpu (vcpu)) { +tdx_vcpu_free (vcpu); +return ; + } + +vmx_vcpu_free (vcpu); +} + +static void vt_vcpu_reset (struct kvm_vcpu *vcpu,bool init_event) +{ +if (is_td_vcpu (vcpu)) +return ; + +vmx_vcpu_reset (vcpu, init_event); +} +static int vt_mem_enc_ioctl (struct kvm *kvm,void __user *argp) {if (!is_td (kvm))
@@ -100,10 +134,10 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .vm_destroy = vt_vm_destroy, .vm_free = vt_vm_free, - .vcpu_precreate = vmx_vcpu_precreate, - .vcpu_create = vmx_vcpu_create, - .vcpu_free = vmx_vcpu_free, - .vcpu_reset = vmx_vcpu_reset, + .vcpu_precreate = vt_vcpu_precreate, + .vcpu_create = vt_vcpu_create, + .vcpu_free = vt_vcpu_free, + .vcpu_reset = vt_vcpu_reset, .prepare_switch_to_guest = vmx_prepare_switch_to_guest, .vcpu_load = vmx_vcpu_load,
arch/x86/kvm/vmx/tdx.c +35 -0
@@ -4,6 +4,7 @@#include <asm/tdx.h> #include "capabilities.h" #include "x86_ops.h" +#include "lapic.h" #include "tdx.h" #pragma GCC poison to_vmx
@@ -420,6 +421,40 @@ int tdx_vm_init(struct kvm *kvm)return 0 ; } +int tdx_vcpu_create (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx *kvm_tdx =to_kvm_tdx (vcpu->kvm); + +if (kvm_tdx->state !=TD_STATE_INITIALIZED ) +return -EIO ; + +/* TDX module mandates APICv, which requires an in-kernel local APIC. */ +if (!lapic_in_kernel (vcpu)) +return -EINVAL ; + +fpstate_set_confidential (&vcpu->arch.guest_fpu); + + vcpu->arch.efer =EFER_SCE |EFER_LME |EFER_LMA |EFER_NX ; + + vcpu->arch.cr0_guest_owned_bits =-1ul ; + vcpu->arch.cr4_guest_owned_bits =-1ul ; + + vcpu->arch.tsc_offset = kvm_tdx->tsc_offset; + vcpu->arch.l1_tsc_offset = vcpu->arch.tsc_offset; + vcpu->arch.guest_state_protected = + !(to_kvm_tdx (vcpu->kvm)->attributes &TDX_TD_ATTR_DEBUG ); + +if ((kvm_tdx->xfam &XFEATURE_MASK_XTILE ) ==XFEATURE_MASK_XTILE ) + vcpu->arch.xfd_no_write_intercept = true; + +return 0 ; +} + +void tdx_vcpu_free (struct kvm_vcpu *vcpu) +{ +/* This is stub for now. More logic will come. */ +} +static int tdx_get_capabilities (struct kvm_tdx_cmd *cmd) {const struct tdx_sys_info_td_conf *td_conf = &tdx_sysinfo->td_conf;
arch/x86/kvm/vmx/x86_ops.h +8 -0
@@ -125,12 +125,20 @@ void vmx_setup_mce(struct kvm_vcpu *vcpu);int tdx_vm_init (struct kvm *kvm);void tdx_mmu_release_hkid (struct kvm *kvm);void tdx_vm_free (struct kvm *kvm); +int tdx_vm_ioctl (struct kvm *kvm,void __user *argp); + +int tdx_vcpu_create (struct kvm_vcpu *vcpu); +void tdx_vcpu_free (struct kvm_vcpu *vcpu);#else static inline int tdx_vm_init (struct kvm *kvm) {return -EOPNOTSUPP ; }static inline void tdx_mmu_release_hkid (struct kvm *kvm) {}static inline void tdx_vm_free (struct kvm *kvm) {} +static inline int tdx_vm_ioctl (struct kvm *kvm,void __user *argp) {return -EOPNOTSUPP ; } + +static inline int tdx_vcpu_create (struct kvm_vcpu *vcpu) {return -EOPNOTSUPP ; } +static inline void tdx_vcpu_free (struct kvm_vcpu *vcpu) {}#endif #endif /* __KVM_X86_VMX_X86_OPS_H */
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 27/30 KVM: TDX: Do TDX specific vcpu initialization
In reply to Paolo BonziniFrom: Isaku Yamahata <[email protected]>
TD guest vcpu needs TDX specific initialization before running. Repurpose KVM_MEMORY_ENCRYPT_OP to vcpu-scope, add a new sub-command KVM_TDX_INIT_VCPU, and implement the callback for it.
---
- Fix comment: https://lore.kernel.org/kvm/[email protected]/
(Sean)
--- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 1 + arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/kvm/lapic.c | 1 + arch/x86/kvm/vmx/main.c | 9 ++ arch/x86/kvm/vmx/tdx.c | 172 ++++++++++++++++++++++++++++- arch/x86/kvm/vmx/tdx.h | 11 +- arch/x86/kvm/vmx/x86_ops.h | 4 + arch/x86/kvm/x86.c | 7 ++ 9 files changed, 205 insertions(+), 2 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +1 -0
@@ -127,6 +127,7 @@ KVM_X86_OP(enable_smi_window)#endif KVM_X86_OP_OPTIONAL(dev_get_attr) KVM_X86_OP(mem_enc_ioctl) +KVM_X86_OP_OPTIONAL(vcpu_mem_enc_ioctl) KVM_X86_OP_OPTIONAL(mem_enc_register_region) KVM_X86_OP_OPTIONAL(mem_enc_unregister_region) KVM_X86_OP_OPTIONAL(vm_copy_enc_context_from)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1847,6 +1847,7 @@ struct kvm_x86_ops {int (*dev_get_attr)(u32 group,u64 attr,u64 *val);int (*mem_enc_ioctl)(struct kvm *kvm,void __user *argp); +int (*vcpu_mem_enc_ioctl)(struct kvm_vcpu *vcpu,void __user *argp);int (*mem_enc_register_region)(struct kvm *kvm,struct kvm_enc_region *argp);int (*mem_enc_unregister_region)(struct kvm *kvm,struct kvm_enc_region *argp);int (*vm_copy_enc_context_from)(struct kvm *kvm,unsigned int source_fd);
arch/x86/include/uapi/asm/kvm.h +1 -0
@@ -931,6 +931,7 @@ struct kvm_hyperv_eventfd {enum kvm_tdx_cmd_id {KVM_TDX_CAPABILITIES =0 ,KVM_TDX_INIT_VM , +KVM_TDX_INIT_VCPU ,KVM_TDX_CMD_NR_MAX , };
arch/x86/kvm/lapic.c +1 -0
@@ -2657,6 +2657,7 @@ int kvm_apic_set_base(struct kvm_vcpu *vcpu, u64 value, bool host_initiated)kvm_recalculate_apic_map (vcpu->kvm);return 0 ; } +EXPORT_SYMBOL_GPL (kvm_apic_set_base);void kvm_apic_update_apicv (struct kvm_vcpu *vcpu) {
arch/x86/kvm/vmx/main.c +9 -0
@@ -106,6 +106,14 @@ static int vt_mem_enc_ioctl(struct kvm *kvm, void __user *argp)return tdx_vm_ioctl (kvm, argp); } +static int vt_vcpu_mem_enc_ioctl (struct kvm_vcpu *vcpu,void __user *argp) +{ +if (!is_td_vcpu (vcpu)) +return -EINVAL ; + +return tdx_vcpu_ioctl (vcpu, argp); +} +#define VMX_REQUIRED_APICV_INHIBITS \ (BIT(APICV_INHIBIT_REASON_DISABLED) | \ BIT(APICV_INHIBIT_REASON_ABSENT) | \
@@ -262,6 +270,7 @@ struct kvm_x86_ops vt_x86_ops __initdata = { .get_untagged_addr = vmx_get_untagged_addr, .mem_enc_ioctl = vt_mem_enc_ioctl, + .vcpu_mem_enc_ioctl = vt_vcpu_mem_enc_ioctl, };struct kvm_x86_init_ops vt_init_ops__initdata = {
arch/x86/kvm/vmx/tdx.c +171 -1
201 lines not on this page · raw message
arch/x86/kvm/vmx/tdx.h +10 -1
@@ -32,9 +32,18 @@ struct kvm_tdx {struct tdx_td td; }; +/* TDX module vCPU states */ +enum vcpu_tdx_state { +VCPU_TD_STATE_UNINITIALIZED =0 , +VCPU_TD_STATE_INITIALIZED , +}; +struct vcpu_tdx {struct kvm_vcpu vcpu; -/* TDX specific members follow. */ + +struct tdx_vp vp; + +enum vcpu_tdx_state state; };static inline bool is_td (struct kvm *kvm)
arch/x86/kvm/vmx/x86_ops.h +4 -0
@@ -130,6 +130,8 @@ int tdx_vm_ioctl(struct kvm *kvm, void __user *argp);int tdx_vcpu_create (struct kvm_vcpu *vcpu);void tdx_vcpu_free (struct kvm_vcpu *vcpu); + +int tdx_vcpu_ioctl (struct kvm_vcpu *vcpu,void __user *argp);#else static inline int tdx_vm_init (struct kvm *kvm) {return -EOPNOTSUPP ; }static inline void tdx_mmu_release_hkid (struct kvm *kvm) {}
@@ -139,6 +141,8 @@ static inline int tdx_vm_ioctl(struct kvm *kvm, void __user *argp) { return -EOPstatic inline int tdx_vcpu_create (struct kvm_vcpu *vcpu) {return -EOPNOTSUPP ; }static inline void tdx_vcpu_free (struct kvm_vcpu *vcpu) {} + +static inline int tdx_vcpu_ioctl (struct kvm_vcpu *vcpu,void __user *argp) {return -EOPNOTSUPP ; }#endif #endif /* __KVM_X86_VMX_X86_OPS_H */
arch/x86/kvm/x86.c +7 -0
@@ -6275,6 +6275,12 @@ long kvm_arch_vcpu_ioctl(struct file *filp,case KVM_SET_DEVICE_ATTR : r =kvm_vcpu_ioctl_device_attr (vcpu, ioctl, argp);break ; +case KVM_MEMORY_ENCRYPT_OP : + r = -ENOTTY ; +if (!kvm_x86_ops.vcpu_mem_enc_ioctl) + goto out; + r = kvm_x86_ops.vcpu_mem_enc_ioctl (vcpu, argp); +break ;default : r = -EINVAL ; }
@@ -12660,6 +12666,7 @@ bool kvm_vcpu_is_reset_bsp(struct kvm_vcpu *vcpu) {return vcpu->kvm->arch.bsp_vcpu_id == vcpu->vcpu_id; } +EXPORT_SYMBOL_GPL (kvm_vcpu_is_reset_bsp);bool kvm_vcpu_is_bsp (struct kvm_vcpu *vcpu) {
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 28/30 KVM: x86: Introduce KVM_TDX_GET_CPUID
In reply to Paolo BonziniFrom: Xiaoyao Li <[email protected]>
Implement an IOCTL to allow userspace to read the CPUID bit values for a configured TD.
The TDX module doesn't provide the ability to set all CPUID bits. Instead some are configured indirectly, or have fixed values. But it does allow for the final resulting CPUID bits to be read. This information will be useful for userspace to understand the configuration of the TD, and set KVM's copy via KVM_SET_CPUID2.
---
- Fix subleaf mask check (Binbin)
- Search all possible sub-leafs (Francesco Lavra)
- Reduce off-by-one error sensitve code (Francesco, Xiaoyao)
- Handle buffers too small from userspace (Xiaoyao)
- Read max CPUID from TD instead of using fixed values (Xiaoyao)
--- arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/kvm/vmx/tdx.c | 191 ++++++++++++++++++++++++++++++++ arch/x86/kvm/vmx/tdx_arch.h | 5 + arch/x86/kvm/vmx/tdx_errno.h | 1 + 4 files changed, 198 insertions(+)
arch/x86/include/uapi/asm/kvm.h +1 -0
@@ -932,6 +932,7 @@ enum kvm_tdx_cmd_id {KVM_TDX_CAPABILITIES =0 ,KVM_TDX_INIT_VM ,KVM_TDX_INIT_VCPU , +KVM_TDX_GET_CPUID , KVM_TDX_CMD_NR_MAX, };
arch/x86/kvm/vmx/tdx.c +191 -0
215 lines not on this page · raw message
arch/x86/kvm/vmx/tdx_arch.h +5 -0
@@ -122,4 +122,9 @@ struct td_params {#define MD_FIELD_ID_FEATURES0_TOPOLOGY_ENUM BIT_ULL(20) +/* +* TD scope metadata field ID. +*/ +#define TD_MD_FIELD_ID_CPUID_VALUES 0x9410000300000000ULL +#endif /* __KVM_X86_TDX_ARCH_H */
arch/x86/kvm/vmx/tdx_errno.h +1 -0
@@ -23,6 +23,7 @@#define TDX_FLUSHVP_NOT_DONE 0x8000082400000000ULL#define TDX_EPT_WALK_FAILED 0xC0000B0000000000ULL#define TDX_EPT_ENTRY_STATE_INCORRECT 0xC0000B0D00000000ULL +#define TDX_METADATA_FIELD_NOT_READABLE 0xC0000C0200000000ULL/* * TDX module operand ID, appears in 31:0 part of error code as
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 29/30 KVM: x86/mmu: Taking guest pa into consideration when calculate tdp level
In reply to Paolo BonziniFrom: Xiaoyao Li <[email protected]>
For TDX, the maxpa (CPUID.0x80000008.EAX[7:0]) is fixed as native and the max_gpa (CPUID.0x80000008.EAX[23:16]) is configurable and used to configure the EPT level and GPAW.
Use max_gpa to determine the TDP level.
--- arch/x86/kvm/cpuid.c | 14 ++++++++++++++ arch/x86/kvm/cpuid.h | 1 + arch/x86/kvm/mmu/mmu.c | 9 ++++++++- 3 files changed, 23 insertions(+), 1 deletion(-)
arch/x86/kvm/cpuid.c +14 -0
@@ -494,6 +494,20 @@ int cpuid_query_maxphyaddr(struct kvm_vcpu *vcpu)return 36 ; } +int cpuid_query_maxguestphyaddr (struct kvm_vcpu *vcpu) +{ +struct kvm_cpuid_entry2 *best; + + best =kvm_find_cpuid_entry (vcpu,0x80000000 ); +if (!best || best->eax <0x80000008 ) + goto not_found; + best =kvm_find_cpuid_entry (vcpu,0x80000008 ); +if (best) +return (best->eax >>16 ) &0xff ; +not_found: +return 0 ; +} +/* * This "raw" version returns the reserved GPA bits without any adjustments for * encryption technologies that usurp bits. The raw mask should be used if and
arch/x86/kvm/cpuid.h +1 -0
@@ -37,6 +37,7 @@ void __init kvm_init_xstate_sizes(void);u32 xstate_required_size (u64 xstate_bv,bool compacted);int cpuid_query_maxphyaddr (struct kvm_vcpu *vcpu); +int cpuid_query_maxguestphyaddr (struct kvm_vcpu *vcpu);u64 kvm_vcpu_reserved_gpa_bits_raw (struct kvm_vcpu *vcpu);static inline int cpuid_maxphyaddr (struct kvm_vcpu *vcpu)
arch/x86/kvm/mmu/mmu.c +8 -1
@@ -5416,12 +5416,19 @@ void __kvm_mmu_refresh_passthrough_bits(struct kvm_vcpu *vcpu,static inline int kvm_mmu_get_tdp_level (struct kvm_vcpu *vcpu) { +int maxpa; + +if (vcpu->kvm->arch.vm_type ==KVM_X86_TDX_VM ) + maxpa =cpuid_query_maxguestphyaddr (vcpu); +else + maxpa =cpuid_maxphyaddr (vcpu); +/* tdp_root_level is architecture forced level, use it if nonzero */ if (tdp_root_level)return tdp_root_level;/* Use 5-level TDP if and only if it's useful/necessary. */ -if (max_tdp_level ==5 &&cpuid_maxphyaddr (vcpu) <=48 ) +if (max_tdp_level ==5 && maxpa <=48 )return 4 ;return max_tdp_level;
Signature · 1 line
2.43.5
Paolo Bonzini
maintainerPATCH v3 30/30 KVM: TDX: Register TDX host key IDs to cgroup misc controller
In reply to Paolo BonziniFrom: Zhiming Hu <[email protected]>
TDX host key IDs (HKID) are limit resources in a machine, and the misc cgroup lets the machine owner track their usage and limits the possibility of abusing them outside the owner's control.
The cgroup v2 miscellaneous subsystem was introduced to control the resource of AMD SEV & SEV-ES ASIDs. Likewise introduce HKIDs as a misc resource.
--- arch/x86/include/asm/tdx.h | 2 ++ arch/x86/kvm/vmx/tdx.c | 14 ++++++++++++++ arch/x86/kvm/vmx/tdx.h | 1 + arch/x86/virt/vmx/tdx/tdx.c | 6 ++++++ include/linux/misc_cgroup.h | 4 ++++ kernel/cgroup/misc.c | 4 ++++ 6 files changed, 31 insertions(+)
arch/x86/include/asm/tdx.h +2 -0
@@ -124,6 +124,7 @@ const char *tdx_dump_mce_info(struct mce *m);const struct tdx_sys_info *tdx_get_sysinfo (void );int tdx_guest_keyid_alloc (void ); +u32 tdx_get_nr_guest_keyids (void );void tdx_guest_keyid_free (unsigned int keyid);struct tdx_td {
@@ -179,6 +180,7 @@ u64 tdh_phymem_page_wbinvd_tdr(struct tdx_td *td);static inline void tdx_init (void ) { }static inline int tdx_cpu_enable (void ) {return -ENODEV ; }static inline int tdx_enable (void ) {return -ENODEV ; } +static u32 tdx_get_nr_guest_keyids (void ) {return 0 ; }static inline const char *tdx_dump_mce_info (struct mce *m) {return NULL ; }static inline const struct tdx_sys_info *tdx_get_sysinfo (void ) {return NULL ; }#endif /* CONFIG_INTEL_TDX_HOST */
arch/x86/kvm/vmx/tdx.c +14 -0
@@ -1,6 +1,7 @@// SPDX-License-Identifier: GPL-2.0 #include <linux/cpu.h> #include <asm/cpufeature.h> +#include <linux/misc_cgroup.h> #include <asm/tdx.h> #include "capabilities.h" #include "mmu.h"
@@ -143,6 +144,9 @@ static inline void tdx_hkid_free(struct kvm_tdx *kvm_tdx)tdx_guest_keyid_free (kvm_tdx->hkid); kvm_tdx->hkid =-1 ;atomic_dec (&nr_configured_hkid); +misc_cg_uncharge (MISC_CG_RES_TDX , kvm_tdx->misc_cg,1 ); +put_misc_cg (kvm_tdx->misc_cg); + kvm_tdx->misc_cg =NULL ; }static inline bool is_hkid_assigned (struct kvm_tdx *kvm_tdx)
@@ -684,6 +688,10 @@ static int __tdx_td_init(struct kvm *kvm, struct td_params *td_params,if (ret <0 )return ret; kvm_tdx->hkid = ret; + kvm_tdx->misc_cg =get_current_misc_cg (); + ret =misc_cg_try_charge (MISC_CG_RES_TDX , kvm_tdx->misc_cg,1 ); +if (ret) + goto free_hkid; ret = -ENOMEM ;
@@ -1465,6 +1473,11 @@ static int __init __tdx_bringup(void) goto get_sysinfo_err; } +if (misc_cg_set_capacity (MISC_CG_RES_TDX ,tdx_get_nr_guest_keyids ())) { + r = -EINVAL ; + goto get_sysinfo_err; + } +/* * Leave hardware virtualization enabled after TDX is enabled * successfully. TDX CPU hotplug depends on this.
@@ -1481,6 +1494,7 @@ static int __init __tdx_bringup(void)void tdx_cleanup (void ) {if (enable_tdx) { +misc_cg_set_capacity (MISC_CG_RES_TDX ,0 );__do_tdx_cleanup ();kvm_disable_virtualization (); }
arch/x86/kvm/vmx/tdx.h +1 -0
@@ -21,6 +21,7 @@ enum kvm_tdx_state {struct kvm_tdx {struct kvm kvm; +struct misc_cg *misc_cg;int hkid;enum kvm_tdx_state state;
arch/x86/virt/vmx/tdx/tdx.c +6 -0
@@ -1476,6 +1476,12 @@ const struct tdx_sys_info *tdx_get_sysinfo(void) }EXPORT_SYMBOL_GPL (tdx_get_sysinfo); +u32 tdx_get_nr_guest_keyids (void ) +{ +return tdx_nr_guest_keyids; +} +EXPORT_SYMBOL_GPL (tdx_get_nr_guest_keyids); +int tdx_guest_keyid_alloc (void ) { return ida_alloc_range(&tdx_guest_keyid_pool, tdx_guest_keyid_start,
include/linux/misc_cgroup.h +4 -0
@@ -17,6 +17,10 @@ enum misc_res_type {MISC_CG_RES_SEV ,/** @MISC_CG_RES_SEV_ES: AMD SEV-ES ASIDs resource */ MISC_CG_RES_SEV_ES , +#endif +#ifdef CONFIG_INTEL_TDX_HOST +/* Intel TDX HKIDs resource */ +MISC_CG_RES_TDX , #endif/** @MISC_CG_RES_TYPES: count of enum misc_res_type constants */ MISC_CG_RES_TYPES
kernel/cgroup/misc.c +4 -0
@@ -24,6 +24,10 @@ static const char *const misc_res_name[] = {/* AMD SEV-ES ASIDs resource */ "sev_es",#endif +#ifdef CONFIG_INTEL_TDX_HOST +/* Intel TDX HKIDs resource */ + "tdx", +#endif };/* Root misc cgroup */
Signature · 1 line
2.43.5