[v14,109/113] Documentation/virt/kvm: Document on Trust Domain Extensions(TDX)

Message ID	51c2482f3f2bfff9469911c2e87acd2085dd5597.1685333728.git.isaku.yamahata@intel.com (mailing list archive)
State	New, archived
Headers	show Return-Path: <kvm-owner@vger.kernel.org> From: isaku.yamahata@intel.com To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Cc: isaku.yamahata@intel.com, isaku.yamahata@gmail.com, Paolo Bonzini <pbonzini@redhat.com>, erdemaktas@google.com, Sean Christopherson <seanjc@google.com>, Sagi Shahar <sagis@google.com>, David Matlack <dmatlack@google.com>, Kai Huang <kai.huang@intel.com>, Zhi Wang <zhi.wang.linux@gmail.com>, chen.bo@intel.com Subject: [PATCH v14 109/113] Documentation/virt/kvm: Document on Trust Domain Extensions(TDX) Date: Sun, 28 May 2023 21:20:31 -0700 Message-Id: <51c2482f3f2bfff9469911c2e87acd2085dd5597.1685333728.git.isaku.yamahata@intel.com> In-Reply-To: <cover.1685333727.git.isaku.yamahata@intel.com> References: <cover.1685333727.git.isaku.yamahata@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	KVM TDX basic feature support \| expand [v14,000/113] KVM TDX basic feature support [v14,001/113] KVM: VMX: Move out vmx_x86_ops to 'main.c' to wrap VMX and TDX [v14,002/113] KVM: x86/vmx: initialize loaded_vmcss_on_cpu in vmx_hardware_setup() [v14,003/113] KVM: x86/vmx: Refactor KVM VMX module init/exit functions [v14,004/113] KVM: TDX: Initialize the TDX module when loading the KVM intel kernel module [v14,005/113] KVM: TDX: Add placeholders for TDX VM/vcpu structure [v14,006/113] KVM: x86: Introduce vm_type to differentiate default VMs from confidential VMs [v14,007/113] KVM: TDX: Make TDX VM type supported [v14,008/113,MARKER] The start of TDX KVM patch series: TDX architectural definitions [v14,009/113] KVM: TDX: Define TDX architectural definitions [v14,010/113] KVM: TDX: Add TDX "architectural" error codes [v14,011/113] KVM: TDX: Add C wrapper functions for SEAMCALLs to the TDX module [v14,012/113] KVM: TDX: Add helper functions to print TDX SEAMCALL error [v14,013/113,MARKER] The start of TDX KVM patch series: TD VM creation/destruction [v14,014/113] x86/cpu: Add helper functions to allocate/free TDX private host key id [v14,015/113] x86/virt/tdx: Add a helper function to return system wide info about TDX module [v14,016/113] KVM: TDX: Add place holder for TDX VM specific mem_enc_op ioctl [v14,017/113] KVM: TDX: x86: Add ioctl to get TDX systemwide parameters [v14,018/113] KVM: x86, tdx: Make KVM_CAP_MAX_VCPUS backend specific [v14,019/113] KVM: TDX: create/destroy VM structure [v14,020/113] KVM: TDX: initialize VM with TDX specific parameters [v14,021/113] KVM: TDX: Make pmu_intel.c ignore guest TD case [v14,022/113] KVM: TDX: Refuse to unplug the last cpu on the package [v14,023/113,MARKER] The start of TDX KVM patch series: TD vcpu creation/destruction [v14,024/113] KVM: TDX: allocate/free TDX vcpu structure [v14,025/113] KVM: TDX: Do TDX specific vcpu initialization [v14,026/113,MARKER] The start of TDX KVM patch series: KVM MMU GPA shared bits [v14,027/113] KVM: x86/mmu: introduce config for PRIVATE KVM MMU [v14,028/113] KVM: x86/mmu: Add address conversion functions for TDX shared bit of GPA [v14,029/113,MARKER] The start of TDX KVM patch series: KVM TDP refactoring for TDX [v14,030/113] KVM: Allow page-sized MMU caches to be initialized with custom 64-bit values [v14,031/113] KVM: x86/mmu: Replace hardcoded value 0 for the initial value for SPTE [v14,032/113] KVM: x86/mmu: Allow non-zero value for non-present SPTE and removed SPTE [v14,033/113] KVM: x86/mmu: Add Suppress VE bit to shadow_mmio_mask/shadow_present_mask [v14,034/113] KVM: x86/mmu: Track shadow MMIO value on a per-VM basis [v14,035/113] KVM: x86/mmu: Disallow fast page fault on private GPA [v14,036/113] KVM: x86/mmu: Allow per-VM override of the TDP max page level [v14,037/113] KVM: VMX: Introduce test mode related to EPT violation VE [v14,038/113,MARKER] The start of TDX KVM patch series: KVM TDP MMU hooks [v14,039/113] KVM: x86/mmu: Assume guest MMIOs are shared [v14,040/113] KVM: x86/tdp_mmu: Init role member of struct kvm_mmu_page at allocation [v14,041/113] KVM: x86/mmu: Add a new is_private member for union kvm_mmu_page_role [v14,042/113] KVM: x86/mmu: Add a private pointer to struct kvm_mmu_page [v14,043/113] KVM: Add flags to struct kvm_gfn_range [v14,044/113] KVM: x86/tdp_mmu: Don't zap private pages for unsupported cases [v14,045/113] KVM: x86/tdp_mmu: Sprinkle __must_check [v14,046/113] KVM: x86/tdp_mmu: Support TDX private mapping for TDP MMU [v14,047/113,MARKER] The start of TDX KVM patch series: TDX EPT violation [v14,048/113] KVM: x86/mmu: TDX: Do not enable page track for TD guest [v14,049/113] KVM: VMX: Split out guts of EPT violation to common/exposed function [v14,050/113] KVM: VMX: Move setting of EPT MMU masks to common VT-x code [v14,051/113] KVM: TDX: Add accessors VMX VMCS helpers [v14,052/113] KVM: TDX: Add load_mmu_pgd method for TDX [v14,053/113] KVM: TDX: Retry seamcall when TDX_OPERAND_BUSY with operand SEPT [v14,054/113] KVM: TDX: Require TDP MMU and mmio caching for TDX [v14,055/113] KVM: TDX: TDP MMU TDX support [v14,056/113] KVM: TDX: MTRR: implement get_mt_mask() for TDX [v14,057/113,MARKER] The start of TDX KVM patch series: TD finalization [v14,058/113] KVM: x86/mmu: Introduce kvm_mmu_map_tdp_page() for use by TDX [v14,059/113] KVM: TDX: Create initial guest memory [v14,060/113] KVM: TDX: Finalize VM initialization [v14,061/113,MARKER] The start of TDX KVM patch series: TD vcpu enter/exit [v14,062/113] KVM: TDX: Add helper assembly function to TDX vcpu [v14,063/113] KVM: TDX: Implement TDX vcpu enter/exit path [v14,064/113] KVM: TDX: vcpu_run: save/restore host state(host kernel gs) [v14,065/113] KVM: TDX: restore host xsave state when exit from the guest TD [v14,066/113] KVM: x86: Allow to update cached values in kvm_user_return_msrs w/o wrmsr [v14,067/113] KVM: TDX: restore user ret MSRs [v14,068/113] KVM: TDX: Add TSX_CTRL msr into uret_msrs list [v14,069/113,MARKER] The start of TDX KVM patch series: TD vcpu exits/interrupts/hypercalls [v14,070/113] KVM: TDX: complete interrupts after tdexit [v14,071/113] KVM: TDX: restore debug store when TD exit [v14,072/113] KVM: TDX: handle vcpu migration over logical processor [v14,073/113] KVM: x86: Add a switch_db_regs flag to handle TDX's auto-switched behavior [v14,074/113] KVM: TDX: Add support for find pending IRQ in a protected local APIC [v14,075/113] KVM: x86: Assume timer IRQ was injected if APIC state is proteced [v14,076/113] KVM: TDX: remove use of struct vcpu_vmx from posted_interrupt.c [v14,077/113] KVM: TDX: Implement interrupt injection [v14,078/113] KVM: TDX: Implements vcpu request_immediate_exit [v14,079/113] KVM: TDX: Implement methods to inject NMI [v14,080/113] KVM: VMX: Modify NMI and INTR handlers to take intr_info as function argument [v14,081/113] KVM: VMX: Move NMI/exception handler to common helper [v14,082/113] KVM: x86: Split core of hypercall emulation to helper function [v14,083/113] KVM: TDX: Add a place holder to handle TDX VM exit [v14,084/113] KVM: TDX: Handle vmentry failure for INTEL TD guest [v14,085/113] KVM: TDX: handle EXIT_REASON_OTHER_SMI [v14,086/113] KVM: TDX: handle ept violation/misconfig exit [v14,087/113] KVM: TDX: handle EXCEPTION_NMI and EXTERNAL_INTERRUPT [v14,088/113] KVM: TDX: Add a place holder for handler of TDX hypercalls (TDG.VP.VMCALL) [v14,089/113] KVM: TDX: handle KVM hypercall with TDG.VP.VMCALL [v14,090/113] KVM: TDX: Add KVM Exit for TDX TDG.VP.VMCALL [v14,091/113] KVM: TDX: Handle TDX PV CPUID hypercall [v14,092/113] KVM: TDX: Handle TDX PV HLT hypercall [v14,093/113] KVM: TDX: Handle TDX PV port io hypercall [v14,094/113] KVM: TDX: Handle TDX PV MMIO hypercall [v14,095/113] KVM: TDX: Implement callbacks for MSR operations for TDX [v14,096/113] KVM: TDX: Handle TDX PV rdmsr/wrmsr hypercall [v14,097/113] KVM: TDX: Handle MSR MTRRCap and MTRRDefType access [v14,098/113] KVM: TDX: Handle TDG.VP.VMCALL<GetTdVmCallInfo> hypercall [v14,099/113] KVM: TDX: Silently discard SMI request [v14,100/113] KVM: TDX: Silently ignore INIT/SIPI [v14,101/113] KVM: TDX: Add methods to ignore accesses to CPU state [v14,102/113] KVM: TDX: Add methods to ignore guest instruction emulation [v14,103/113] KVM: TDX: Add a method to ignore dirty logging [v14,104/113] KVM: TDX: Add methods to ignore VMX preemption timer [v14,105/113] KVM: TDX: Add methods to ignore accesses to TSC [v14,106/113] KVM: TDX: Ignore setting up mce [v14,107/113] KVM: TDX: Add a method to ignore for TDX to ignore hypercall patch [v14,108/113] KVM: TDX: Add methods to ignore virtual apic related operation [v14,109/113] Documentation/virt/kvm: Document on Trust Domain Extensions(TDX) [v14,110/113] KVM: x86: design documentation on TDX support of x86 KVM TDP MMU [v14,111/113] RFC: KVM: x86, TDX: Add check for setting CPUID [v14,112/113] RFC: KVM: TDX: Make busy with S-EPT on entry bug [v14,113/113,MARKER] the end of (the first phase of) TDX KVM patch series

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index 14a599aadb58..37c1e23492b3 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -1375,6 +1375,9 @@ the memory region are automatically reflected into the guest. For example, an mmap() that affects the region will be made visible immediately. Another example is madvise(MADV_DROP). +For TDX guest, deleting/moving memory region loses guest memory contents. +Read only region isn't supported. Only as-id 0 is supported. + Note: On arm64, a write generated by the page-table walker (to update the Access and Dirty flags, for example) never results in a KVM_EXIT_MMIO exit when the slot has the KVM_MEM_READONLY flag. This @@ -4692,7 +4695,7 @@ H_GET_CPU_CHARACTERISTICS hypercall. :Capability: basic :Architectures: x86 -:Type: vm +:Type: vm ioctl, vcpu ioctl :Parameters: an opaque platform specific structure (in/out) :Returns: 0 on success; -1 on error @@ -4704,6 +4707,10 @@ Currently, this ioctl is used for issuing Secure Encrypted Virtualization (SEV) commands on AMD Processors. The SEV commands are defined in Documentation/virt/kvm/x86/amd-memory-encryption.rst. +Currently, this ioctl is used for issuing Trusted Domain Extensions +(TDX) commands on Intel Processors. The TDX commands are defined in +Documentation/virt/kvm/intel-tdx.rst. + 4.111 KVM_MEMORY_ENCRYPT_REG_REGION ----------------------------------- diff --git a/Documentation/virt/kvm/index.rst b/Documentation/virt/kvm/index.rst index 7f5f803fa87a..41d1e59a65be 100644 --- a/Documentation/virt/kvm/index.rst +++ b/Documentation/virt/kvm/index.rst @@ -20,4 +20,5 @@ KVM halt-polling review-checklist + intel-tdx intel-tdx-layer-status.rst diff --git a/Documentation/virt/kvm/intel-tdx.rst b/Documentation/virt/kvm/intel-tdx.rst new file mode 100644 index 000000000000..9a299923844d --- /dev/null +++ b/Documentation/virt/kvm/intel-tdx.rst @@ -0,0 +1,357 @@ +.. SPDX-License-Identifier: GPL-2.0 + +=================================== +Intel Trust Domain Extensions (TDX) +=================================== + +Overview +======== +TDX stands for Trust Domain Extensions which isolates VMs from +the virtual-machine manager (VMM)/hypervisor and any other software on +the platform. For details, see the specifications [1]_, whitepaper [2]_, +architectural extensions specification [3]_, module documentation [4]_, +loader interface specification [5]_, guest-hypervisor communication +interface [6]_, virtual firmware design guide [7]_, and other resources +([8]_, [9]_, [10]_, [11]_, and [12]_). + + +API description +=============== + +KVM_MEMORY_ENCRYPT_OP +--------------------- +:Type: vm ioctl, vcpu ioctl + +For TDX operations, KVM_MEMORY_ENCRYPT_OP is re-purposed to be generic +ioctl with TDX specific sub ioctl command. + +:: + + /* Trust Domain eXtension sub-ioctl() commands. */ + enum kvm_tdx_cmd_id { + KVM_TDX_CAPABILITIES = 0, + KVM_TDX_INIT_VM, + KVM_TDX_INIT_VCPU, + KVM_TDX_INIT_MEM_REGION, + KVM_TDX_FINALIZE_VM, + + 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. + * Defined for consistency with struct kvm_sev_cmd. + */ + __u64 error; + /* Reserved: Defined for consistency with struct kvm_sev_cmd. */ + __u64 unused; + }; + +KVM_TDX_CAPABILITIES +-------------------- +:Type: vm ioctl + +Subset of TDSYSINFO_STRCUCT retrieved by TDH.SYS.INFO TDX SEAM call will be +returned. Which describes about Intel TDX module. + +- id: KVM_TDX_CAPABILITIES +- flags: must be 0 +- data: pointer to struct kvm_tdx_capabilities +- error: must be 0 +- unused: must be 0 + +:: + + struct kvm_tdx_cpuid_config { + __u32 leaf; + __u32 sub_leaf; + __u32 eax; + __u32 ebx; + __u32 ecx; + __u32 edx; + }; + + struct kvm_tdx_capabilities { + __u64 attrs_fixed0; + __u64 attrs_fixed1; + __u64 xfam_fixed0; + __u64 xfam_fixed1; + + __u32 nr_cpuid_configs; + struct kvm_tdx_cpuid_config cpuid_configs[0]; + }; + + +KVM_TDX_INIT_VM +--------------- +:Type: vm ioctl + +Does additional VM initialization specific to TDX which corresponds to +TDH.MNG.INIT TDX SEAM call. + +- id: KVM_TDX_INIT_VM +- flags: must be 0 +- data: pointer to struct kvm_tdx_init_vm +- error: must be 0 +- unused: must be 0 + +:: + + struct kvm_tdx_init_vm { + __u64 attributes; + __u64 mrconfigid[6]; /* sha384 digest */ + __u64 mrowner[6]; /* sha384 digest */ + __u64 mrownerconfig[6]; /* sha348 digest */ + __u64 reserved[1004]; /* must be zero for future extensibility */ + + struct kvm_cpuid2 cpuid; + }; + + +KVM_TDX_INIT_VCPU +----------------- +:Type: vcpu ioctl + +Does additional VCPU initialization specific to TDX which corresponds to +TDH.VP.INIT TDX SEAM call. + +- id: KVM_TDX_INIT_VCPU +- flags: must be 0 +- data: initial value of the guest TD VCPU RCX +- error: must be 0 +- unused: must be 0 + +KVM_TDX_INIT_MEM_REGION +----------------------- +:Type: vm ioctl + +Encrypt a memory continuous region which corresponding to TDH.MEM.PAGE.ADD +TDX SEAM call. +If KVM_TDX_MEASURE_MEMORY_REGION flag is specified, it also extends measurement +which corresponds to TDH.MR.EXTEND TDX SEAM call. + +- id: KVM_TDX_INIT_VCPU +- flags: flags + currently only KVM_TDX_MEASURE_MEMORY_REGION is defined +- data: pointer to struct kvm_tdx_init_mem_region +- error: must be 0 +- unused: must be 0 + +:: + + #define KVM_TDX_MEASURE_MEMORY_REGION (1UL << 0) + + struct kvm_tdx_init_mem_region { + __u64 source_addr; + __u64 gpa; + __u64 nr_pages; + }; + + +KVM_TDX_FINALIZE_VM +------------------- +:Type: vm ioctl + +Complete measurement of the initial TD contents and mark it ready to run +which corresponds to TDH.MR.FINALIZE + +- id: KVM_TDX_FINALIZE_VM +- flags: must be 0 +- data: must be 0 +- error: must be 0 +- unused: must be 0 + +KVM TDX creation flow +===================== +In addition to KVM normal flow, new TDX ioctls need to be called. The control flow +looks like as follows. + +#. system wide capability check + + * KVM_CAP_VM_TYPES: check if VM type is supported and if KVM_X86_PROTECTED_VM + is supported. + +#. creating VM + + * KVM_CREATE_VM + * KVM_TDX_CAPABILITIES: query if TDX is supported on the platform. + * KVM_ENABLE_CAP_VM(KVM_CAP_MAX_VCPUS): set max_vcpus. KVM_MAX_VCPUS by + default. KVM_MAX_VCPUS is not a part of ABI, but kernel internal constant + that is subject to change. Because max vcpus is a part of attestation, max + vcpus should be explicitly set. + * KVM_SET_TSC_KHZ for vm. optional + * KVM_TDX_INIT_VM: pass TDX specific VM parameters. + +#. creating VCPU + + * KVM_CREATE_VCPU + * KVM_TDX_INIT_VCPU: pass TDX specific VCPU parameters. + * KVM_SET_CPUID2: Enable CPUID[0x1].ECX.X2APIC(bit 21)=1 so that the following + setting of MSR_IA32_APIC_BASE success. Without this, + KVM_SET_MSRS(MSR_IA32_APIC_BASE) fails. + * KVM_SET_MSRS: Set the initial reset value of MSR_IA32_APIC_BASE to + APIC_DEFAULT_ADDRESS(0xfee00000) | XAPIC_ENABLE(bit 10) | + X2APIC_ENABLE(bit 11) [| MSR_IA32_APICBASE_BSP(bit 8) optional] + +#. initializing guest memory + + * allocate guest memory and initialize page same to normal KVM case + In TDX case, parse and load TDVF into guest memory in addition. + * KVM_TDX_INIT_MEM_REGION to add and measure guest pages. + If the pages has contents above, those pages need to be added. + Otherwise the contents will be lost and guest sees zero pages. + * KVM_TDX_FINALIAZE_VM: Finalize VM and measurement + This must be after KVM_TDX_INIT_MEM_REGION. + +#. run vcpu + +Design discussion +================= + +Coexistence of normal(VMX) VM and TD VM +--------------------------------------- +It's required to allow both legacy(normal VMX) VMs and new TD VMs to +coexist. Otherwise the benefits of VM flexibility would be eliminated. +The main issue for it is that the logic of kvm_x86_ops callbacks for +TDX is different from VMX. On the other hand, the variable, +kvm_x86_ops, is global single variable. Not per-VM, not per-vcpu. + +Several points to be considered: + + * No or minimal overhead when TDX is disabled(CONFIG_INTEL_TDX_HOST=n). + * Avoid overhead of indirect call via function pointers. + * Contain the changes under arch/x86/kvm/vmx directory and share logic + with VMX for maintenance. + Even though the ways to operation on VM (VMX instruction vs TDX + SEAM call) are different, the basic idea remains the same. So, many + logic can be shared. + * Future maintenance + The huge change of kvm_x86_ops in (near) future isn't expected. + a centralized file is acceptable. + +- Wrapping kvm x86_ops: The current choice + + Introduce dedicated file for arch/x86/kvm/vmx/main.c (the name, + main.c, is just chosen to show main entry points for callbacks.) and + wrapper functions around all the callbacks with + "if (is-tdx) tdx-callback() else vmx-callback()". + + Pros: + + - No major change in common x86 KVM code. The change is (mostly) + contained under arch/x86/kvm/vmx/. + - When TDX is disabled(CONFIG_INTEL_TDX_HOST=n), the overhead is + optimized out. + - Micro optimization by avoiding function pointer. + + Cons: + + - Many boiler plates in arch/x86/kvm/vmx/main.c. + +KVM MMU Changes +--------------- +KVM MMU needs to be enhanced to handle Secure/Shared-EPT. The +high-level execution flow is mostly same to normal EPT case. +EPT violation/misconfiguration -> invoke TDP fault handler -> +resolve TDP fault -> resume execution. (or emulate MMIO) +The difference is, that S-EPT is operated(read/write) via TDX SEAM +call which is expensive instead of direct read/write EPT entry. +One bit of GPA (51 or 47 bit) is repurposed so that it means shared +with host(if set to 1) or private to TD(if cleared to 0). + +- The current implementation + + * Reuse the existing MMU code with minimal update. Because the + execution flow is mostly same. But additional operation, TDX call + for S-EPT, is needed. So add hooks for it to kvm_x86_ops. + * For performance, minimize TDX SEAM call to operate on S-EPT. When + getting corresponding S-EPT pages/entry from faulting GPA, don't + use TDX SEAM call to read S-EPT entry. Instead create shadow copy + in host memory. + Repurpose the existing kvm_mmu_page as shadow copy of S-EPT and + associate S-EPT to it. + * Treats share bit as attributes. mask/unmask the bit where + necessary to keep the existing traversing code works. + Introduce kvm.arch.gfn_shared_mask and use "if (gfn_share_mask)" + for special case. + + * 0 : for non-TDX case + * 51 or 47 bit set for TDX case. + + Pros: + + - Large code reuse with minimal new hooks. + - Execution path is same. + + Cons: + + - Complicates the existing code. + - Repurpose kvm_mmu_page as shadow of Secure-EPT can be confusing. + +New KVM API, ioctl (sub)command, to manage TD VMs +------------------------------------------------- +Additional KVM APIs are needed to control TD VMs. The operations on TD +VMs are specific to TDX. + +- Piggyback and repurpose KVM_MEMORY_ENCRYPT_OP + + Although operations for TD VMs aren't necessarily related to memory + encryption, define sub operations of KVM_MEMORY_ENCRYPT_OP for TDX specific + ioctls. + + Pros: + + - No major change in common x86 KVM code. + - Follows the SEV case. + + Cons: + + - The sub operations of KVM_MEMORY_ENCRYPT_OP aren't necessarily memory + encryption, but operations on TD VMs. + +References +========== + +.. [1] TDX specification + https://software.intel.com/content/www/us/en/develop/articles/intel-trust-domain-extensions.html +.. [2] Intel Trust Domain Extensions (Intel TDX) + https://software.intel.com/content/dam/develop/external/us/en/documents/tdx-whitepaper-final9-17.pdf +.. [3] Intel CPU Architectural Extensions Specification + https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-cpu-architectural-specification.pdf +.. [4] Intel TDX Module 1.0 EAS + https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-module-1eas.pdf +.. [5] Intel TDX Loader Interface Specification + https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-seamldr-interface-specification.pdf +.. [6] Intel TDX Guest-Hypervisor Communication Interface + https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-guest-hypervisor-communication-interface.pdf +.. [7] Intel TDX Virtual Firmware Design Guide + https://software.intel.com/content/dam/develop/external/us/en/documents/tdx-virtual-firmware-design-guide-rev-1. +.. [8] intel public github + + * kvm TDX branch: https://github.com/intel/tdx/tree/kvm + * TDX guest branch: https://github.com/intel/tdx/tree/guest + +.. [9] tdvf + https://github.com/tianocore/edk2-staging/tree/TDVF +.. [10] KVM forum 2020: Intel Virtualization Technology Extensions to + Enable Hardware Isolated VMs + https://osseu2020.sched.com/event/eDzm/intel-virtualization-technology-extensions-to-enable-hardware-isolated-vms-sean-christopherson-intel +.. [11] Linux Security Summit EU 2020: + Architectural Extensions for Hardware Virtual Machine Isolation + to Advance Confidential Computing in Public Clouds - Ravi Sahita + & Jun Nakajima, Intel Corporation + https://osseu2020.sched.com/event/eDOx/architectural-extensions-for-hardware-virtual-machine-isolation-to-advance-confidential-computing-in-public-clouds-ravi-sahita-jun-nakajima-intel-corporation +.. [12] [RFCv2,00/16] KVM protected memory extension + https://lkml.org/lkml/2020/10/20/66

[v14,109/113] Documentation/virt/kvm: Document on Trust Domain Extensions(TDX)

Commit Message

Patch