TDX KVM selftests
Subsystems (4)
v5 cover TDX KVM selftests
Hello,
This is v4 of the patch series for TDX selftests.
It has been updated for Intel’s v17 of the TDX host patches which was proposed here:
https://lore.kernel.org/all/[email protected]/
The tree can be found at:
https://github.com/googleprodkernel/linux-cc/tree/tdx-selftests-rfc-v5
Changes from RFC v4:
Added patch to propagate KVM_EXIT_MEMORY_FAULT to userspace.
Minor tweaks to align the tests to the new TDX 1.5 spec such as changes in the expected values in TDG.VP.INFO.
In RFCv5, TDX selftest code is organized into:
+ headers in tools/testing/selftests/kvm/include/x86_64/tdx/
+ common code in tools/testing/selftests/kvm/lib/x86_64/tdx/
+ selftests in tools/testing/selftests/kvm/x86_64/tdx_*
Dependencies
+ Peter’s patches, which provide functions for the host to allocate and track protected memory in the guest.
https://lore.kernel.org/all/[email protected]/
Further work for this patch series/TODOs
+ Sean’s comments for the non-confidential UPM selftests patch series at https://lore.kernel.org/lkml/[email protected]/T/#u apply here as well
+ Add ucall support for TDX selftests
I would also like to acknowledge the following people, who helped review or test patches in previous versions:
+ Sean Christopherson <[email protected]>
+ Zhenzhong Duan <[email protected]>
+ Peter Gonda <[email protected]>
+ Andrew Jones <[email protected]>
+ Maxim Levitsky <[email protected]>
+ Xiaoyao Li <[email protected]>
+ David Matlack <[email protected]>
+ Marc Orr <[email protected]>
+ Isaku Yamahata <[email protected]>
+ Maciej S. Szmigiero <[email protected]>
Links to earlier patch series
+ RFC v1: https://lore.kernel.org/lkml/[email protected]/T/#u
+ RFC v2: https://lore.kernel.org/lkml/[email protected]/T/#u
+ RFC v3: https://lore.kernel.org/lkml/[email protected]/T/#u
+ RFC v4: https://lore.kernel.org/lkml/[email protected]/
*** BLURB HERE ***
Ackerley Tng (12):
KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
KVM: selftests: Expose function that sets up sregs based on VM's mode
KVM: selftests: Store initial stack address in struct kvm_vcpu
KVM: selftests: Refactor steps in vCPU descriptor table initialization
KVM: selftests: TDX: Use KVM_TDX_CAPABILITIES to validate TDs'
attribute configuration
KVM: selftests: TDX: Update load_td_memory_region for VM memory backed
by guest memfd
KVM: selftests: Add functions to allow mapping as shared
KVM: selftests: Expose _vm_vaddr_alloc
KVM: selftests: TDX: Add support for TDG.MEM.PAGE.ACCEPT
KVM: selftests: TDX: Add support for TDG.VP.VEINFO.GET
KVM: selftests: TDX: Add TDX UPM selftest
KVM: selftests: TDX: Add TDX UPM selftests for implicit conversion
Erdem Aktas (3):
KVM: selftests: Add helper functions to create TDX VMs
KVM: selftests: TDX: Add TDX lifecycle test
KVM: selftests: TDX: Adding test case for TDX port IO
Roger Wang (1):
KVM: selftests: TDX: Add TDG.VP.INFO test
Ryan Afranji (2):
KVM: selftests: TDX: Verify the behavior when host consumes a TD
private memory
KVM: selftests: TDX: Add shared memory test
Sagi Shahar (11):
KVM: selftests: TDX: Add report_fatal_error test
KVM: selftests: TDX: Add basic TDX CPUID test
KVM: selftests: TDX: Add basic get_td_vmcall_info test
KVM: selftests: TDX: Add TDX IO writes test
KVM: selftests: TDX: Add TDX IO reads test
KVM: selftests: TDX: Add TDX MSR read/write tests
KVM: selftests: TDX: Add TDX HLT exit test
KVM: selftests: TDX: Add TDX MMIO reads test
KVM: selftests: TDX: Add TDX MMIO writes test
KVM: selftests: TDX: Add TDX CPUID TDVMCALL test
KVM: selftests: Propagate KVM_EXIT_MEMORY_FAULT to userspace
tools/testing/selftests/kvm/Makefile | 8 + .../selftests/kvm/include/kvm_util_base.h | 30 + .../selftests/kvm/include/x86_64/processor.h | 4 + .../kvm/include/x86_64/tdx/td_boot.h | 82 + .../kvm/include/x86_64/tdx/td_boot_asm.h | 16 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 59 + .../selftests/kvm/include/x86_64/tdx/tdx.h | 65 + .../kvm/include/x86_64/tdx/tdx_util.h | 19 + .../kvm/include/x86_64/tdx/test_util.h | 164 ++ tools/testing/selftests/kvm/lib/kvm_util.c | 101 +- .../selftests/kvm/lib/x86_64/processor.c | 77 +- .../selftests/kvm/lib/x86_64/tdx/td_boot.S | 101 ++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 158 ++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 262 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 558 +++++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 101 ++ .../kvm/x86_64/tdx_shared_mem_test.c | 135 ++ .../selftests/kvm/x86_64/tdx_upm_test.c | 469 ++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 1319 +++++++++++++++++ 19 files changed, 3693 insertions(+), 35 deletions(-) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_upm_test.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c
Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 1/29 KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
From: Ackerley Tng <[email protected]>
One-to-one GVA to GPA mappings can be used in the guest to set up boot sequences during which paging is enabled, hence requiring a transition from using physical to virtual addresses in consecutive instructions.
--- .../selftests/kvm/include/kvm_util_base.h | 2 + tools/testing/selftests/kvm/lib/kvm_util.c | 63 ++++++++++++++++--- 2 files changed, 55 insertions(+), 10 deletions(-)
tools/testing/selftests/kvm/include/kvm_util_base.h +2 -0
@@ -564,6 +564,8 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot);vm_vaddr_t vm_vaddr_alloc_pages (struct kvm_vm *vm,int nr_pages);vm_vaddr_t __vm_vaddr_alloc_page (struct kvm_vm *vm,enum kvm_mem_region_type type);
tools/testing/selftests/kvm/lib/kvm_util.c +53 -10
96 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 01/29] KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
Quoted 114 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
One-to-one GVA to GPA mappings can be used in the guest to set up boot sequences during which paging is enabled, hence requiring a transition from using physical to virtual addresses in consecutive instructions.
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 2 + tools/testing/selftests/kvm/lib/kvm_util.c | 63 ++++++++++++++++--- 2 files changed, 55 insertions(+), 10 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +2
-0@@ -564,6 +564,8 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot);vm_vaddr_t vm_vaddr_alloc_pages (struct kvm_vm *vm,int nr_pages);vm_vaddr_t __vm_vaddr_alloc_page (struct kvm_vm *vm,enum kvm_mem_region_type type);tools/testing/selftests/kvm/lib/kvm_util.c +39
-10@@ -1388,17 +1388,37 @@ vm_vaddr_t vm_vaddr_unused_gap(struct kvm_vm *vm, size_t sz,return pgidx_start * vm->page_size; } +/* +* VM Virtual Address Allocate Shared/Encrypted +* +* Input Args: +* vm - Virtual Machine +* sz - Size in bytes +* vaddr_min - Minimum starting virtual address +* paddr_min - Minimum starting physical address +* data_memslot - memslot number to allocate in +* encrypt - Whether the region should be handled as encrypted +* +* Output Args: None +* +* Return: +* Starting guest virtual address +* +* Allocates at least sz bytes within the virtual address space of the vm +* given by vm. The allocated bytes are mapped to a virtual address >= +* the address given by vaddr_min. Note that each allocation uses a +* a unique set of pages, with the minimum real allocation being at least +* a page. +*/ static vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, -vm_vaddr_t vaddr_min, -enum kvm_mem_region_type type, -bool encrypt) +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt) {uint64_t pages = (sz >> vm->page_shift) + ((sz % vm->page_size) !=0 );virt_pgd_alloc (vm); -vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, -KVM_UTIL_MIN_PFN * vm->page_size, - vm->memslots[type], encrypt); +vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, paddr_min, + data_memslot, encrypt);/* * Find an unused range of virtual page addresses of at least @@ -1408,8 +1428,7 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,/* Map the virtual pages. */ for (vm_vaddr_t vaddr = vaddr_start; pages >0 ; - pages--, vaddr += vm->page_size, paddr += vm->page_size) { - + pages--, vaddr += vm->page_size, paddr += vm->page_size) {virt_pg_map (vm, vaddr, paddr);sparsebit_set (vm->vpages_mapped, vaddr >> vm->page_shift);@@ -1421,12 +1440,16 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min, type, vm->protected); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[type], vm->protected); }vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA , false); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[MEM_REGION_TEST_DATA ], false); }/* @@ -1453,6 +1476,26 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min)return __vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA ); } +/** +* Allocate memory in @vm of size @sz in memslot with id @data_memslot, +* beginning with the desired address of @vaddr_min. +* +* If there isn't enough memory at @vaddr_min, find the next possible address +* that can meet the requested size in the given memslot.
tools/testing/selftests/kvm/lib/kvm_util.c vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min) · line 1494
Quoted 10 lines
tools/testing/selftests/kvm/lib/kvm_util.c +10
-0+* +* Return the address where the memory is allocated. +*/ +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot) +{ +vm_vaddr_t gva =____vm_vaddr_alloc (vm, sz, vaddr_min, + (vm_paddr_t )vaddr_min, data_memslot, + vm->protected); +TEST_ASSERT_EQ (gva,addr_gva2gpa (vm, gva));
How can this be guaranteed?
For ____vm_vaddr_alloc(), generically there is no enforcement about the identity of virtual and physical address.
Quoted 7 lines
tools/testing/selftests/kvm/lib/kvm_util.c +4
-0+ +return gva; +} +/* * VM Virtual Address Allocate Pages *
Re: [RFC PATCH v5 01/29] KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
Quoted 124 lines · Binbin Wu
Quoted 120 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
One-to-one GVA to GPA mappings can be used in the guest to set up boot sequences during which paging is enabled, hence requiring a transition from using physical to virtual addresses in consecutive instructions.
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 2 + tools/testing/selftests/kvm/lib/kvm_util.c | 63 ++++++++++++++++--- 2 files changed, 55 insertions(+), 10 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +2
-0@@ -564,6 +564,8 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot);vm_vaddr_t vm_vaddr_alloc_pages (struct kvm_vm *vm,int nr_pages);vm_vaddr_t __vm_vaddr_alloc_page (struct kvm_vm *vm,enum kvm_mem_region_type type);tools/testing/selftests/kvm/lib/kvm_util.c +45
-10@@ -1388,17 +1388,37 @@ vm_vaddr_t vm_vaddr_unused_gap(struct kvm_vm *vm, size_t sz,return pgidx_start * vm->page_size; } +/* +* VM Virtual Address Allocate Shared/Encrypted +* +* Input Args: +* vm - Virtual Machine +* sz - Size in bytes +* vaddr_min - Minimum starting virtual address +* paddr_min - Minimum starting physical address +* data_memslot - memslot number to allocate in +* encrypt - Whether the region should be handled as encrypted +* +* Output Args: None +* +* Return: +* Starting guest virtual address +* +* Allocates at least sz bytes within the virtual address space of the vm +* given by vm. The allocated bytes are mapped to a virtual address >= +* the address given by vaddr_min. Note that each allocation uses a +* a unique set of pages, with the minimum real allocation being at least +* a page. +*/ static vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, -vm_vaddr_t vaddr_min, -enum kvm_mem_region_type type, -bool encrypt) +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt) {uint64_t pages = (sz >> vm->page_shift) + ((sz % vm->page_size) !=0 );virt_pgd_alloc (vm); -vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, -KVM_UTIL_MIN_PFN * vm->page_size, - vm->memslots[type], encrypt); +vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, paddr_min, + data_memslot, encrypt);/* * Find an unused range of virtual page addresses of at least @@ -1408,8 +1428,7 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,/* Map the virtual pages. */ for (vm_vaddr_t vaddr = vaddr_start; pages >0 ; - pages--, vaddr += vm->page_size, paddr += vm->page_size) { - + pages--, vaddr += vm->page_size, paddr += vm->page_size) {virt_pg_map (vm, vaddr, paddr);sparsebit_set (vm->vpages_mapped, vaddr >> vm->page_shift);@@ -1421,12 +1440,16 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min, type, vm->protected); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[type], vm->protected); }vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA , false); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[MEM_REGION_TEST_DATA ], false); }/* @@ -1453,6 +1476,26 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min)return __vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA ); } +/** +* Allocate memory in @vm of size @sz in memslot with id @data_memslot, +* beginning with the desired address of @vaddr_min. +* +* If there isn't enough memory at @vaddr_min, find the next possible address +* that can meet the requested size in the given memslot. +* +* Return the address where the memory is allocated. +*/ +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot) +{
Quoted 8 lines
tools/testing/selftests/kvm/lib/kvm_util.c vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min) · line 1494
Quoted 4 lines
tools/testing/selftests/kvm/lib/kvm_util.c +4
-0+vm_vaddr_t gva =____vm_vaddr_alloc (vm, sz, vaddr_min, + (vm_paddr_t )vaddr_min, data_memslot, + vm->protected); +TEST_ASSERT_EQ (gva,addr_gva2gpa (vm, gva));How can this be guaranteed?
For____vm_vaddr_alloc(), generically there is no enforcement about the identity of virtual and physical address.
The problem is that if the allocation won't be 1-to-1 the tests won't work. So we figured it's better to fail early.
The way this is used in practice generally guarantees that the mapping can be 1-to-1 since we create these mappings at an early stage.
Quoted 10 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/kvm_util.c +4
-0+ +return gva; +} +/* * VM Virtual Address Allocate Pages *
Re: [RFC PATCH v5 01/29] KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
In reply to Sagi ShaharQuoted 114 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
One-to-one GVA to GPA mappings can be used in the guest to set up boot sequences during which paging is enabled, hence requiring a transition from using physical to virtual addresses in consecutive instructions.
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 2 + tools/testing/selftests/kvm/lib/kvm_util.c | 63 ++++++++++++++++--- 2 files changed, 55 insertions(+), 10 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +2
-0@@ -564,6 +564,8 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot);vm_vaddr_t vm_vaddr_alloc_pages (struct kvm_vm *vm,int nr_pages);vm_vaddr_t __vm_vaddr_alloc_page (struct kvm_vm *vm,enum kvm_mem_region_type type);tools/testing/selftests/kvm/lib/kvm_util.c +39
-10@@ -1388,17 +1388,37 @@ vm_vaddr_t vm_vaddr_unused_gap(struct kvm_vm *vm, size_t sz,return pgidx_start * vm->page_size; } +/* +* VM Virtual Address Allocate Shared/Encrypted +* +* Input Args: +* vm - Virtual Machine +* sz - Size in bytes +* vaddr_min - Minimum starting virtual address +* paddr_min - Minimum starting physical address +* data_memslot - memslot number to allocate in +* encrypt - Whether the region should be handled as encrypted +* +* Output Args: None +* +* Return: +* Starting guest virtual address +* +* Allocates at least sz bytes within the virtual address space of the vm +* given by vm. The allocated bytes are mapped to a virtual address >= +* the address given by vaddr_min. Note that each allocation uses a +* a unique set of pages, with the minimum real allocation being at least +* a page. +*/ static vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, -vm_vaddr_t vaddr_min, -enum kvm_mem_region_type type, -bool encrypt) +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt) {uint64_t pages = (sz >> vm->page_shift) + ((sz % vm->page_size) !=0 );virt_pgd_alloc (vm); -vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, -KVM_UTIL_MIN_PFN * vm->page_size, - vm->memslots[type], encrypt); +vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, paddr_min, + data_memslot, encrypt);/* * Find an unused range of virtual page addresses of at least @@ -1408,8 +1428,7 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,/* Map the virtual pages. */ for (vm_vaddr_t vaddr = vaddr_start; pages >0 ; - pages--, vaddr += vm->page_size, paddr += vm->page_size) { - + pages--, vaddr += vm->page_size, paddr += vm->page_size) {virt_pg_map (vm, vaddr, paddr);sparsebit_set (vm->vpages_mapped, vaddr >> vm->page_shift);@@ -1421,12 +1440,16 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min, type, vm->protected); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[type], vm->protected); }vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA , false); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[MEM_REGION_TEST_DATA ], false); }/* @@ -1453,6 +1476,26 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min)return __vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA ); } +/** +* Allocate memory in @vm of size @sz in memslot with id @data_memslot, +* beginning with the desired address of @vaddr_min. +* +* If there isn't enough memory at @vaddr_min, find the next possible address +* that can meet the requested size in the given memslot.
tools/testing/selftests/kvm/lib/kvm_util.c vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min) · line 1494
Quoted 10 lines
tools/testing/selftests/kvm/lib/kvm_util.c +10
-0+* +* Return the address where the memory is allocated. +*/ +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot) +{ +vm_vaddr_t gva =____vm_vaddr_alloc (vm, sz, vaddr_min, + (vm_paddr_t )vaddr_min, data_memslot, + vm->protected); +TEST_ASSERT_EQ (gva,addr_gva2gpa (vm, gva));
By 1to1, do you mean virtual address=physical address?, community tends to call this identity mapping. Examples (function name):create_identity_mapping_pagetables()hellcreek_setup_tc_identity_mapping()identity_mapping_add()
Quoted 7 lines
tools/testing/selftests/kvm/lib/kvm_util.c +4
-0+ +return gva; +} +/* * VM Virtual Address Allocate Pages *
Re: [RFC PATCH v5 01/29] KVM: selftests: Add function to allow one-to-one GVA to GPA mappings
Quoted 126 lines · Dongsheng X
Quoted 122 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
One-to-one GVA to GPA mappings can be used in the guest to set up boot sequences during which paging is enabled, hence requiring a transition from using physical to virtual addresses in consecutive instructions.
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 2 + tools/testing/selftests/kvm/lib/kvm_util.c | 63 ++++++++++++++++--- 2 files changed, 55 insertions(+), 10 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +2
-0@@ -564,6 +564,8 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot);vm_vaddr_t vm_vaddr_alloc_pages (struct kvm_vm *vm,int nr_pages);vm_vaddr_t __vm_vaddr_alloc_page (struct kvm_vm *vm,enum kvm_mem_region_type type);tools/testing/selftests/kvm/lib/kvm_util.c +47
-10@@ -1388,17 +1388,37 @@ vm_vaddr_t vm_vaddr_unused_gap(struct kvm_vm *vm, size_t sz,return pgidx_start * vm->page_size; } +/* +* VM Virtual Address Allocate Shared/Encrypted +* +* Input Args: +* vm - Virtual Machine +* sz - Size in bytes +* vaddr_min - Minimum starting virtual address +* paddr_min - Minimum starting physical address +* data_memslot - memslot number to allocate in +* encrypt - Whether the region should be handled as encrypted +* +* Output Args: None +* +* Return: +* Starting guest virtual address +* +* Allocates at least sz bytes within the virtual address space of the vm +* given by vm. The allocated bytes are mapped to a virtual address >= +* the address given by vaddr_min. Note that each allocation uses a +* a unique set of pages, with the minimum real allocation being at least +* a page. +*/ static vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, -vm_vaddr_t vaddr_min, -enum kvm_mem_region_type type, -bool encrypt) +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt) {uint64_t pages = (sz >> vm->page_shift) + ((sz % vm->page_size) !=0 );virt_pgd_alloc (vm); -vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, -KVM_UTIL_MIN_PFN * vm->page_size, - vm->memslots[type], encrypt); +vm_paddr_t paddr =_vm_phy_pages_alloc (vm, pages, paddr_min, + data_memslot, encrypt);/* * Find an unused range of virtual page addresses of at least @@ -1408,8 +1428,7 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,/* Map the virtual pages. */ for (vm_vaddr_t vaddr = vaddr_start; pages >0 ; - pages--, vaddr += vm->page_size, paddr += vm->page_size) { - + pages--, vaddr += vm->page_size, paddr += vm->page_size) {virt_pg_map (vm, vaddr, paddr);sparsebit_set (vm->vpages_mapped, vaddr >> vm->page_shift);@@ -1421,12 +1440,16 @@ static vm_vaddr_t ____vm_vaddr_alloc(struct kvm_vm *vm, size_t sz,vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min, type, vm->protected); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[type], vm->protected); }vm_vaddr_t vm_vaddr_alloc_shared (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min) { -return ____vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA , false); +return ____vm_vaddr_alloc (vm, sz, vaddr_min, +KVM_UTIL_MIN_PFN * vm->page_size, + vm->memslots[MEM_REGION_TEST_DATA ], false); }/* @@ -1453,6 +1476,26 @@ vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min)return __vm_vaddr_alloc (vm, sz, vaddr_min,MEM_REGION_TEST_DATA ); } +/** +* Allocate memory in @vm of size @sz in memslot with id @data_memslot, +* beginning with the desired address of @vaddr_min. +* +* If there isn't enough memory at @vaddr_min, find the next possible address +* that can meet the requested size in the given memslot. +* +* Return the address where the memory is allocated. +*/ +vm_vaddr_t vm_vaddr_alloc_1to1 (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,uint32_t data_memslot) +{ + vm_vaddr_t gva = ____vm_vaddr_alloc(vm, sz, vaddr_min, + (vm_paddr_t)vaddr_min, data_memslot,
Quoted 8 lines
tools/testing/selftests/kvm/lib/kvm_util.c vm_vaddr_t vm_vaddr_alloc(struct kvm_vm *vm, size_t sz, vm_vaddr_t vaddr_min) · line 1494
Quoted 2 lines
tools/testing/selftests/kvm/lib/kvm_util.c +2
-0+ vm->protected); +TEST_ASSERT_EQ (gva,addr_gva2gpa (vm, gva));By 1to1, do you mean virtual address=physical address?, community tends to call this identity mapping. Examples (function name):
create_identity_mapping_pagetables()hellcreek_setup_tc_identity_mapping()identity_mapping_add()
Thanks for the input. Will switch to vm_vaddr_identity_alloc()
Quoted 9 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/kvm_util.c +4
-0+ +return gva; +} +/* * VM Virtual Address Allocate Pages *
RFC PATCH v5 2/29 KVM: selftests: Expose function that sets up sregs based on VM's mode
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
This allows initializing sregs without setting vCPU registers in KVM.
No functional change intended.
--- .../selftests/kvm/include/x86_64/processor.h | 2 + .../selftests/kvm/lib/x86_64/processor.c | 39 ++++++++++--------- 2 files changed, 23 insertions(+), 18 deletions(-)
tools/testing/selftests/kvm/include/x86_64/processor.h +2 -0
@@ -958,6 +958,8 @@ static inline struct kvm_cpuid2 *allocate_kvm_cpuid2(int nr_entries)void vcpu_init_cpuid (struct kvm_vcpu *vcpu,const struct kvm_cpuid2 *cpuid);void vcpu_set_hv_cpuid (struct kvm_vcpu *vcpu); +void vcpu_setup_mode_sregs (struct kvm_vm *vm,struct kvm_sregs *sregs); +static inline struct kvm_cpuid_entry2 *__vcpu_get_cpuid_entry (struct kvm_vcpu *vcpu,uint32_t function,uint32_t index)
tools/testing/selftests/kvm/lib/x86_64/processor.c +21 -18
@@ -543,36 +543,39 @@ static void kvm_setup_tss_64bit(struct kvm_vm *vm, struct kvm_segment *segp,kvm_seg_fill_gdt_64bit (vm, segp); } -static void vcpu_setup (struct kvm_vm *vm,struct kvm_vcpu *vcpu) +void vcpu_setup_mode_sregs (struct kvm_vm *vm,struct kvm_sregs *sregs) { -struct kvm_sregs sregs; - -/* Set mode specific system register values. */ -vcpu_sregs_get (vcpu, &sregs); - - sregs.idt.limit =0 ; + sregs->idt.limit =0 ; -kvm_setup_gdt (vm, &sregs.gdt); +kvm_setup_gdt (vm, &sregs->gdt);switch (vm->mode) {case VM_MODE_PXXV48_4K_SEV :case VM_MODE_PXXV48_4K : - sregs.cr0 =X86_CR0_PE |X86_CR0_NE |X86_CR0_PG ; - sregs.cr4 |=X86_CR4_PAE |X86_CR4_OSFXSR ; - sregs.efer |= (EFER_LME |EFER_LMA |EFER_NX ); - -kvm_seg_set_unusable (&sregs.ldt); -kvm_seg_set_kernel_code_64bit (vm,DEFAULT_CODE_SELECTOR , &sregs.cs); -kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs.ds); -kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs.es); -kvm_setup_tss_64bit (vm, &sregs.tr,0x18 ); + sregs->cr0 =X86_CR0_PE |X86_CR0_NE |X86_CR0_PG ; + sregs->cr4 |=X86_CR4_PAE |X86_CR4_OSFXSR ; + sregs->efer |= (EFER_LME |EFER_LMA |EFER_NX ); + +kvm_seg_set_unusable (&sregs->ldt); +kvm_seg_set_kernel_code_64bit (vm,DEFAULT_CODE_SELECTOR , &sregs->cs); +kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs->ds); +kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs->es); +kvm_setup_tss_64bit (vm, &sregs->tr,0x18 );break ;default :TEST_FAIL ("Unknown guest mode, mode: 0x%x" , vm->mode); } - sregs.cr3 = vm->pgd; + sregs->cr3 = vm->pgd; +} + +static void vcpu_setup (struct kvm_vm *vm,struct kvm_vcpu *vcpu) +{ +struct kvm_sregs sregs; + +vcpu_sregs_get (vcpu, &sregs); +vcpu_setup_mode_sregs (vm, &sregs);vcpu_sregs_set (vcpu, &sregs); }
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 02/29] KVM: selftests: Expose function that sets up sregs based on VM's mode
Quoted 6 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
This allows initializing sregs without setting vCPU registers in KVM.
No functional change intended.
Quoted 84 lines
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/x86_64/processor.h | 2 + .../selftests/kvm/lib/x86_64/processor.c | 39 ++++++++++--------- 2 files changed, 23 insertions(+), 18 deletions(-)tools/testing/selftests/kvm/include/x86_64/processor.h +2
-0@@ -958,6 +958,8 @@ static inline struct kvm_cpuid2 *allocate_kvm_cpuid2(int nr_entries)void vcpu_init_cpuid (struct kvm_vcpu *vcpu,const struct kvm_cpuid2 *cpuid);void vcpu_set_hv_cpuid (struct kvm_vcpu *vcpu); +void vcpu_setup_mode_sregs (struct kvm_vm *vm,struct kvm_sregs *sregs); +static inline struct kvm_cpuid_entry2 *__vcpu_get_cpuid_entry (struct kvm_vcpu *vcpu,uint32_t function,uint32_t index)tools/testing/selftests/kvm/lib/x86_64/processor.c +21
-18@@ -543,36 +543,39 @@ static void kvm_setup_tss_64bit(struct kvm_vm *vm, struct kvm_segment *segp,kvm_seg_fill_gdt_64bit (vm, segp); } -static void vcpu_setup (struct kvm_vm *vm,struct kvm_vcpu *vcpu) +void vcpu_setup_mode_sregs (struct kvm_vm *vm,struct kvm_sregs *sregs) { -struct kvm_sregs sregs; - -/* Set mode specific system register values. */ -vcpu_sregs_get (vcpu, &sregs); - - sregs.idt.limit =0 ; + sregs->idt.limit =0 ; -kvm_setup_gdt (vm, &sregs.gdt); +kvm_setup_gdt (vm, &sregs->gdt);switch (vm->mode) {case VM_MODE_PXXV48_4K_SEV :case VM_MODE_PXXV48_4K : - sregs.cr0 =X86_CR0_PE |X86_CR0_NE |X86_CR0_PG ; - sregs.cr4 |=X86_CR4_PAE |X86_CR4_OSFXSR ; - sregs.efer |= (EFER_LME |EFER_LMA |EFER_NX ); - -kvm_seg_set_unusable (&sregs.ldt); -kvm_seg_set_kernel_code_64bit (vm,DEFAULT_CODE_SELECTOR , &sregs.cs); -kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs.ds); -kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs.es); -kvm_setup_tss_64bit (vm, &sregs.tr,0x18 ); + sregs->cr0 =X86_CR0_PE |X86_CR0_NE |X86_CR0_PG ; + sregs->cr4 |=X86_CR4_PAE |X86_CR4_OSFXSR ; + sregs->efer |= (EFER_LME |EFER_LMA |EFER_NX ); + +kvm_seg_set_unusable (&sregs->ldt); +kvm_seg_set_kernel_code_64bit (vm,DEFAULT_CODE_SELECTOR , &sregs->cs); +kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs->ds); +kvm_seg_set_kernel_data_64bit (vm,DEFAULT_DATA_SELECTOR , &sregs->es); +kvm_setup_tss_64bit (vm, &sregs->tr,0x18 );break ;default :TEST_FAIL ("Unknown guest mode, mode: 0x%x" , vm->mode); } - sregs.cr3 = vm->pgd; + sregs->cr3 = vm->pgd; +} + +static void vcpu_setup (struct kvm_vm *vm,struct kvm_vcpu *vcpu) +{ +struct kvm_sregs sregs; + +vcpu_sregs_get (vcpu, &sregs); +vcpu_setup_mode_sregs (vm, &sregs);vcpu_sregs_set (vcpu, &sregs); }
RFC PATCH v5 3/29 KVM: selftests: Store initial stack address in struct kvm_vcpu
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
TDX guests' registers cannot be initialized directly using vcpu_regs_set(), hence the stack pointer needs to be initialized by the guest itself, running boot code beginning at the reset vector.
We store the stack address as part of struct kvm_vcpu so that it can be accessible later to be passed to the boot code for rsp initialization.
--- tools/testing/selftests/kvm/include/kvm_util_base.h | 1 + tools/testing/selftests/kvm/lib/x86_64/processor.c | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/include/kvm_util_base.h +1 -0
@@ -68,6 +68,7 @@ struct kvm_vcpu {int fd;struct kvm_vm *vm;struct kvm_run *run; +vm_vaddr_t initial_stack_addr;#ifdef __x86_64__struct kvm_cpuid2 *cpuid;#endif
tools/testing/selftests/kvm/lib/x86_64/processor.c +3 -1
@@ -621,10 +621,12 @@ struct kvm_vcpu *vm_arch_vcpu_add(struct kvm_vm *vm, uint32_t vcpu_id,vcpu_init_cpuid (vcpu,kvm_get_supported_cpuid ());vcpu_setup (vm, vcpu); + vcpu->initial_stack_addr = stack_vaddr; +/* Setup guest general purpose registers */ vcpu_regs_get (vcpu, ®s); regs.rflags = regs.rflags |0x2 ; - regs.rsp = stack_vaddr; + regs.rsp = vcpu->initial_stack_addr; regs.rip = (unsigned long ) guest_code;vcpu_regs_set (vcpu, ®s);
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 03/29] KVM: selftests: Store initial stack address in struct kvm_vcpu
Quoted 35 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
TDX guests' registers cannot be initialized directly using
vcpu_regs_set(), hence the stack pointer needs to be initialized by the guest itself, running boot code beginning at the reset vector.We store the stack address as part of struct
kvm_vcpuso that it can be accessible later to be passed to the boot code for rsp initialization.Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- tools/testing/selftests/kvm/include/kvm_util_base.h | 1 + tools/testing/selftests/kvm/lib/x86_64/processor.c | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/kvm_util_base.h +1
-0@@ -68,6 +68,7 @@ struct kvm_vcpu {int fd;struct kvm_vm *vm;struct kvm_run *run; +vm_vaddr_t initial_stack_addr;#ifdef __x86_64__struct kvm_cpuid2 *cpuid;#endif tools/testing/selftests/kvm/lib/x86_64/processor.c +0
-0
tools/testing/selftests/kvm/lib/x86_64/processor.c struct kvm_vcpu *vm_arch_vcpu_add(struct kvm_vm *vm, uint32_t vcpu_id, · line 629
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +3
-1@@ -621,10 +621,12 @@ struct kvm_vcpu *vm_arch_vcpu_add(struct kvm_vm *vm, uint32_t vcpu_id,vcpu_init_cpuid (vcpu,kvm_get_supported_cpuid ());vcpu_setup (vm, vcpu); + vcpu->initial_stack_addr = stack_vaddr; +/* Setup guest general purpose registers */ vcpu_regs_get (vcpu, ®s); regs.rflags = regs.rflags |0x2 ; - regs.rsp = stack_vaddr; + regs.rsp = vcpu->initial_stack_addr;
Nit: No need to do this change.
Quoted 3 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +0
-0regs.rip = (unsigned long ) guest_code;vcpu_regs_set (vcpu, ®s);
RFC PATCH v5 4/29 KVM: selftests: Refactor steps in vCPU descriptor table initialization
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
Split the vCPU descriptor table initialization process into a few steps and expose them:
+ Setting up the IDT
+ Syncing exception handlers into the guest
In kvm_setup_idt(), we conditionally allocate guest memory for vm->idt to avoid double allocation when kvm_setup_idt() is used after vm_init_descriptor_tables().
--- .../selftests/kvm/include/x86_64/processor.h | 2 ++ .../selftests/kvm/lib/x86_64/processor.c | 19 ++++++++++++++++--- 2 files changed, 18 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/include/x86_64/processor.h +2 -0
@@ -1089,6 +1089,8 @@ struct idt_entry {uint32_t offset2;uint32_t reserved; }; +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt); +void sync_exception_handlers_to_guest (struct kvm_vm *vm);void vm_init_descriptor_tables (struct kvm_vm *vm);void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu); void vm_install_exception_handler(struct kvm_vm *vm, int vector,
tools/testing/selftests/kvm/lib/x86_64/processor.c +16 -3
@@ -1155,19 +1155,32 @@ void vm_init_descriptor_tables(struct kvm_vm *vm) DEFAULT_CODE_SELECTOR); } +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt) +{ +if (!vm->idt) + vm->idt =vm_vaddr_alloc_page (vm); + + dt->base = vm->idt; + dt->limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +} + +void sync_exception_handlers_to_guest (struct kvm_vm *vm) +{ + *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +} +void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu) {struct kvm_vm *vm = vcpu->vm;struct kvm_sregs sregs;vcpu_sregs_get (vcpu, &sregs); - sregs.idt.base = vm->idt; - sregs.idt.limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +kvm_setup_idt (vcpu->vm, &sregs.idt); sregs.gdt.base = vm->gdt; sregs.gdt.limit =getpagesize () -1 ;kvm_seg_set_kernel_data_64bit (NULL ,DEFAULT_DATA_SELECTOR , &sregs.gs);vcpu_sregs_set (vcpu, &sregs); - *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +sync_exception_handlers_to_guest (vm); } void vm_install_exception_handler(struct kvm_vm *vm, int vector,
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 04/29] KVM: selftests: Refactor steps in vCPU descriptor table initialization
Quoted 38 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
Split the vCPU descriptor table initialization process into a few steps and expose them:
+ Setting up the IDT
+ Syncing exception handlers into the guestIn
kvm_setup_idt(), we conditionally allocate guest memory forvm->idtto avoid double allocation whenkvm_setup_idt()is used aftervm_init_descriptor_tables().Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/x86_64/processor.h | 2 ++ .../selftests/kvm/lib/x86_64/processor.c | 19 ++++++++++++++++--- 2 files changed, 18 insertions(+), 3 deletions(-)tools/testing/selftests/kvm/include/x86_64/processor.h +2
-0@@ -1089,6 +1089,8 @@ struct idt_entry {uint32_t offset2;uint32_t reserved; }; +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt); +void sync_exception_handlers_to_guest (struct kvm_vm *vm);void vm_init_descriptor_tables (struct kvm_vm *vm);void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu); void vm_install_exception_handler(struct kvm_vm *vm, int vector,tools/testing/selftests/kvm/lib/x86_64/processor.c +0
-0
tools/testing/selftests/kvm/lib/x86_64/processor.c void vm_init_descriptor_tables(struct kvm_vm *vm) · line 1161
Quoted 7 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +4
-0@@ -1155,19 +1155,32 @@ void vm_init_descriptor_tables(struct kvm_vm *vm) DEFAULT_CODE_SELECTOR); } +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt) +{ +if (!vm->idt) + vm->idt =vm_vaddr_alloc_page (vm);
IDT is allocated in DATA memslot in current code, but here, when using vm_vaddr_alloc_page(), it will be allocated in TEST_DATA memslot.
Do we need to follow the current code to use __vm_vaddr_alloc_page(vm, MEM_REGION_DATA) instead?
Quoted 28 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +12
-3+ + dt->base = vm->idt; + dt->limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +} + +void sync_exception_handlers_to_guest (struct kvm_vm *vm) +{ + *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +} +void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu) {struct kvm_vm *vm = vcpu->vm;struct kvm_sregs sregs;vcpu_sregs_get (vcpu, &sregs); - sregs.idt.base = vm->idt; - sregs.idt.limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +kvm_setup_idt (vcpu->vm, &sregs.idt); sregs.gdt.base = vm->gdt; sregs.gdt.limit =getpagesize () -1 ;kvm_seg_set_kernel_data_64bit (NULL ,DEFAULT_DATA_SELECTOR , &sregs.gs);vcpu_sregs_set (vcpu, &sregs); - *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +sync_exception_handlers_to_guest (vm); } void vm_install_exception_handler(struct kvm_vm *vm, int vector,
Re: [RFC PATCH v5 04/29] KVM: selftests: Refactor steps in vCPU descriptor table initialization
Quoted 53 lines · Binbin Wu
Quoted 38 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
Split the vCPU descriptor table initialization process into a few steps and expose them:
+ Setting up the IDT
+ Syncing exception handlers into the guestIn
kvm_setup_idt(), we conditionally allocate guest memory forvm->idtto avoid double allocation whenkvm_setup_idt()is used aftervm_init_descriptor_tables().Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/x86_64/processor.h | 2 ++ .../selftests/kvm/lib/x86_64/processor.c | 19 ++++++++++++++++--- 2 files changed, 18 insertions(+), 3 deletions(-)tools/testing/selftests/kvm/include/x86_64/processor.h +2
-0@@ -1089,6 +1089,8 @@ struct idt_entry {uint32_t offset2;uint32_t reserved; }; +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt); +void sync_exception_handlers_to_guest (struct kvm_vm *vm);void vm_init_descriptor_tables (struct kvm_vm *vm);void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu); void vm_install_exception_handler(struct kvm_vm *vm, int vector,tools/testing/selftests/kvm/lib/x86_64/processor.c +0
-0tools/testing/selftests/kvm/lib/x86_64/processor.c void vm_init_descriptor_tables(struct kvm_vm *vm) · line 1161
Quoted 7 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +4
-0@@ -1155,19 +1155,32 @@ void vm_init_descriptor_tables(struct kvm_vm *vm) DEFAULT_CODE_SELECTOR); } +void kvm_setup_idt (struct kvm_vm *vm,struct kvm_dtable *dt) +{ +if (!vm->idt) + vm->idt =vm_vaddr_alloc_page (vm);IDT is allocated in DATA memslot in current code, but here, when using
vm_vaddr_alloc_page(), it will be allocated inTEST_DATAmemslot.
Quoted 2 lines
Do we need to follow the current code to use
__vm_vaddr_alloc_page(vm, MEM_REGION_DATA)instead?
This code is no longer needed after Sean's refactor in "[PATCH 00/18] KVM: selftests: Clean up x86's DT initialization"
https://lore.kernel.org/lkml/[email protected]/
Quoted 30 lines
Quoted 29 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +12
-3+ + dt->base = vm->idt; + dt->limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +} + +void sync_exception_handlers_to_guest (struct kvm_vm *vm) +{ + *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +} +void vcpu_init_descriptor_tables (struct kvm_vcpu *vcpu) {struct kvm_vm *vm = vcpu->vm;struct kvm_sregs sregs;vcpu_sregs_get (vcpu, &sregs); - sregs.idt.base = vm->idt; - sregs.idt.limit =NUM_INTERRUPTS *sizeof (struct idt_entry ) -1 ; +kvm_setup_idt (vcpu->vm, &sregs.idt); sregs.gdt.base = vm->gdt; sregs.gdt.limit =getpagesize () -1 ;kvm_seg_set_kernel_data_64bit (NULL ,DEFAULT_DATA_SELECTOR , &sregs.gs);vcpu_sregs_set (vcpu, &sregs); - *(vm_vaddr_t *)addr_gva2hva (vm, (vm_vaddr_t)(&exception_handlers)) = vm->handlers; +sync_exception_handlers_to_guest (vm); } void vm_install_exception_handler(struct kvm_vm *vm, int vector,
RFC PATCH v5 5/29 KVM: selftests: Add helper functions to create TDX VMs
In reply to Sagi ShaharFrom: Erdem Aktas <[email protected]>
TDX requires additional IOCTLs to initialize VM and vCPUs to add private memory and to finalize the VM memory. Also additional utility functions are provided to manipulate a TD, similar to those that manipulate a VM in the current selftest framework.
A TD's initial register state cannot be manipulated directly by setting the VM's memory, hence boot code is provided at the TD's reset vector. This boot code takes boot parameters loaded in the TD's memory and sets up the TD for the selftest.
--- tools/testing/selftests/kvm/Makefile | 2 + .../kvm/include/x86_64/tdx/td_boot.h | 82 ++++ .../kvm/include/x86_64/tdx/td_boot_asm.h | 16 + .../kvm/include/x86_64/tdx/tdx_util.h | 16 + .../selftests/kvm/lib/x86_64/tdx/td_boot.S | 101 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 434 ++++++++++++++++++ 6 files changed, 651 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c
tools/testing/selftests/kvm/Makefile +2 -0
@@ -50,6 +50,8 @@ LIBKVM_x86_64 += lib/x86_64/svm.c LIBKVM_x86_64 += lib/x86_64/ucall.c LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c +LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c +LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h new file +82 -0
82 lines not on this page · raw message
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h new file +16 -0
@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TD_BOOT_ASM_H +#define SELFTEST_TDX_TD_BOOT_ASM_H + +/* +* GPA where TD boot parameters wil lbe loaded. +* +* TD_BOOT_PARAMETERS_GPA is arbitrarily chosen to +* +* + be within the 4GB address space +* + provide enough contiguous memory for the struct td_boot_parameters such +* that there is one struct td_per_vcpu_parameters for KVM_MAX_VCPUS +*/ +#define TD_BOOT_PARAMETERS_GPA 0xffff0000 + +#endif // SELFTEST_TDX_TD_BOOT_ASM_H
tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h new file +16 -0
@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTESTS_TDX_KVM_UTIL_H +#define SELFTESTS_TDX_KVM_UTIL_H + +#include <stdint.h> + +#include "kvm_util_base.h" + +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code); + +struct kvm_vm *td_create (void ); +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes); +void td_finalize (struct kvm_vm *vm); + +#endif // SELFTESTS_TDX_KVM_UTIL_H
tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S new file +101 -0
101 lines not on this page · raw message
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +434 -0
434 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 05/29] KVM: selftests: Add helper functions to create TDX VMs
Quoted 11 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+/** +* Adds a vCPU to a TD (Trusted Domain) with minimum defaults. It will not set +* up any general purpose registers as they will be initialized by the TDX. In +* TDX, vCPUs RIP is set to 0xFFFFFFF0. See Intel TDX EAS Section "Initial State +* of Guest GPRs" for more information on vCPUs initial register values when +* entering the TD first time. +* +* Input Args: +* vm - Virtual Machine +* vcpuid - The id of the VCPU to add to the VM.
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 262
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+*/ +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code) +{ +struct kvm_vcpu *vcpu; + +/* +* TD setup will not use the value of rip set in vm_vcpu_add anyway, so +* NULL can be used for guest_code. +*/ + vcpu =vm_vcpu_add (vm, vcpu_id,NULL );
Rather than to call vm_vcpu_add(), is is better to call __vm_vcpu_add(), __vm_vaddr_alloc() for vcpu->initial_stack_addr and vcpu_mp_state_set() only?
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +8
-0+tdx_td_vcpu_init (vcpu); + +load_td_boot_parameters (addr_gpa2hva (vm,TD_BOOT_PARAMETERS_GPA ), + vcpu, guest_code); + +return vcpu; +} +
...
Quoted 54 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +54
-0+static void td_setup_boot_code (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_code_allocation =round_up (TD_BOOT_CODE_SIZE ,PAGE_SIZE ); +vm_paddr_t boot_code_base_gpa =FOUR_GIGABYTES_GPA - boot_code_allocation; +size_t npages =DIV_ROUND_UP (boot_code_allocation,PAGE_SIZE ); + +vm_userspace_mem_region_add (vm, src_type, boot_code_base_gpa,1 , npages, +KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, boot_code_allocation, boot_code_base_gpa,1 ); +TEST_ASSERT_EQ (addr, boot_code_base_gpa); + +load_td_boot_code (vm); +} + +static size_t td_boot_parameters_size (void ) +{ +int max_vcpus =kvm_check_cap (KVM_CAP_MAX_VCPUS ); +size_t total_per_vcpu_parameters_size = + max_vcpus *sizeof (struct td_per_vcpu_parameters ); + +return sizeof (struct td_boot_parameters ) + total_per_vcpu_parameters_size; +} + +static void td_setup_boot_parameters (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_params_size =td_boot_parameters_size (); +int npages =DIV_ROUND_UP (boot_params_size,PAGE_SIZE ); +size_t total_size = npages *PAGE_SIZE ; + +vm_userspace_mem_region_add (vm, src_type,TD_BOOT_PARAMETERS_GPA ,2 , + npages,KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, total_size,TD_BOOT_PARAMETERS_GPA ,2 ); +TEST_ASSERT_EQ (addr,TD_BOOT_PARAMETERS_GPA ); +} + +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes) +{ +uint64_t nr_pages_required; + +tdx_enable_capabilities (vm); + +tdx_configure_memory_encryption (vm); + +tdx_td_init (vm, attributes); + + nr_pages_required =vm_nr_pages_required (VM_MODE_DEFAULT ,1 ,0 ); + +/* +* Add memory (add 0th memslot) for TD. This will be used to setup the +* CPU (provide stack space for the CPU) and to load the elf file. +*/
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 425
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+vm_userspace_mem_region_add (vm, src_type,0 ,0 , nr_pages_required, +KVM_MEM_PRIVATE ); + +kvm_vm_elf_load (vm, program_invocation_name); + +vm_init_descriptor_tables (vm); + +td_setup_boot_code (vm, src_type); +td_setup_boot_parameters (vm, src_type); +}
Could we define slot ID macros for slot 0, 1, 2? e.g. BOOT_SLOT_ID_0, BOOT_SLOT_ID_1,BOOT_SLOT_ID_2.
Re: [RFC PATCH v5 05/29] KVM: selftests: Add helper functions to create TDX VMs
In reply to Sagi ShaharQuoted 502 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
TDX requires additional IOCTLs to initialize VM and vCPUs to add private memory and to finalize the VM memory. Also additional utility functions are provided to manipulate a TD, similar to those that manipulate a VM in the current selftest framework.
A TD's initial register state cannot be manipulated directly by setting the VM's memory, hence boot code is provided at the TD's reset vector. This boot code takes boot parameters loaded in the TD's memory and sets up the TD for the selftest.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 2 + .../kvm/include/x86_64/tdx/td_boot.h | 82 ++++ .../kvm/include/x86_64/tdx/td_boot_asm.h | 16 + .../kvm/include/x86_64/tdx/tdx_util.h | 16 + .../selftests/kvm/lib/x86_64/tdx/td_boot.S | 101 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 434 ++++++++++++++++++ 6 files changed, 651 insertions(+)create mode 100644
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot.hcreate mode 100644tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.hcreate mode 100644tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.hcreate mode 100644tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.Screate mode 100644tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.ctools/testing/selftests/kvm/Makefile +2
-0@@ -50,6 +50,8 @@ LIBKVM_x86_64 += lib/x86_64/svm.c LIBKVM_x86_64 += lib/x86_64/ucall.c LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c +LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c +LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.ctools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h new file +82
-0@@ -0,0 +1,82 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TD_BOOT_H +#define SELFTEST_TDX_TD_BOOT_H + +#include <stdint.h> +#include "tdx/td_boot_asm.h" + +/* +* Layout for boot section (not to scale) +* +* GPA +* ┌─────────────────────────────┬──0x1_0000_0000 (4GB) +* │ Boot code trampoline │ +* ├─────────────────────────────┼──0x0_ffff_fff0: Reset vector (16B below 4GB) +* │ Boot code │ +* ├─────────────────────────────┼──td_boot will be copied here, so that the +* │ │ jmp to td_boot is exactly at the reset vector +* │ Empty space │ +* │ │ +* ├─────────────────────────────┤ +* │ │ +* │ │ +* │ Boot parameters │ +* │ │ +* │ │ +* └─────────────────────────────┴──0x0_ffff_0000: TD_BOOT_PARAMETERS_GPA +*/ +#define FOUR_GIGABYTES_GPA (4ULL << 30) + +/** +* The exact memory layout for LGDT or LIDT instructions. +*/ +struct __packed td_boot_parameters_dtr { +uint16_t limit; +uint32_t base; +}; + +/** +* The exact layout in memory required for a ljmp, including the selector for +* changing code segment. +*/ +struct __packed td_boot_parameters_ljmp_target { +uint32_t eip_gva; +uint16_t code64_sel; +}; + +/** +* Allows each vCPU to be initialized with different eip and esp. +*/ +struct __packed td_per_vcpu_parameters { +uint32_t esp_gva; +struct td_boot_parameters_ljmp_target ljmp_target; +}; + +/** +* Boot parameters for the TD. +* +* Unlike a regular VM, we can't ask KVM to set registers such as esp, eip, etc +* before boot, so to run selftests, these registers' values have to be +* initialized by the TD. +* +* This struct is loaded in TD private memory at TD_BOOT_PARAMETERS_GPA. +* +* The TD boot code will read off parameters from this struct and set up the +* vcpu for executing selftests. +*/ +struct __packed td_boot_parameters { +uint32_t cr0; +uint32_t cr3; +uint32_t cr4; +struct td_boot_parameters_dtr gdtr; +struct td_boot_parameters_dtr idtr; +struct td_per_vcpu_parameters per_vcpu[]; +}; + +extern void td_boot (void ); +extern void reset_vector (void ); +extern void td_boot_code_end (void ); + +#define TD_BOOT_CODE_SIZE (td_boot_code_end - td_boot) + +#endif /* SELFTEST_TDX_TD_BOOT_H */ tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h new file +16
-0@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TD_BOOT_ASM_H +#define SELFTEST_TDX_TD_BOOT_ASM_H + +/* +* GPA where TD boot parameters wil lbe loaded. +* +* TD_BOOT_PARAMETERS_GPA is arbitrarily chosen to +* +* + be within the 4GB address space +* + provide enough contiguous memory for the struct td_boot_parameters such +* that there is one struct td_per_vcpu_parameters for KVM_MAX_VCPUS +*/ +#define TD_BOOT_PARAMETERS_GPA 0xffff0000 + +#endif // SELFTEST_TDX_TD_BOOT_ASM_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h new file +16
-0@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTESTS_TDX_KVM_UTIL_H +#define SELFTESTS_TDX_KVM_UTIL_H + +#include <stdint.h> + +#include "kvm_util_base.h" + +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code); + +struct kvm_vm *td_create (void ); +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes); +void td_finalize (struct kvm_vm *vm); + +#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S new file +101
-0@@ -0,0 +1,101 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ + +#include "tdx/td_boot_asm.h" + +/* Offsets for reading struct td_boot_parameters */ +#define TD_BOOT_PARAMETERS_CR0 0 +#define TD_BOOT_PARAMETERS_CR3 4 +#define TD_BOOT_PARAMETERS_CR4 8 +#define TD_BOOT_PARAMETERS_GDT 12 +#define TD_BOOT_PARAMETERS_IDT 18 +#define TD_BOOT_PARAMETERS_PER_VCPU 24 + +/* Offsets for reading struct td_per_vcpu_parameters */ +#define TD_PER_VCPU_PARAMETERS_ESP_GVA 0 +#define TD_PER_VCPU_PARAMETERS_LJMP_TARGET 4 + +#define SIZEOF_TD_PER_VCPU_PARAMETERS 10 + +.code32 + +.globl td_boot +td_boot: + /* In this procedure, edi is used as a temporary register */ + cli + + /* Paging is off */ + + movl $TD_BOOT_PARAMETERS_GPA, %ebx + + /* + * Find the address of struct td_per_vcpu_parameters for this + * vCPU based on esi (TDX spec: initialized with vcpu id). Put + * struct address into register for indirect addressing + */ + movl $SIZEOF_TD_PER_VCPU_PARAMETERS, %eax + mul %esi + leal TD_BOOT_PARAMETERS_PER_VCPU(%ebx), %edi + addl %edi, %eax + + /* Setup stack */ + movl TD_PER_VCPU_PARAMETERS_ESP_GVA(%eax), %esp + + /* Setup GDT */ + leal TD_BOOT_PARAMETERS_GDT(%ebx), %edi + lgdt (%edi) + + /* Setup IDT */ + leal TD_BOOT_PARAMETERS_IDT(%ebx), %edi + lidt (%edi) + + /* + * Set up control registers (There are no instructions to + * mov from memory to control registers, hence we need to use ebx + * as a scratch register) + */ + movl TD_BOOT_PARAMETERS_CR4(%ebx), %edi + movl %edi, %cr4 + movl TD_BOOT_PARAMETERS_CR3(%ebx), %edi + movl %edi, %cr3 + movl TD_BOOT_PARAMETERS_CR0(%ebx), %edi + movl %edi, %cr0 + + /* Paging is on after setting the most significant bit on cr0 */ + + /* + * Jump to selftest guest code. Far jumps read <segment + * selector:new eip> from <addr+4:addr>. This location has + * already been set up in boot parameters, and we can read boot + * parameters because boot code and boot parameters are loaded so + * that GVA and GPA are mapped 1:1. + */ + ljmp *TD_PER_VCPU_PARAMETERS_LJMP_TARGET(%eax) + +.globl reset_vector +reset_vector: + jmp td_boot + /* + * Pad reset_vector to its full size of 16 bytes so that this + * can be loaded with the end of reset_vector aligned to GPA=4G + */ + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + +/* Leave marker so size of td_boot code can be computed */ +.globl td_boot_code_end +td_boot_code_end: + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +213
-0@@ -0,0 +1,434 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#define _GNU_SOURCE +#include <asm/kvm.h> +#include <asm/kvm_host.h> +#include <errno.h> +#include <linux/kvm.h> +#include <stdint.h> +#include <sys/ioctl.h> + +#include "kvm_util.h" +#include "test_util.h" +#include "tdx/td_boot.h" +#include "kvm_util_base.h" +#include "processor.h" + +/* +* TDX ioctls +*/ + +static char *tdx_cmd_str[] = { +"KVM_TDX_CAPABILITIES" , +"KVM_TDX_INIT_VM" , +"KVM_TDX_INIT_VCPU" , +"KVM_TDX_INIT_MEM_REGION" , +"KVM_TDX_FINALIZE_VM" +}; +#define TDX_MAX_CMD_STR (ARRAY_SIZE(tdx_cmd_str)) + +static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +{ +struct kvm_tdx_cmd tdx_cmd; +int r; + +TEST_ASSERT (ioctl_no <TDX_MAX_CMD_STR ,"Unknown TDX CMD : %d\n" , + ioctl_no); + +memset (&tdx_cmd,0x0 ,sizeof (tdx_cmd)); + tdx_cmd.id = ioctl_no; + tdx_cmd.flags = flags; + tdx_cmd.data = (uint64_t )data; + + r =ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +TEST_ASSERT (r ==0 ,"%s failed: %d %d" , tdx_cmd_str[ioctl_no], r, + errno); +} + +#define XFEATURE_MASK_CET (XFEATURE_MASK_CET_USER | XFEATURE_MASK_CET_KERNEL) + +static void tdx_apply_cpuid_restrictions (struct kvm_cpuid2 *cpuid_data) +{ +for (int i =0 ; i < cpuid_data->nent; i++) { +struct kvm_cpuid_entry2 *e = &cpuid_data->entries[i]; + +if (e->function ==0xd && e->index ==0 ) { +/* +* TDX module requires both XTILE_{CFG, DATA} to be set. +* Both bits are required for AMX to be functional. +*/ +if ((e->eax &XFEATURE_MASK_XTILE ) != +XFEATURE_MASK_XTILE ) { + e->eax &= ~XFEATURE_MASK_XTILE ; + } + } +if (e->function ==0xd && e->index ==1 ) { +/* +* TDX doesn't support LBR yet. +* Disable bits from the XCR0 register. +*/ + e->ecx &= ~XFEATURE_MASK_LBR ; +/* +* TDX modules requires both CET_{U, S} to be set even +* if only one is supported. +*/ +if (e->ecx &XFEATURE_MASK_CET ) + e->ecx |=XFEATURE_MASK_CET ; + } + } +} + +static void tdx_td_init (struct kvm_vm *vm,uint64_t attributes) +{ +const struct kvm_cpuid2 *cpuid; +struct kvm_tdx_init_vm *init_vm; + + cpuid =kvm_get_supported_cpuid (); + + init_vm =malloc (sizeof (*init_vm) + +sizeof (init_vm->cpuid.entries[0 ]) * cpuid->nent); + +memset (init_vm,0 ,sizeof (*init_vm)); +memcpy (&init_vm->cpuid, cpuid,kvm_cpuid2_size (cpuid->nent)); + + init_vm->attributes = attributes; + +tdx_apply_cpuid_restrictions (&init_vm->cpuid); + +tdx_ioctl (vm->fd,KVM_TDX_INIT_VM ,0 , init_vm); +} + +static void tdx_td_vcpu_init (struct kvm_vcpu *vcpu) +{ +const struct kvm_cpuid2 *cpuid =kvm_get_supported_cpuid (); + +vcpu_init_cpuid (vcpu, cpuid); +tdx_ioctl (vcpu->fd,KVM_TDX_INIT_VCPU ,0 ,NULL ); +} + +static void tdx_init_mem_region (struct kvm_vm *vm,void *source_pages, +uint64_t gpa,uint64_t size) +{ +struct kvm_tdx_init_mem_region mem_region = { + .source_addr = (uint64_t )source_pages, + .gpa = gpa, + .nr_pages = size /PAGE_SIZE , + }; +uint32_t metadata =KVM_TDX_MEASURE_MEMORY_REGION ; + +TEST_ASSERT ((mem_region.nr_pages >0 ) && + ((mem_region.nr_pages *PAGE_SIZE ) == size), +"Cannot add partial pages to the guest memory.\n" ); +TEST_ASSERT (((uint64_t )source_pages & (PAGE_SIZE -1 )) ==0 , +"Source memory buffer is not page aligned\n" ); +tdx_ioctl (vm->fd,KVM_TDX_INIT_MEM_REGION , metadata, &mem_region); +} + +static void tdx_td_finalizemr (struct kvm_vm *vm) +{ +tdx_ioctl (vm->fd,KVM_TDX_FINALIZE_VM ,0 ,NULL ); +} + +/* +* TD creation/setup/finalization +*/ + +static void tdx_enable_capabilities (struct kvm_vm *vm) +{ +int rc; + + rc =kvm_check_cap (KVM_CAP_X2APIC_API ); +TEST_ASSERT (rc,"TDX: KVM_CAP_X2APIC_API is not supported!" ); + rc =kvm_check_cap (KVM_CAP_SPLIT_IRQCHIP ); +TEST_ASSERT (rc,"TDX: KVM_CAP_SPLIT_IRQCHIP is not supported!" ); + +vm_enable_cap (vm,KVM_CAP_X2APIC_API , +KVM_X2APIC_API_USE_32BIT_IDS | +KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK ); +vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +} + +static void tdx_configure_memory_encryption (struct kvm_vm *vm) +{ +/* Configure shared/enCrypted bit for this VM according to TDX spec */ + vm->arch.s_bit =1ULL << (vm->pa_bits -1 ); + vm->arch.c_bit =0 ; +/* Set gpa_protected_mask so that tagging/untagging of GPAs works */ + vm->gpa_protected_mask = vm->arch.s_bit; +/* This VM is protected (has memory encryption) */ + vm->protected = true; +} + +static void tdx_apply_cr4_restrictions (struct kvm_sregs *sregs) +{ +/* TDX spec 11.6.2: CR4 bit MCE is fixed to 1 */ + sregs->cr4 |=X86_CR4_MCE ; + +/* Set this because UEFI also sets this up, to handle XMM exceptions */ + sregs->cr4 |=X86_CR4_OSXMMEXCPT ; + +/* TDX spec 11.6.2: CR4 bit VMXE and SMXE are fixed to 0 */ + sregs->cr4 &= ~(X86_CR4_VMXE |X86_CR4_SMXE ); +} + +static void load_td_boot_code (struct kvm_vm *vm) +{ +void *boot_code_hva =addr_gpa2hva (vm,FOUR_GIGABYTES_GPA -TD_BOOT_CODE_SIZE ); + +TEST_ASSERT (td_boot_code_end - reset_vector ==16 , +"The reset vector must be 16 bytes in size." ); +memcpy (boot_code_hva, td_boot,TD_BOOT_CODE_SIZE ); +} + +static void load_td_per_vcpu_parameters (struct td_boot_parameters *params, +struct kvm_sregs *sregs, +struct kvm_vcpu *vcpu, +void *guest_code) +{ +/* Store vcpu_index to match what the TDX module would store internally */ +static uint32_t vcpu_index; + +struct td_per_vcpu_parameters *vcpu_params = ¶ms->per_vcpu[vcpu_index]; + +TEST_ASSERT (vcpu->initial_stack_addr !=0 , +"initial stack address should not be 0" ); +TEST_ASSERT (vcpu->initial_stack_addr <=0xffffffff , +"initial stack address must fit in 32 bits" ); +TEST_ASSERT ((uint64_t )guest_code <=0xffffffff , +"guest_code must fit in 32 bits" ); +TEST_ASSERT (sregs->cs.selector !=0 ,"cs.selector should not be 0" ); + + vcpu_params->esp_gva = (uint32_t )(uint64_t )vcpu->initial_stack_addr; + vcpu_params->ljmp_target.eip_gva = (uint32_t )(uint64_t )guest_code; + vcpu_params->ljmp_target.code64_sel = sregs->cs.selector; + + vcpu_index++; +} + +static void load_td_common_parameters (struct td_boot_parameters *params, +struct kvm_sregs *sregs) +{ +/* Set parameters! */ + params->cr0 = sregs->cr0; + params->cr3 = sregs->cr3;
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 223
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+ params->cr4 = sregs->cr4; + params->gdtr.limit = sregs->gdt.limit; + params->gdtr.base = sregs->gdt.base; + params->idtr.limit = sregs->idt.limit; + params->idtr.base = sregs->idt.base; + +TEST_ASSERT (params->cr0 !=0 ,"cr0 should not be 0" ); +TEST_ASSERT (params->cr3 !=0 ,"cr3 should not be 0" ); +TEST_ASSERT (params->cr4 !=0 ,"cr4 should not be 0" ); +TEST_ASSERT (params->gdtr.base !=0 ,"gdt base address should not be 0" );
Do we also need to check idtr.base?
Quoted 66 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +66
-0+} + +static void load_td_boot_parameters (struct td_boot_parameters *params, +struct kvm_vcpu *vcpu,void *guest_code) +{ +struct kvm_sregs sregs; + +/* Assemble parameters in sregs */ +memset (&sregs,0 ,sizeof (struct kvm_sregs )); +vcpu_setup_mode_sregs (vcpu->vm, &sregs); +tdx_apply_cr4_restrictions (&sregs); +kvm_setup_idt (vcpu->vm, &sregs.idt); + +if (!params->cr0) +load_td_common_parameters (params, &sregs); + +load_td_per_vcpu_parameters (params, &sregs, vcpu, guest_code); +} + +/** +* Adds a vCPU to a TD (Trusted Domain) with minimum defaults. It will not set +* up any general purpose registers as they will be initialized by the TDX. In +* TDX, vCPUs RIP is set to 0xFFFFFFF0. See Intel TDX EAS Section "Initial State +* of Guest GPRs" for more information on vCPUs initial register values when +* entering the TD first time. +* +* Input Args: +* vm - Virtual Machine +* vcpuid - The id of the VCPU to add to the VM. +*/ +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code) +{ +struct kvm_vcpu *vcpu; + +/* +* TD setup will not use the value of rip set in vm_vcpu_add anyway, so +* NULL can be used for guest_code. +*/ + vcpu =vm_vcpu_add (vm, vcpu_id,NULL ); + +tdx_td_vcpu_init (vcpu); + +load_td_boot_parameters (addr_gpa2hva (vm,TD_BOOT_PARAMETERS_GPA ), + vcpu, guest_code); + +return vcpu; +} + +/** +* Iterate over set ranges within sparsebit @s. In each iteration, +* @range_begin and @range_end will take the beginning and end of the set range, +* which are of type sparsebit_idx_t. +* +* For example, if the range [3, 7] (inclusive) is set, within the iteration, +* @range_begin will take the value 3 and @range_end will take the value 7. +* +* Ensure that there is at least one bit set before using this macro with +* sparsebit_any_set(), because sparsebit_first_set() will abort if none are +* set. +*/ +#define sparsebit_for_each_set_range (s, range_begin, range_end) \ + for (range_begin = sparsebit_first_set(s), \ + range_end = sparsebit_next_clear(s, range_begin) - 1; \ + range_begin && range_end; \ + range_begin = sparsebit_next_set(s, range_end), \ + range_end = sparsebit_next_clear(s, range_begin) - 1)
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 299
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+/* +* sparsebit_next_clear() can return 0 if [x, 2**64-1] are all set, and the -1 +* would then cause an underflow back to 2**64 - 1. This is expected and +* correct. +* +* If the last range in the sparsebit is [x, y] and we try to iterate, +* sparsebit_next_set() will return 0, and sparsebit_next_clear() will try and +* find the first range, but that's correct because the condition expression +* would cause us to quit the loop. +*/
Since both sev and tdx need sparsebit_for_each_set_range(), can it be moved to a header file to avoid code duplication?
Quoted 135 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +135
-0+ +static void load_td_memory_region (struct kvm_vm *vm, +struct userspace_mem_region *region) +{ +const struct sparsebit *pages = region->protected_phy_pages; +const uint64_t hva_base = region->region.userspace_addr; +const vm_paddr_t gpa_base = region->region.guest_phys_addr; +const sparsebit_idx_t lowest_page_in_region = gpa_base >> + vm->page_shift; + +sparsebit_idx_t i; +sparsebit_idx_t j; + +if (!sparsebit_any_set (pages)) +return ; + +sparsebit_for_each_set_range (pages, i, j) { +const uint64_t size_to_load = (j - i +1 ) * vm->page_size; +const uint64_t offset = + (i - lowest_page_in_region) * vm->page_size; +const uint64_t hva = hva_base + offset; +const uint64_t gpa = gpa_base + offset; +void *source_addr; + +/* +* KVM_TDX_INIT_MEM_REGION ioctl cannot encrypt memory in place, +* hence we have to make a copy if there's only one backing +* memory source +*/ + source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , +MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); +TEST_ASSERT ( + source_addr, +"Could not allocate memory for loading memory region" ); + +memcpy (source_addr, (void *)hva, size_to_load); + +tdx_init_mem_region (vm, source_addr, gpa, size_to_load); + +munmap (source_addr, size_to_load); + } +} + +static void load_td_private_memory (struct kvm_vm *vm) +{ +int ctr; +struct userspace_mem_region *region; + +hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) { +load_td_memory_region (vm, region); + } +} + +struct kvm_vm *td_create (void ) +{ +struct vm_shape shape; + + shape.mode =VM_MODE_DEFAULT ; + shape.type =KVM_X86_TDX_VM ; +return ____vm_create (shape); +} + +static void td_setup_boot_code (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_code_allocation =round_up (TD_BOOT_CODE_SIZE ,PAGE_SIZE ); +vm_paddr_t boot_code_base_gpa =FOUR_GIGABYTES_GPA - boot_code_allocation; +size_t npages =DIV_ROUND_UP (boot_code_allocation,PAGE_SIZE ); + +vm_userspace_mem_region_add (vm, src_type, boot_code_base_gpa,1 , npages, +KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, boot_code_allocation, boot_code_base_gpa,1 ); +TEST_ASSERT_EQ (addr, boot_code_base_gpa); + +load_td_boot_code (vm); +} + +static size_t td_boot_parameters_size (void ) +{ +int max_vcpus =kvm_check_cap (KVM_CAP_MAX_VCPUS ); +size_t total_per_vcpu_parameters_size = + max_vcpus *sizeof (struct td_per_vcpu_parameters ); + +return sizeof (struct td_boot_parameters ) + total_per_vcpu_parameters_size; +} + +static void td_setup_boot_parameters (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_params_size =td_boot_parameters_size (); +int npages =DIV_ROUND_UP (boot_params_size,PAGE_SIZE ); +size_t total_size = npages *PAGE_SIZE ; + +vm_userspace_mem_region_add (vm, src_type,TD_BOOT_PARAMETERS_GPA ,2 , + npages,KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, total_size,TD_BOOT_PARAMETERS_GPA ,2 ); +TEST_ASSERT_EQ (addr,TD_BOOT_PARAMETERS_GPA ); +} + +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes) +{ +uint64_t nr_pages_required; + +tdx_enable_capabilities (vm); + +tdx_configure_memory_encryption (vm); + +tdx_td_init (vm, attributes); + + nr_pages_required =vm_nr_pages_required (VM_MODE_DEFAULT ,1 ,0 ); + +/* +* Add memory (add 0th memslot) for TD. This will be used to setup the +* CPU (provide stack space for the CPU) and to load the elf file. +*/ +vm_userspace_mem_region_add (vm, src_type,0 ,0 , nr_pages_required, +KVM_MEM_PRIVATE ); + +kvm_vm_elf_load (vm, program_invocation_name); + +vm_init_descriptor_tables (vm); + +td_setup_boot_code (vm, src_type); +td_setup_boot_parameters (vm, src_type); +} + +void td_finalize (struct kvm_vm *vm) +{ +sync_exception_handlers_to_guest (vm); + +load_td_private_memory (vm); + +tdx_td_finalizemr (vm); +}
Re: [RFC PATCH v5 05/29] KVM: selftests: Add helper functions to create TDX VMs
In reply to Sagi ShaharQuoted 138 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
TDX requires additional IOCTLs to initialize VM and vCPUs to add private memory and to finalize the VM memory. Also additional utility functions are provided to manipulate a TD, similar to those that manipulate a VM in the current selftest framework.
A TD's initial register state cannot be manipulated directly by setting the VM's memory, hence boot code is provided at the TD's reset vector. This boot code takes boot parameters loaded in the TD's memory and sets up the TD for the selftest.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 2 + .../kvm/include/x86_64/tdx/td_boot.h | 82 ++++ .../kvm/include/x86_64/tdx/td_boot_asm.h | 16 + .../kvm/include/x86_64/tdx/tdx_util.h | 16 + .../selftests/kvm/lib/x86_64/tdx/td_boot.S | 101 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 434 ++++++++++++++++++ 6 files changed, 651 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.ctools/testing/selftests/kvm/Makefile +2
-0@@ -50,6 +50,8 @@ LIBKVM_x86_64 += lib/x86_64/svm.c LIBKVM_x86_64 += lib/x86_64/ucall.c LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c +LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c +LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.ctools/testing/selftests/kvm/include/x86_64/tdx/td_boot.h new file +82
-0@@ -0,0 +1,82 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TD_BOOT_H +#define SELFTEST_TDX_TD_BOOT_H + +#include <stdint.h> +#include "tdx/td_boot_asm.h" + +/* +* Layout for boot section (not to scale) +* +* GPA +* ┌─────────────────────────────┬──0x1_0000_0000 (4GB) +* │ Boot code trampoline │ +* ├─────────────────────────────┼──0x0_ffff_fff0: Reset vector (16B below 4GB) +* │ Boot code │ +* ├─────────────────────────────┼──td_boot will be copied here, so that the +* │ │ jmp to td_boot is exactly at the reset vector +* │ Empty space │ +* │ │ +* ├─────────────────────────────┤ +* │ │ +* │ │ +* │ Boot parameters │ +* │ │ +* │ │ +* └─────────────────────────────┴──0x0_ffff_0000: TD_BOOT_PARAMETERS_GPA +*/ +#define FOUR_GIGABYTES_GPA (4ULL << 30) + +/** +* The exact memory layout for LGDT or LIDT instructions. +*/ +struct __packed td_boot_parameters_dtr { +uint16_t limit; +uint32_t base; +}; + +/** +* The exact layout in memory required for a ljmp, including the selector for +* changing code segment. +*/ +struct __packed td_boot_parameters_ljmp_target { +uint32_t eip_gva; +uint16_t code64_sel; +}; + +/** +* Allows each vCPU to be initialized with different eip and esp. +*/ +struct __packed td_per_vcpu_parameters { +uint32_t esp_gva; +struct td_boot_parameters_ljmp_target ljmp_target; +}; + +/** +* Boot parameters for the TD. +* +* Unlike a regular VM, we can't ask KVM to set registers such as esp, eip, etc +* before boot, so to run selftests, these registers' values have to be +* initialized by the TD. +* +* This struct is loaded in TD private memory at TD_BOOT_PARAMETERS_GPA. +* +* The TD boot code will read off parameters from this struct and set up the +* vcpu for executing selftests. +*/ +struct __packed td_boot_parameters { +uint32_t cr0; +uint32_t cr3; +uint32_t cr4; +struct td_boot_parameters_dtr gdtr; +struct td_boot_parameters_dtr idtr; +struct td_per_vcpu_parameters per_vcpu[]; +}; + +extern void td_boot (void ); +extern void reset_vector (void ); +extern void td_boot_code_end (void ); + +#define TD_BOOT_CODE_SIZE (td_boot_code_end - td_boot) + +#endif /* SELFTEST_TDX_TD_BOOT_H */ tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h new file +0
-0
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h line 6
Quoted 6 lines
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h new file +6
-0@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TD_BOOT_ASM_H +#define SELFTEST_TDX_TD_BOOT_ASM_H + +/* +* GPA where TD boot parameters wil lbe loaded.
Typo: "wil lbe" ==> "will be"
Quoted 224 lines
tools/testing/selftests/kvm/include/x86_64/tdx/td_boot_asm.h new file +10
-0+* +* TD_BOOT_PARAMETERS_GPA is arbitrarily chosen to +* +* + be within the 4GB address space +* + provide enough contiguous memory for the struct td_boot_parameters such +* that there is one struct td_per_vcpu_parameters for KVM_MAX_VCPUS +*/ +#define TD_BOOT_PARAMETERS_GPA 0xffff0000 + +#endif // SELFTEST_TDX_TD_BOOT_ASM_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h new file +16
-0@@ -0,0 +1,16 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTESTS_TDX_KVM_UTIL_H +#define SELFTESTS_TDX_KVM_UTIL_H + +#include <stdint.h> + +#include "kvm_util_base.h" + +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code); + +struct kvm_vm *td_create (void ); +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes); +void td_finalize (struct kvm_vm *vm); + +#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S new file +101
-0@@ -0,0 +1,101 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ + +#include "tdx/td_boot_asm.h" + +/* Offsets for reading struct td_boot_parameters */ +#define TD_BOOT_PARAMETERS_CR0 0 +#define TD_BOOT_PARAMETERS_CR3 4 +#define TD_BOOT_PARAMETERS_CR4 8 +#define TD_BOOT_PARAMETERS_GDT 12 +#define TD_BOOT_PARAMETERS_IDT 18 +#define TD_BOOT_PARAMETERS_PER_VCPU 24 + +/* Offsets for reading struct td_per_vcpu_parameters */ +#define TD_PER_VCPU_PARAMETERS_ESP_GVA 0 +#define TD_PER_VCPU_PARAMETERS_LJMP_TARGET 4 + +#define SIZEOF_TD_PER_VCPU_PARAMETERS 10 + +.code32 + +.globl td_boot +td_boot: + /* In this procedure, edi is used as a temporary register */ + cli + + /* Paging is off */ + + movl $TD_BOOT_PARAMETERS_GPA, %ebx + + /* + * Find the address of struct td_per_vcpu_parameters for this + * vCPU based on esi (TDX spec: initialized with vcpu id). Put + * struct address into register for indirect addressing + */ + movl $SIZEOF_TD_PER_VCPU_PARAMETERS, %eax + mul %esi + leal TD_BOOT_PARAMETERS_PER_VCPU(%ebx), %edi + addl %edi, %eax + + /* Setup stack */ + movl TD_PER_VCPU_PARAMETERS_ESP_GVA(%eax), %esp + + /* Setup GDT */ + leal TD_BOOT_PARAMETERS_GDT(%ebx), %edi + lgdt (%edi) + + /* Setup IDT */ + leal TD_BOOT_PARAMETERS_IDT(%ebx), %edi + lidt (%edi) + + /* + * Set up control registers (There are no instructions to + * mov from memory to control registers, hence we need to use ebx + * as a scratch register) + */ + movl TD_BOOT_PARAMETERS_CR4(%ebx), %edi + movl %edi, %cr4 + movl TD_BOOT_PARAMETERS_CR3(%ebx), %edi + movl %edi, %cr3 + movl TD_BOOT_PARAMETERS_CR0(%ebx), %edi + movl %edi, %cr0 + + /* Paging is on after setting the most significant bit on cr0 */ + + /* + * Jump to selftest guest code. Far jumps read <segment + * selector:new eip> from <addr+4:addr>. This location has + * already been set up in boot parameters, and we can read boot + * parameters because boot code and boot parameters are loaded so + * that GVA and GPA are mapped 1:1. + */ + ljmp *TD_PER_VCPU_PARAMETERS_LJMP_TARGET(%eax) + +.globl reset_vector +reset_vector: + jmp td_boot + /* + * Pad reset_vector to its full size of 16 bytes so that this + * can be loaded with the end of reset_vector aligned to GPA=4G + */ + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + int3 + +/* Leave marker so size of td_boot code can be computed */ +.globl td_boot_code_end +td_boot_code_end: + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +79
-0@@ -0,0 +1,434 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#define _GNU_SOURCE +#include <asm/kvm.h> +#include <asm/kvm_host.h> +#include <errno.h> +#include <linux/kvm.h> +#include <stdint.h> +#include <sys/ioctl.h> + +#include "kvm_util.h" +#include "test_util.h" +#include "tdx/td_boot.h" +#include "kvm_util_base.h" +#include "processor.h" + +/* +* TDX ioctls +*/ + +static char *tdx_cmd_str[] = { +"KVM_TDX_CAPABILITIES" , +"KVM_TDX_INIT_VM" , +"KVM_TDX_INIT_VCPU" , +"KVM_TDX_INIT_MEM_REGION" , +"KVM_TDX_FINALIZE_VM" +}; +#define TDX_MAX_CMD_STR (ARRAY_SIZE(tdx_cmd_str)) + +static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +{ +struct kvm_tdx_cmd tdx_cmd; +int r; + +TEST_ASSERT (ioctl_no <TDX_MAX_CMD_STR ,"Unknown TDX CMD : %d\n" , + ioctl_no); + +memset (&tdx_cmd,0x0 ,sizeof (tdx_cmd)); + tdx_cmd.id = ioctl_no; + tdx_cmd.flags = flags; + tdx_cmd.data = (uint64_t )data; + + r =ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +TEST_ASSERT (r ==0 ,"%s failed: %d %d" , tdx_cmd_str[ioctl_no], r, + errno); +} + +#define XFEATURE_MASK_CET (XFEATURE_MASK_CET_USER | XFEATURE_MASK_CET_KERNEL) + +static void tdx_apply_cpuid_restrictions (struct kvm_cpuid2 *cpuid_data) +{ +for (int i =0 ; i < cpuid_data->nent; i++) { +struct kvm_cpuid_entry2 *e = &cpuid_data->entries[i]; + +if (e->function ==0xd && e->index ==0 ) { +/* +* TDX module requires both XTILE_{CFG, DATA} to be set. +* Both bits are required for AMX to be functional. +*/ +if ((e->eax &XFEATURE_MASK_XTILE ) != +XFEATURE_MASK_XTILE ) { + e->eax &= ~XFEATURE_MASK_XTILE ; + } + } +if (e->function ==0xd && e->index ==1 ) { +/* +* TDX doesn't support LBR yet. +* Disable bits from the XCR0 register. +*/ + e->ecx &= ~XFEATURE_MASK_LBR ; +/* +* TDX modules requires both CET_{U, S} to be set even +* if only one is supported. +*/ +if (e->ecx &XFEATURE_MASK_CET ) + e->ecx |=XFEATURE_MASK_CET ; + } + } +}
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 89
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+ +static void tdx_td_init (struct kvm_vm *vm,uint64_t attributes) +{ +const struct kvm_cpuid2 *cpuid; +struct kvm_tdx_init_vm *init_vm; + + cpuid =kvm_get_supported_cpuid (); + + init_vm =malloc (sizeof (*init_vm) + +sizeof (init_vm->cpuid.entries[0 ]) * cpuid->nent);
Can add a sanity checking for init_vm here like the following:TEST_ASSERT(init_vm, "vm allocation failed");
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 91
Quoted 2 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +2
-0+ +memset (init_vm,0 ,sizeof (*init_vm));
Can use calloc instead:init_vm = calloc(1, sizeof(*init_vm));
Quoted 30 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +30
-0+memcpy (&init_vm->cpuid, cpuid,kvm_cpuid2_size (cpuid->nent)); + + init_vm->attributes = attributes; + +tdx_apply_cpuid_restrictions (&init_vm->cpuid); + +tdx_ioctl (vm->fd,KVM_TDX_INIT_VM ,0 , init_vm); +} + +static void tdx_td_vcpu_init (struct kvm_vcpu *vcpu) +{ +const struct kvm_cpuid2 *cpuid =kvm_get_supported_cpuid (); + +vcpu_init_cpuid (vcpu, cpuid); +tdx_ioctl (vcpu->fd,KVM_TDX_INIT_VCPU ,0 ,NULL ); +} + +static void tdx_init_mem_region (struct kvm_vm *vm,void *source_pages, +uint64_t gpa,uint64_t size) +{ +struct kvm_tdx_init_mem_region mem_region = { + .source_addr = (uint64_t )source_pages, + .gpa = gpa, + .nr_pages = size /PAGE_SIZE , + }; +uint32_t metadata =KVM_TDX_MEASURE_MEMORY_REGION ; + +TEST_ASSERT ((mem_region.nr_pages >0 ) && + ((mem_region.nr_pages *PAGE_SIZE ) == size), +"Cannot add partial pages to the guest memory.\n" );
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 131
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+TEST_ASSERT (((uint64_t )source_pages & (PAGE_SIZE -1 )) ==0 , +"Source memory buffer is not page aligned\n" ); +tdx_ioctl (vm->fd,KVM_TDX_INIT_MEM_REGION , metadata, &mem_region); +} + +static void tdx_td_finalizemr (struct kvm_vm *vm) +{ +tdx_ioctl (vm->fd,KVM_TDX_FINALIZE_VM ,0 ,NULL ); +} +
Nit: tdx_td_finalizemr ==> tdx_td_finalize_mr
Quoted 50 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +50
-0+/* +* TD creation/setup/finalization +*/ + +static void tdx_enable_capabilities (struct kvm_vm *vm) +{ +int rc; + + rc =kvm_check_cap (KVM_CAP_X2APIC_API ); +TEST_ASSERT (rc,"TDX: KVM_CAP_X2APIC_API is not supported!" ); + rc =kvm_check_cap (KVM_CAP_SPLIT_IRQCHIP ); +TEST_ASSERT (rc,"TDX: KVM_CAP_SPLIT_IRQCHIP is not supported!" ); + +vm_enable_cap (vm,KVM_CAP_X2APIC_API , +KVM_X2APIC_API_USE_32BIT_IDS | +KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK ); +vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +} + +static void tdx_configure_memory_encryption (struct kvm_vm *vm) +{ +/* Configure shared/enCrypted bit for this VM according to TDX spec */ + vm->arch.s_bit =1ULL << (vm->pa_bits -1 ); + vm->arch.c_bit =0 ; +/* Set gpa_protected_mask so that tagging/untagging of GPAs works */ + vm->gpa_protected_mask = vm->arch.s_bit; +/* This VM is protected (has memory encryption) */ + vm->protected = true; +} + +static void tdx_apply_cr4_restrictions (struct kvm_sregs *sregs) +{ +/* TDX spec 11.6.2: CR4 bit MCE is fixed to 1 */ + sregs->cr4 |=X86_CR4_MCE ; + +/* Set this because UEFI also sets this up, to handle XMM exceptions */ + sregs->cr4 |=X86_CR4_OSXMMEXCPT ; + +/* TDX spec 11.6.2: CR4 bit VMXE and SMXE are fixed to 0 */ + sregs->cr4 &= ~(X86_CR4_VMXE |X86_CR4_SMXE ); +} + +static void load_td_boot_code (struct kvm_vm *vm) +{ +void *boot_code_hva =addr_gpa2hva (vm,FOUR_GIGABYTES_GPA -TD_BOOT_CODE_SIZE ); + +TEST_ASSERT (td_boot_code_end - reset_vector ==16 , +"The reset vector must be 16 bytes in size." ); +memcpy (boot_code_hva, td_boot,TD_BOOT_CODE_SIZE ); +}
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 191
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+ +static void load_td_per_vcpu_parameters (struct td_boot_parameters *params, +struct kvm_sregs *sregs, +struct kvm_vcpu *vcpu, +void *guest_code) +{ +/* Store vcpu_index to match what the TDX module would store internally */ +static uint32_t vcpu_index; + +struct td_per_vcpu_parameters *vcpu_params = ¶ms->per_vcpu[vcpu_index];
I think we can use vcpu->id in place of vcpu_index in this function, thus removing vcpu_index
Quoted 158 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +158
-0+ +TEST_ASSERT (vcpu->initial_stack_addr !=0 , +"initial stack address should not be 0" ); +TEST_ASSERT (vcpu->initial_stack_addr <=0xffffffff , +"initial stack address must fit in 32 bits" ); +TEST_ASSERT ((uint64_t )guest_code <=0xffffffff , +"guest_code must fit in 32 bits" ); +TEST_ASSERT (sregs->cs.selector !=0 ,"cs.selector should not be 0" ); + + vcpu_params->esp_gva = (uint32_t )(uint64_t )vcpu->initial_stack_addr; + vcpu_params->ljmp_target.eip_gva = (uint32_t )(uint64_t )guest_code; + vcpu_params->ljmp_target.code64_sel = sregs->cs.selector; + + vcpu_index++; +} + +static void load_td_common_parameters (struct td_boot_parameters *params, +struct kvm_sregs *sregs) +{ +/* Set parameters! */ + params->cr0 = sregs->cr0; + params->cr3 = sregs->cr3; + params->cr4 = sregs->cr4; + params->gdtr.limit = sregs->gdt.limit; + params->gdtr.base = sregs->gdt.base; + params->idtr.limit = sregs->idt.limit; + params->idtr.base = sregs->idt.base; + +TEST_ASSERT (params->cr0 !=0 ,"cr0 should not be 0" ); +TEST_ASSERT (params->cr3 !=0 ,"cr3 should not be 0" ); +TEST_ASSERT (params->cr4 !=0 ,"cr4 should not be 0" ); +TEST_ASSERT (params->gdtr.base !=0 ,"gdt base address should not be 0" ); +} + +static void load_td_boot_parameters (struct td_boot_parameters *params, +struct kvm_vcpu *vcpu,void *guest_code) +{ +struct kvm_sregs sregs; + +/* Assemble parameters in sregs */ +memset (&sregs,0 ,sizeof (struct kvm_sregs )); +vcpu_setup_mode_sregs (vcpu->vm, &sregs); +tdx_apply_cr4_restrictions (&sregs); +kvm_setup_idt (vcpu->vm, &sregs.idt); + +if (!params->cr0) +load_td_common_parameters (params, &sregs); + +load_td_per_vcpu_parameters (params, &sregs, vcpu, guest_code); +} + +/** +* Adds a vCPU to a TD (Trusted Domain) with minimum defaults. It will not set +* up any general purpose registers as they will be initialized by the TDX. In +* TDX, vCPUs RIP is set to 0xFFFFFFF0. See Intel TDX EAS Section "Initial State +* of Guest GPRs" for more information on vCPUs initial register values when +* entering the TD first time. +* +* Input Args: +* vm - Virtual Machine +* vcpuid - The id of the VCPU to add to the VM. +*/ +struct kvm_vcpu *td_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id,void *guest_code) +{ +struct kvm_vcpu *vcpu; + +/* +* TD setup will not use the value of rip set in vm_vcpu_add anyway, so +* NULL can be used for guest_code. +*/ + vcpu =vm_vcpu_add (vm, vcpu_id,NULL ); + +tdx_td_vcpu_init (vcpu); + +load_td_boot_parameters (addr_gpa2hva (vm,TD_BOOT_PARAMETERS_GPA ), + vcpu, guest_code); + +return vcpu; +} + +/** +* Iterate over set ranges within sparsebit @s. In each iteration, +* @range_begin and @range_end will take the beginning and end of the set range, +* which are of type sparsebit_idx_t. +* +* For example, if the range [3, 7] (inclusive) is set, within the iteration, +* @range_begin will take the value 3 and @range_end will take the value 7. +* +* Ensure that there is at least one bit set before using this macro with +* sparsebit_any_set(), because sparsebit_first_set() will abort if none are +* set. +*/ +#define sparsebit_for_each_set_range (s, range_begin, range_end) \ + for (range_begin = sparsebit_first_set(s), \ + range_end = sparsebit_next_clear(s, range_begin) - 1; \ + range_begin && range_end; \ + range_begin = sparsebit_next_set(s, range_end), \ + range_end = sparsebit_next_clear(s, range_begin) - 1) +/* +* sparsebit_next_clear() can return 0 if [x, 2**64-1] are all set, and the -1 +* would then cause an underflow back to 2**64 - 1. This is expected and +* correct. +* +* If the last range in the sparsebit is [x, y] and we try to iterate, +* sparsebit_next_set() will return 0, and sparsebit_next_clear() will try and +* find the first range, but that's correct because the condition expression +* would cause us to quit the loop. +*/ + +static void load_td_memory_region (struct kvm_vm *vm, +struct userspace_mem_region *region) +{ +const struct sparsebit *pages = region->protected_phy_pages; +const uint64_t hva_base = region->region.userspace_addr; +const vm_paddr_t gpa_base = region->region.guest_phys_addr; +const sparsebit_idx_t lowest_page_in_region = gpa_base >> + vm->page_shift; + +sparsebit_idx_t i; +sparsebit_idx_t j; + +if (!sparsebit_any_set (pages)) +return ; + +sparsebit_for_each_set_range (pages, i, j) { +const uint64_t size_to_load = (j - i +1 ) * vm->page_size; +const uint64_t offset = + (i - lowest_page_in_region) * vm->page_size; +const uint64_t hva = hva_base + offset; +const uint64_t gpa = gpa_base + offset; +void *source_addr; + +/* +* KVM_TDX_INIT_MEM_REGION ioctl cannot encrypt memory in place, +* hence we have to make a copy if there's only one backing +* memory source +*/ + source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , +MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); +TEST_ASSERT ( + source_addr, +"Could not allocate memory for loading memory region" ); + +memcpy (source_addr, (void *)hva, size_to_load); + +tdx_init_mem_region (vm, source_addr, gpa, size_to_load); + +munmap (source_addr, size_to_load); + } +} + +static void load_td_private_memory (struct kvm_vm *vm) +{ +int ctr; +struct userspace_mem_region *region; + +hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) { +load_td_memory_region (vm, region);
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 359
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +10
-0+ } +} + +struct kvm_vm *td_create (void ) +{ +struct vm_shape shape; + + shape.mode =VM_MODE_DEFAULT ; + shape.type =KVM_X86_TDX_VM ; +return ____vm_create (shape);
Nit:
init shape to 0s:
struct vm_shape shape = {};
Pass pointer of share to ____vm_create() instead:____vm_create(&shape)
Quoted 75 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +75
-0+} + +static void td_setup_boot_code (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_code_allocation =round_up (TD_BOOT_CODE_SIZE ,PAGE_SIZE ); +vm_paddr_t boot_code_base_gpa =FOUR_GIGABYTES_GPA - boot_code_allocation; +size_t npages =DIV_ROUND_UP (boot_code_allocation,PAGE_SIZE ); + +vm_userspace_mem_region_add (vm, src_type, boot_code_base_gpa,1 , npages, +KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, boot_code_allocation, boot_code_base_gpa,1 ); +TEST_ASSERT_EQ (addr, boot_code_base_gpa); + +load_td_boot_code (vm); +} + +static size_t td_boot_parameters_size (void ) +{ +int max_vcpus =kvm_check_cap (KVM_CAP_MAX_VCPUS ); +size_t total_per_vcpu_parameters_size = + max_vcpus *sizeof (struct td_per_vcpu_parameters ); + +return sizeof (struct td_boot_parameters ) + total_per_vcpu_parameters_size; +} + +static void td_setup_boot_parameters (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type) +{ +vm_vaddr_t addr; +size_t boot_params_size =td_boot_parameters_size (); +int npages =DIV_ROUND_UP (boot_params_size,PAGE_SIZE ); +size_t total_size = npages *PAGE_SIZE ; + +vm_userspace_mem_region_add (vm, src_type,TD_BOOT_PARAMETERS_GPA ,2 , + npages,KVM_MEM_PRIVATE ); + addr =vm_vaddr_alloc_1to1 (vm, total_size,TD_BOOT_PARAMETERS_GPA ,2 ); +TEST_ASSERT_EQ (addr,TD_BOOT_PARAMETERS_GPA ); +} + +void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type, +uint64_t attributes) +{ +uint64_t nr_pages_required; + +tdx_enable_capabilities (vm); + +tdx_configure_memory_encryption (vm); + +tdx_td_init (vm, attributes); + + nr_pages_required =vm_nr_pages_required (VM_MODE_DEFAULT ,1 ,0 ); + +/* +* Add memory (add 0th memslot) for TD. This will be used to setup the +* CPU (provide stack space for the CPU) and to load the elf file. +*/ +vm_userspace_mem_region_add (vm, src_type,0 ,0 , nr_pages_required, +KVM_MEM_PRIVATE ); + +kvm_vm_elf_load (vm, program_invocation_name); + +vm_init_descriptor_tables (vm); + +td_setup_boot_code (vm, src_type); +td_setup_boot_parameters (vm, src_type); +} + +void td_finalize (struct kvm_vm *vm) +{ +sync_exception_handlers_to_guest (vm); + +load_td_private_memory (vm); + +tdx_td_finalizemr (vm); +}
Re: [RFC PATCH v5 05/29] KVM: selftests: Add helper functions to create TDX VMs
Thank you for your other comments!
Quoted 14 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c line 191
Quoted 11 lines
<snip>
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +9
-0+static void load_td_per_vcpu_parameters (struct td_boot_parameters *params, +struct kvm_sregs *sregs, +struct kvm_vcpu *vcpu, +void *guest_code) +{ +/* Store vcpu_index to match what the TDX module would store internally */ +static uint32_t vcpu_index; + +struct td_per_vcpu_parameters *vcpu_params = ¶ms->per_vcpu[vcpu_index];I think we can use
vcpu->idin place ofvcpu_indexin this function, thus removingvcpu_index
td_per_vcpu_parameters is used in the selftest setup code (see tools/testing/selftests/kvm/lib/x86_64/tdx/td_boot.S), (read via ESI) to access the set of parameters belonging to the vcpu running the selftest code, based on vcpu_index.
ESI is used because according to the TDX base spec, RSI contains the vcpu index, which starts "from 0 and allocated sequentially on each successful TDH.VP.INIT".
Hence, vcpu_index is set up to be static and is incremented once every time load_td_per_vcpu_parameters() is called, which is once every time td_vcpu_add() is called, which is aligned with the TDX base spec.
vcpu->id can be specified by the user when vm_vcpu_add() is called, but that may not be the same as vcpu_index.
Quoted 17 lines
Quoted 17 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c new file +15
-0+ +TEST_ASSERT (vcpu->initial_stack_addr !=0 , +"initial stack address should not be 0" ); +TEST_ASSERT (vcpu->initial_stack_addr <=0xffffffff , +"initial stack address must fit in 32 bits" ); +TEST_ASSERT ((uint64_t )guest_code <=0xffffffff , +"guest_code must fit in 32 bits" ); +TEST_ASSERT (sregs->cs.selector !=0 ,"cs.selector should not be 0" ); + + vcpu_params->esp_gva = (uint32_t )(uint64_t )vcpu->initial_stack_addr; + vcpu_params->ljmp_target.eip_gva = (uint32_t )(uint64_t )guest_code; + vcpu_params->ljmp_target.code64_sel = sregs->cs.selector; + + vcpu_index++; +}
RFC PATCH v5 6/29 KVM: selftests: TDX: Use KVM_TDX_CAPABILITIES to validate TDs' attribute configuration
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
This also exercises the KVM_TDX_CAPABILITIES ioctl.
--- .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 69 ++++++++++++++++++- 1 file changed, 66 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +66 -3
@@ -27,10 +27,9 @@ static char *tdx_cmd_str[] = { };#define TDX_MAX_CMD_STR (ARRAY_SIZE(tdx_cmd_str)) -static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +static int _tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) {struct kvm_tdx_cmd tdx_cmd; -int r;TEST_ASSERT (ioctl_no <TDX_MAX_CMD_STR ,"Unknown TDX CMD : %d\n" , ioctl_no);
@@ -40,11 +39,58 @@ static void tdx_ioctl(int fd, int ioctl_no, uint32_t flags, void *data) tdx_cmd.flags = flags; tdx_cmd.data = (uint64_t )data; - r =ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +return ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +} + +static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +{ +int r; + + r =_tdx_ioctl (fd, ioctl_no, flags, data);TEST_ASSERT (r ==0 ,"%s failed: %d %d" , tdx_cmd_str[ioctl_no], r, errno); } +static struct kvm_tdx_capabilities *tdx_read_capabilities (struct kvm_vm *vm) +{ +int i; +int rc =-1 ; +int nr_cpuid_configs =4 ; +struct kvm_tdx_capabilities *tdx_cap =NULL ; + +do { + nr_cpuid_configs *=2 ; + + tdx_cap =realloc ( + tdx_cap,sizeof (*tdx_cap) + + nr_cpuid_configs *sizeof (*tdx_cap->cpuid_configs)); +TEST_ASSERT (tdx_cap !=NULL , +"Could not allocate memory for tdx capability nr_cpuid_configs %d\n" , + nr_cpuid_configs); + + tdx_cap->nr_cpuid_configs = nr_cpuid_configs; + rc =_tdx_ioctl (vm->fd,KVM_TDX_CAPABILITIES ,0 , tdx_cap); + }while (rc <0 && errno ==E2BIG ); + +TEST_ASSERT (rc ==0 ,"KVM_TDX_CAPABILITIES failed: %d %d" , + rc, errno); + +pr_debug ("tdx_cap: attrs: fixed0 0x%016llx fixed1 0x%016llx\n" +"tdx_cap: xfam fixed0 0x%016llx fixed1 0x%016llx\n" , + tdx_cap->attrs_fixed0, tdx_cap->attrs_fixed1, + tdx_cap->xfam_fixed0, tdx_cap->xfam_fixed1); + +for (i =0 ; i < tdx_cap->nr_cpuid_configs; i++) { +const struct kvm_tdx_cpuid_config *config = + &tdx_cap->cpuid_configs[i]; +pr_debug ("cpuid config[%d]: leaf 0x%x sub_leaf 0x%x eax 0x%08x ebx 0x%08x ecx 0x%08x edx 0x%08x\n" , + i, config->leaf, config->sub_leaf, + config->eax, config->ebx, config->ecx, config->edx); + } + +return tdx_cap; +} +#define XFEATURE_MASK_CET (XFEATURE_MASK_CET_USER | XFEATURE_MASK_CET_KERNEL)static void tdx_apply_cpuid_restrictions (struct kvm_cpuid2 *cpuid_data)
@@ -78,6 +124,21 @@ static void tdx_apply_cpuid_restrictions(struct kvm_cpuid2 *cpuid_data) } } +static void tdx_check_attributes (struct kvm_vm *vm,uint64_t attributes) +{ +struct kvm_tdx_capabilities *tdx_cap; + + tdx_cap =tdx_read_capabilities (vm); + +/* TDX spec: any bits 0 in attrs_fixed0 must be 0 in attributes */ +TEST_ASSERT_EQ (attributes & ~tdx_cap->attrs_fixed0,0 ); + +/* TDX spec: any bits 1 in attrs_fixed1 must be 1 in attributes */ +TEST_ASSERT_EQ (attributes & tdx_cap->attrs_fixed1, tdx_cap->attrs_fixed1); + +free (tdx_cap); +} +static void tdx_td_init (struct kvm_vm *vm,uint64_t attributes) {const struct kvm_cpuid2 *cpuid;
@@ -91,6 +152,8 @@ static void tdx_td_init(struct kvm_vm *vm, uint64_t attributes)memset (init_vm,0 ,sizeof (*init_vm));memcpy (&init_vm->cpuid, cpuid,kvm_cpuid2_size (cpuid->nent)); +tdx_check_attributes (vm, attributes); + init_vm->attributes = attributes;tdx_apply_cpuid_restrictions (&init_vm->cpuid);
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 06/29] KVM: selftests: TDX: Use KVM_TDX_CAPABILITIES to validate TDs' attribute configuration
Quoted 11 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
This also exercises the
KVM_TDX_CAPABILITIESioctl.Suggested-by Isaku Yamahata <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 69 ++++++++++++++++++- 1 file changed, 66 insertions(+), 3 deletions(-)
Nit: Can also dump 'supported_gpaw' in tdx_read_capabilities().
Quoted 108 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +66
-3@@ -27,10 +27,9 @@ static char *tdx_cmd_str[] = { };#define TDX_MAX_CMD_STR (ARRAY_SIZE(tdx_cmd_str)) -static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +static int _tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) {struct kvm_tdx_cmd tdx_cmd; -int r;TEST_ASSERT (ioctl_no <TDX_MAX_CMD_STR ,"Unknown TDX CMD : %d\n" , ioctl_no);@@ -40,11 +39,58 @@ static void tdx_ioctl(int fd, int ioctl_no, uint32_t flags, void *data) tdx_cmd.flags = flags; tdx_cmd.data = (uint64_t )data; - r =ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +return ioctl (fd,KVM_MEMORY_ENCRYPT_OP , &tdx_cmd); +} + +static void tdx_ioctl (int fd,int ioctl_no,uint32_t flags,void *data) +{ +int r; + + r =_tdx_ioctl (fd, ioctl_no, flags, data);TEST_ASSERT (r ==0 ,"%s failed: %d %d" , tdx_cmd_str[ioctl_no], r, errno); } +static struct kvm_tdx_capabilities *tdx_read_capabilities (struct kvm_vm *vm) +{ +int i; +int rc =-1 ; +int nr_cpuid_configs =4 ; +struct kvm_tdx_capabilities *tdx_cap =NULL ; + +do { + nr_cpuid_configs *=2 ; + + tdx_cap =realloc ( + tdx_cap,sizeof (*tdx_cap) + + nr_cpuid_configs *sizeof (*tdx_cap->cpuid_configs)); +TEST_ASSERT (tdx_cap !=NULL , +"Could not allocate memory for tdx capability nr_cpuid_configs %d\n" , + nr_cpuid_configs); + + tdx_cap->nr_cpuid_configs = nr_cpuid_configs; + rc =_tdx_ioctl (vm->fd,KVM_TDX_CAPABILITIES ,0 , tdx_cap); + }while (rc <0 && errno ==E2BIG ); + +TEST_ASSERT (rc ==0 ,"KVM_TDX_CAPABILITIES failed: %d %d" , + rc, errno); + +pr_debug ("tdx_cap: attrs: fixed0 0x%016llx fixed1 0x%016llx\n" +"tdx_cap: xfam fixed0 0x%016llx fixed1 0x%016llx\n" , + tdx_cap->attrs_fixed0, tdx_cap->attrs_fixed1, + tdx_cap->xfam_fixed0, tdx_cap->xfam_fixed1); + +for (i =0 ; i < tdx_cap->nr_cpuid_configs; i++) { +const struct kvm_tdx_cpuid_config *config = + &tdx_cap->cpuid_configs[i]; +pr_debug ("cpuid config[%d]: leaf 0x%x sub_leaf 0x%x eax 0x%08x ebx 0x%08x ecx 0x%08x edx 0x%08x\n" , + i, config->leaf, config->sub_leaf, + config->eax, config->ebx, config->ecx, config->edx); + } + +return tdx_cap; +} +#define XFEATURE_MASK_CET (XFEATURE_MASK_CET_USER | XFEATURE_MASK_CET_KERNEL)static void tdx_apply_cpuid_restrictions (struct kvm_cpuid2 *cpuid_data)@@ -78,6 +124,21 @@ static void tdx_apply_cpuid_restrictions(struct kvm_cpuid2 *cpuid_data) } } +static void tdx_check_attributes (struct kvm_vm *vm,uint64_t attributes) +{ +struct kvm_tdx_capabilities *tdx_cap; + + tdx_cap =tdx_read_capabilities (vm); + +/* TDX spec: any bits 0 in attrs_fixed0 must be 0 in attributes */ +TEST_ASSERT_EQ (attributes & ~tdx_cap->attrs_fixed0,0 ); + +/* TDX spec: any bits 1 in attrs_fixed1 must be 1 in attributes */ +TEST_ASSERT_EQ (attributes & tdx_cap->attrs_fixed1, tdx_cap->attrs_fixed1); + +free (tdx_cap); +} +static void tdx_td_init (struct kvm_vm *vm,uint64_t attributes) {const struct kvm_cpuid2 *cpuid;@@ -91,6 +152,8 @@ static void tdx_td_init(struct kvm_vm *vm, uint64_t attributes)memset (init_vm,0 ,sizeof (*init_vm));memcpy (&init_vm->cpuid, cpuid,kvm_cpuid2_size (cpuid->nent)); +tdx_check_attributes (vm, attributes); + init_vm->attributes = attributes;tdx_apply_cpuid_restrictions (&init_vm->cpuid);
RFC PATCH v5 7/29 KVM: selftests: TDX: Update load_td_memory_region for VM memory backed by guest memfd
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
If guest memory is backed by restricted memfd
+ UPM is being used, hence encrypted memory region has to be registered
+ Can avoid making a copy of guest memory before getting TDX to initialize the memory region
--- .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 41 +++++++++++++++---- 1 file changed, 32 insertions(+), 9 deletions(-)
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +32 -9
@@ -192,6 +192,21 @@ static void tdx_td_finalizemr(struct kvm_vm *vm)tdx_ioctl (vm->fd,KVM_TDX_FINALIZE_VM ,0 ,NULL ); } +/* +* Other ioctls +*/ + +/** +* Register a memory region that may contain encrypted data in KVM. +*/ +static void register_encrypted_memory_region ( +struct kvm_vm *vm,struct userspace_mem_region *region) +{ +vm_set_memory_attributes (vm, region->region.guest_phys_addr, + region->region.memory_size, +KVM_MEMORY_ATTRIBUTE_PRIVATE ); +} +/* * TD creation/setup/finalization */
@@ -376,30 +391,38 @@ static void load_td_memory_region(struct kvm_vm *vm,if (!sparsebit_any_set (pages))return ; + +if (region->region.guest_memfd !=-1 ) +register_encrypted_memory_region (vm, region); +sparsebit_for_each_set_range (pages, i, j) {const uint64_t size_to_load = (j - i +1 ) * vm->page_size;const uint64_t offset = (i - lowest_page_in_region) * vm->page_size;const uint64_t hva = hva_base + offset;const uint64_t gpa = gpa_base + offset; -void *source_addr; +void *source_addr = (void *)hva;/* * KVM_TDX_INIT_MEM_REGION ioctl cannot encrypt memory in place, * hence we have to make a copy if there's only one backing * memory source */ - source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , -MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); -TEST_ASSERT ( - source_addr, -"Could not allocate memory for loading memory region" ); - -memcpy (source_addr, (void *)hva, size_to_load); +if (region->region.guest_memfd ==-1 ) { + source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , +MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); +TEST_ASSERT ( + source_addr, +"Could not allocate memory for loading memory region" ); + +memcpy (source_addr, (void *)hva, size_to_load); +memset ((void *)hva,0 , size_to_load); + }tdx_init_mem_region (vm, source_addr, gpa, size_to_load); -munmap (source_addr, size_to_load); +if (region->region.guest_memfd ==-1 ) +munmap (source_addr, size_to_load); } }
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 07/29] KVM: selftests: TDX: Update load_td_memory_region for VM memory backed by guest memfd
Quoted 78 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
If guest memory is backed by restricted memfd
+ UPM is being used, hence encrypted memory region has to be registered
+ Can avoid making a copy of guest memory before getting TDX to initialize the memory regionSigned-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 41 +++++++++++++++---- 1 file changed, 32 insertions(+), 9 deletions(-)tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +27
-8@@ -192,6 +192,21 @@ static void tdx_td_finalizemr(struct kvm_vm *vm)tdx_ioctl (vm->fd,KVM_TDX_FINALIZE_VM ,0 ,NULL ); } +/* +* Other ioctls +*/ + +/** +* Register a memory region that may contain encrypted data in KVM. +*/ +static void register_encrypted_memory_region ( +struct kvm_vm *vm,struct userspace_mem_region *region) +{ +vm_set_memory_attributes (vm, region->region.guest_phys_addr, + region->region.memory_size, +KVM_MEMORY_ATTRIBUTE_PRIVATE ); +} +/* * TD creation/setup/finalization */ @@ -376,30 +391,38 @@ static void load_td_memory_region(struct kvm_vm *vm,if (!sparsebit_any_set (pages))return ; + +if (region->region.guest_memfd !=-1 ) +register_encrypted_memory_region (vm, region); +sparsebit_for_each_set_range (pages, i, j) {const uint64_t size_to_load = (j - i +1 ) * vm->page_size;const uint64_t offset = (i - lowest_page_in_region) * vm->page_size;const uint64_t hva = hva_base + offset;const uint64_t gpa = gpa_base + offset; -void *source_addr; +void *source_addr = (void *)hva;/* * KVM_TDX_INIT_MEM_REGION ioctl cannot encrypt memory in place, * hence we have to make a copy if there's only one backing * memory source */ - source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , -MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); -TEST_ASSERT ( - source_addr, -"Could not allocate memory for loading memory region" ); - -memcpy (source_addr, (void *)hva, size_to_load); +if (region->region.guest_memfd ==-1 ) { + source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , +MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); +TEST_ASSERT ( + source_addr, +"Could not allocate memory for loading memory region" ); +
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c static void load_td_memory_region(struct kvm_vm *vm, · line 426
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +5
-1+memcpy (source_addr, (void *)hva, size_to_load); +memset ((void *)hva,0 , size_to_load); + }tdx_init_mem_region (vm, source_addr, gpa, size_to_load); -munmap (source_addr, size_to_load); +if (region->region.guest_memfd ==-1 ) +munmap (source_addr, size_to_load); }
For memslot 0, 1, 2, when guest_memfd != -1,
is it possible to also munmap(mmap_start, mmap_size) after finish loading?
Quoted 6 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +0
-0}Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 07/29] KVM: selftests: TDX: Update load_td_memory_region for VM memory backed by guest memfd
Quoted 85 lines · Yan Zhao
Quoted 84 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
If guest memory is backed by restricted memfd
+ UPM is being used, hence encrypted memory region has to be registered
+ Can avoid making a copy of guest memory before getting TDX to initialize the memory regionSigned-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 41 +++++++++++++++---- 1 file changed, 32 insertions(+), 9 deletions(-)tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +30
-8@@ -192,6 +192,21 @@ static void tdx_td_finalizemr(struct kvm_vm *vm)tdx_ioctl (vm->fd,KVM_TDX_FINALIZE_VM ,0 ,NULL ); } +/* +* Other ioctls +*/ + +/** +* Register a memory region that may contain encrypted data in KVM. +*/ +static void register_encrypted_memory_region ( +struct kvm_vm *vm,struct userspace_mem_region *region) +{ +vm_set_memory_attributes (vm, region->region.guest_phys_addr, + region->region.memory_size, +KVM_MEMORY_ATTRIBUTE_PRIVATE ); +} +/* * TD creation/setup/finalization */ @@ -376,30 +391,38 @@ static void load_td_memory_region(struct kvm_vm *vm,if (!sparsebit_any_set (pages))return ; + +if (region->region.guest_memfd !=-1 ) +register_encrypted_memory_region (vm, region); +sparsebit_for_each_set_range (pages, i, j) {const uint64_t size_to_load = (j - i +1 ) * vm->page_size;const uint64_t offset = (i - lowest_page_in_region) * vm->page_size;const uint64_t hva = hva_base + offset;const uint64_t gpa = gpa_base + offset; -void *source_addr; +void *source_addr = (void *)hva;/* * KVM_TDX_INIT_MEM_REGION ioctl cannot encrypt memory in place, * hence we have to make a copy if there's only one backing * memory source */ - source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , -MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); -TEST_ASSERT ( - source_addr, -"Could not allocate memory for loading memory region" ); - -memcpy (source_addr, (void *)hva, size_to_load); +if (region->region.guest_memfd ==-1 ) { + source_addr =mmap (NULL , size_to_load,PROT_READ |PROT_WRITE , +MAP_ANONYMOUS |MAP_PRIVATE ,-1 ,0 ); +TEST_ASSERT ( + source_addr, +"Could not allocate memory for loading memory region" ); + +memcpy (source_addr, (void *)hva, size_to_load); +memset ((void *)hva,0 , size_to_load); + }tdx_init_mem_region (vm, source_addr, gpa, size_to_load);
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c static void load_td_memory_region(struct kvm_vm *vm, · line 426
Quoted 4 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +2
-1-munmap (source_addr, size_to_load); +if (region->region.guest_memfd ==-1 ) +munmap (source_addr, size_to_load); }For memslot 0, 1, 2, when
guest_memfd!= -1,
is it possible to alsomunmap(mmap_start, mmap_size)after finish loading?
Thank you for your review!
Did you mean "possible" as in whether it is "correct" to do munmap() for the rest of the earlier memslots containing non-test-code?
It is correct because the munmap() just deallocates memory that was recently allocated in mmap() in this same change. The memory set up for the VM is not affected.
Hope that answers your question, and here's some further detail, hope this helps too:
load_td_memory_region() loads a memory region into a TD by calling the KVM_TDX_INIT_MEM_REGION ioctl, which copies (and encrypts) the data in an existing memory region into TD private memory for the TD to use.
In these selftests, we use the KVM selftest framework to set up a TD's memory as if it were a regular VM, and then use this function to copy+encrypt the memory that is already set up for the TD. This lets us re-use most of the code from the KVM selftest framework for TDs, which is extremely useful for setting up page tables, exception handlers, etc for the TD. These key pieces of memory setup are in the memslots with smaller indices, as you pointed out.
KVM_TDX_INIT_MEM_REGION ioctl uses the provided gpa and struct kvm to look up the destination address, and uses source_addr as the source address for the copying.
If we are not using guest_memfd (region->region.guest_memfd == -1), then we need to make the source and destination address different by copying the contents at the source address somewhere else for the call to tdx_init_mem_region(). That is what the mmap() is doing. This temporary buffer then needs to be freed, hence the munmap(). Without this copying, the destination address for the ioctl's copy would be the same as the source address, since those very same pages are provided in the memslot for this memory region.
If we are using guest_memfd, then the destination address for the ioctl's copy will be taken from the guest_memfd, which is already different from the source address, hence we can skip the copying.
Quoted 6 lines
Quoted 6 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +0
-0}Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 07/29] KVM: selftests: TDX: Update load_td_memory_region for VM memory backed by guest memfd
Quoted 29 lines · Ackerley Tng
Quoted 10 lines · Yan Zhao
Quoted 9 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
If guest memory is backed by restricted memfd
+ UPM is being used, hence encrypted memory region has to be registered
+ Can avoid making a copy of guest memory before getting TDX to initialize the memory regionQuoted 5 lines
Quoted 1 line
<snip>
For memslot 0, 1, 2, when
guest_memfd!= -1,
is it possible to alsomunmap(mmap_start, mmap_size)after finish loading?Thank you for your review!
Did you mean "possible" as in whether it is "correct" to do
munmap()for the rest of the earlier memslots containing non-test-code?It is correct because the
munmap()just deallocates memory that was recently allocated inmmap()in this same change. The memory set up for the VM is not affected.<snip>
Quoted 9 lines
If we are not using
guest_memfd(region->region.guest_memfd== -1), then we need to make the source and destination address different by copying the contents at the source address somewhere else for the call totdx_init_mem_region(). That is what themmap()is doing. This temporary buffer then needs to be freed, hence themunmap(). Without this copying, the destination address for the ioctl's copy would be the same as the source address, since those very same pages are provided in the memslot for this memory region.
Update on this:
Since TDX requires the use of guest_memfd, this patch will be simplified in the next revision.
The checks for region->region.guest_memfd != -1 will be removed, and there will be no need to do any mmap() or munmap(), so those will be removed as well.
Quoted 11 lines
If we are using
guest_memfd, then the destination address for the ioctl's copy will be taken from theguest_memfd, which is already different from the source address, hence we can skip the copying.Quoted 6 lines
Quoted 6 lines
}
Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 8/29 KVM: selftests: TDX: Add TDX lifecycle test
In reply to Sagi ShaharFrom: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c
tools/testing/selftests/kvm/Makefile +4 -0
@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c
@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_test
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +35 -0
@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 + +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +12 -0
@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h new file +52 -0
52 lines not on this page · raw message
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +90 -0
90 lines not on this page · raw message
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c new file +27 -0
@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "tdx/tdcall.h" +#include "tdx/tdx.h" + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r10 =TDX_HYPERCALL_STANDARD , + .r11 =TDG_VP_VMCALL_INSTRUCTION_IO , + .r12 = size, + .r13 = write, + .r14 = port, + }; + +if (write) + args.r15 = *data; + + ret =__tdx_hypercall (&args, write ?0 :TDX_HCALL_HAS_OUTPUT ); + +if (!write) + *data = args.r11; + +return ret; +}
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1 -0
@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 ); }static void tdx_configure_memory_encryption (struct kvm_vm *vm)
tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c new file +34 -0
@@ -0,0 +1,34 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <stdbool.h> +#include <stdint.h> +#include <stdlib.h> +#include <sys/wait.h> +#include <unistd.h> + +#include "kvm_util_base.h" +#include "tdx/tdx.h" +#include "tdx/test_util.h" + +void run_in_new_process (void (*func)(void )) +{ +if (fork () ==0 ) { +func (); +exit (0 ); + } +wait (NULL ); +} + +bool is_tdx_enabled (void ) +{ +return !!(kvm_check_cap (KVM_CAP_VM_TYPES ) &BIT (KVM_X86_TDX_VM )); +} + +void tdx_test_success (void ) +{ +uint64_t code =0 ; + +tdg_vp_vmcall_instruction_io (TDX_TEST_SUCCESS_PORT , +TDX_TEST_SUCCESS_SIZE , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , &code); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +45 -0
45 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
Hi Sagi,
Quoted 365 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.ctools/testing/selftests/kvm/Makefile +4
-0@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_testtools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +35
-0@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 + +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +12
-0@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h new file +52
-0@@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TEST_UTIL_H +#define SELFTEST_TDX_TEST_UTIL_H + +#include <stdbool.h> + +#include "tdcall.h" + +#define TDX_TEST_SUCCESS_PORT 0x30 +#define TDX_TEST_SUCCESS_SIZE 4 + +/** +* Assert that tdx_test_success() was called in the guest. +*/ +#define TDX_TEST_ASSERT_SUCCESS (VCPU ) \ + (TEST_ASSERT( \ + ((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == TDX_TEST_SUCCESS_PORT) && \ + ((VCPU)->run->io.size == TDX_TEST_SUCCESS_SIZE) && \ + ((VCPU)->run->io.direction == \ + TDG_VP_VMCALL_INSTRUCTION_IO_WRITE), \ + "Unexpected exit values while waiting for test completion: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction)) + +/** +* Run a test in a new process. +* +* There might be multiple tests we are running and if one test fails, it will +* prevent the subsequent tests to run due to how tests are failing with +* TEST_ASSERT function. The run_in_new_process function will run a test in a +* new process context and wait for it to finish or fail to prevent TEST_ASSERT +* to kill the main testing process. +*/ +void run_in_new_process (void (*func)(void )); + +/** +* Verify that the TDX is supported by KVM. +*/ +bool is_tdx_enabled (void ); + +/** +* Report test success to userspace. +* +* Use TDX_TEST_ASSERT_SUCCESS() to assert that this function was called in the +* guest. +*/ +void tdx_test_success (void ); + +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +90
-0@@ -0,0 +1,90 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/coco/tdx/tdcall.S */ + +#define TDX_HYPERCALL_r10 0 /* offsetof(struct tdx_hypercall_args, r10) */ +#define TDX_HYPERCALL_r11 8 /* offsetof(struct tdx_hypercall_args, r11) */ +#define TDX_HYPERCALL_r12 16 /* offsetof(struct tdx_hypercall_args, r12) */ +#define TDX_HYPERCALL_r13 24 /* offsetof(struct tdx_hypercall_args, r13) */ +#define TDX_HYPERCALL_r14 32 /* offsetof(struct tdx_hypercall_args, r14) */ +#define TDX_HYPERCALL_r15 40 /* offsetof(struct tdx_hypercall_args, r15) */ + +/* + * Bitmasks of exposed registers (with VMM). + */ +#define TDX_R10 0x400 +#define TDX_R11 0x800 +#define TDX_R12 0x1000 +#define TDX_R13 0x2000 +#define TDX_R14 0x4000 +#define TDX_R15 0x8000 + +#define TDX_HCALL_HAS_OUTPUT 0x1 + +/* + * These registers are clobbered to hold arguments for each + * TDVMCALL. They are safe to expose to the VMM. + * Each bit in this mask represents a register ID. Bit field + * details can be found in TDX GHCI specification, section + * titled "TDCALL [TDG.VP.VMCALL] leaf". + */ +#define TDVMCALL_EXPOSE_REGS_MASK ( TDX_R10 | TDX_R11 | \ + TDX_R12 | TDX_R13 | \ + TDX_R14 | TDX_R15 ) + +.code64 +.section .text + +.globl __tdx_hypercall +.type __tdx_hypercall, @function +__tdx_hypercall: + /* Set up stack frame */ + push %rbp + movq %rsp, %rbp + + /* Save callee-saved GPRs as mandated by the x86_64 ABI */ + push %r15 + push %r14 + push %r13 + push %r12 + + /* Mangle function call ABI into TDCALL ABI: */ + /* Set TDCALL leaf ID (TDVMCALL (0)) in RAX */ + xor %eax, %eax + + /* Copy hypercall registers from arg struct: */ + movq TDX_HYPERCALL_r10(%rdi), %r10 + movq TDX_HYPERCALL_r11(%rdi), %r11 + movq TDX_HYPERCALL_r12(%rdi), %r12 + movq TDX_HYPERCALL_r13(%rdi), %r13 + movq TDX_HYPERCALL_r14(%rdi), %r14 + movq TDX_HYPERCALL_r15(%rdi), %r15 + + movl $TDVMCALL_EXPOSE_REGS_MASK, %ecx + + tdcall + + /* TDVMCALL leaf return code is in R10 */ + movq %r10, %rax + + /* Copy hypercall result registers to arg struct if needed */ + testq $TDX_HCALL_HAS_OUTPUT, %rsi + jz .Lout + + movq %r10, TDX_HYPERCALL_r10(%rdi) + movq %r11, TDX_HYPERCALL_r11(%rdi) + movq %r12, TDX_HYPERCALL_r12(%rdi) + movq %r13, TDX_HYPERCALL_r13(%rdi) + movq %r14, TDX_HYPERCALL_r14(%rdi) + movq %r15, TDX_HYPERCALL_r15(%rdi) +.Lout: + /* Restore callee-saved GPRs as mandated by the x86_64 ABI */ + pop %r12 + pop %r13 + pop %r14 + pop %r15 + + pop %rbp + ret + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c new file +27
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "tdx/tdcall.h" +#include "tdx/tdx.h" + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r10 =TDX_HYPERCALL_STANDARD , + .r11 =TDG_VP_VMCALL_INSTRUCTION_IO , + .r12 = size, + .r13 = write, + .r14 = port, + }; + +if (write) + args.r15 = *data; + + ret =__tdx_hypercall (&args, write ?0 :TDX_HCALL_HAS_OUTPUT ); + +if (!write) + *data = args.r11; + +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1
-0@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 ); }static void tdx_configure_memory_encryption (struct kvm_vm *vm)tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c new file +34
-0@@ -0,0 +1,34 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <stdbool.h> +#include <stdint.h> +#include <stdlib.h> +#include <sys/wait.h> +#include <unistd.h> + +#include "kvm_util_base.h" +#include "tdx/tdx.h" +#include "tdx/test_util.h" + +void run_in_new_process (void (*func)(void )) +{ +if (fork () ==0 ) { +func (); +exit (0 ); + } +wait (NULL ); +} + +bool is_tdx_enabled (void ) +{ +return !!(kvm_check_cap (KVM_CAP_VM_TYPES ) &BIT (KVM_X86_TDX_VM )); +} + +void tdx_test_success (void ) +{ +uint64_t code =0 ; + +tdg_vp_vmcall_instruction_io (TDX_TEST_SUCCESS_PORT , +TDX_TEST_SUCCESS_SIZE , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , &code); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +10
-0@@ -0,0 +1,45 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <signal.h> +#include "kvm_util_base.h" +#include "tdx/tdx_util.h" +#include "tdx/test_util.h" +#include "test_util.h" + +void guest_code_lifecycle (void ) +{
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c line 20
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +10
-0+tdx_test_success (); +} + +void verify_td_lifecycle (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 );
From a user point of view, this lifecycle test is very useful to me for vm creation/destruction time test, and I believe you have an enhanced version to specify the memory size. May I know if there is any plan to add that part too? And maybe allow the user to customize the memory size rather than a fixed size.
thanks,
Chenyu
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
In reply to Sagi ShaharQuoted 60 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +54
-0@@ -0,0 +1,90 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/coco/tdx/tdcall.S */ + +#define TDX_HYPERCALL_r10 0 /* offsetof(struct tdx_hypercall_args, r10) */ +#define TDX_HYPERCALL_r11 8 /* offsetof(struct tdx_hypercall_args, r11) */ +#define TDX_HYPERCALL_r12 16 /* offsetof(struct tdx_hypercall_args, r12) */ +#define TDX_HYPERCALL_r13 24 /* offsetof(struct tdx_hypercall_args, r13) */ +#define TDX_HYPERCALL_r14 32 /* offsetof(struct tdx_hypercall_args, r14) */ +#define TDX_HYPERCALL_r15 40 /* offsetof(struct tdx_hypercall_args, r15) */ + +/* + * Bitmasks of exposed registers (with VMM). + */ +#define TDX_R10 0x400 +#define TDX_R11 0x800 +#define TDX_R12 0x1000 +#define TDX_R13 0x2000 +#define TDX_R14 0x4000 +#define TDX_R15 0x8000 + +#define TDX_HCALL_HAS_OUTPUT 0x1 + +/* + * These registers are clobbered to hold arguments for each + * TDVMCALL. They are safe to expose to the VMM. + * Each bit in this mask represents a register ID. Bit field + * details can be found in TDX GHCI specification, section + * titled "TDCALL [TDG.VP.VMCALL] leaf". + */ +#define TDVMCALL_EXPOSE_REGS_MASK ( TDX_R10 | TDX_R11 | \ + TDX_R12 | TDX_R13 | \ + TDX_R14 | TDX_R15 ) + +.code64 +.section .text + +.globl __tdx_hypercall +.type __tdx_hypercall, @function +__tdx_hypercall: + /* Set up stack frame */ + push %rbp + movq %rsp, %rbp + + /* Save callee-saved GPRs as mandated by the x86_64 ABI */ + push %r15 + push %r14 + push %r13 + push %r12 + + /* Mangle function call ABI into TDCALL ABI: */ + /* Set TDCALL leaf ID (TDVMCALL (0)) in RAX */ + xor %eax, %eax + + /* Copy hypercall registers from arg struct: */
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S line 64
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +10
-0+ movq TDX_HYPERCALL_r10(%rdi), %r10 + movq TDX_HYPERCALL_r11(%rdi), %r11 + movq TDX_HYPERCALL_r12(%rdi), %r12 + movq TDX_HYPERCALL_r13(%rdi), %r13 + movq TDX_HYPERCALL_r14(%rdi), %r14 + movq TDX_HYPERCALL_r15(%rdi), %r15 + + movl $TDVMCALL_EXPOSE_REGS_MASK, %ecx + + tdcall
Looks there's a missing of definition for tdcall, and will produce below error:lib/x86_64/tdx/tdcall.S:65: Error: no such instruction: `tdcall'
I pulled the code https://github.com/googleprodkernel/linux-cc.git with branch tdx-selftests-rfc-v5.
Fixed by adding a line in tdcall.S in my side.
#define tdcall .byte 0x66,0x0f,0x01,0xcc
Quoted 25 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +25
-0+ + /* TDVMCALL leaf return code is in R10 */ + movq %r10, %rax + + /* Copy hypercall result registers to arg struct if needed */ + testq $TDX_HCALL_HAS_OUTPUT, %rsi + jz .Lout + + movq %r10, TDX_HYPERCALL_r10(%rdi) + movq %r11, TDX_HYPERCALL_r11(%rdi) + movq %r12, TDX_HYPERCALL_r12(%rdi) + movq %r13, TDX_HYPERCALL_r13(%rdi) + movq %r14, TDX_HYPERCALL_r14(%rdi) + movq %r15, TDX_HYPERCALL_r15(%rdi) +.Lout: + /* Restore callee-saved GPRs as mandated by the x86_64 ABI */ + pop %r12 + pop %r13 + pop %r14 + pop %r15 + + pop %rbp + ret + +/* Disable executable stack */
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
In reply to Sagi Shahartools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c static void tdx_enable_capabilities(struct kvm_vm *vm) · line 227
Quoted 9 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1
-0@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 );
This is not a must for TD life cycle?
Though I know, currently, the selftest will fail without setting this line, due to TD's default max vcpu count is -1.
But I guess it's an error.
https://lore.kernel.org/all/[email protected]/
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
In reply to Sagi ShaharQuoted 58 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.ctools/testing/selftests/kvm/Makefile +4
-0@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_testtools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +1
-0@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h line 11
Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +10
-0+/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1
Nit:
Probably we can define the following instead in test_util.c? /* Port I/O direction */
#define PORT_READ 0
#define PORT_WRITE 1
Then use them in place of TDG_VP_VMCALL_INSTRUCTION_IO_READ/TDG_VP_VMCALL_INSTRUCTION_IO_WRITE? which are too long
Quoted 30 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +24
-0+ +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +0
-0
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h line 7
Quoted 7 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +7
-0@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30
Nit:arch/x86/include/uapi/asm/vmx.h already exports the following define:
#define EXIT_REASON_IO_INSTRUCTION 30
Linux kernel example (arch/x86/coco/tdx/tdx.c):
static bool handle_in(struct pt_regs *regs, int size, int port)
{
struct tdx_module_args args = {
.r10 = TDX_HYPERCALL_STANDARD,
.r11 = hcall_func(EXIT_REASON_IO_INSTRUCTION),
.r12 = size,
.r13 = PORT_READ,
.r14 = port,
};So just like the kernel, here we can also use EXIT_REASON_IO_INSTRUCTION in place of TDG_VP_VMCALL_INSTRUCTION_IO, just need to do a '#include "vmx.h"' or '#include <asm/vmx.h>' to bring in the define
Quoted 271 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +5
-0+ +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h new file +52
-0@@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TEST_UTIL_H +#define SELFTEST_TDX_TEST_UTIL_H + +#include <stdbool.h> + +#include "tdcall.h" + +#define TDX_TEST_SUCCESS_PORT 0x30 +#define TDX_TEST_SUCCESS_SIZE 4 + +/** +* Assert that tdx_test_success() was called in the guest. +*/ +#define TDX_TEST_ASSERT_SUCCESS (VCPU ) \ + (TEST_ASSERT( \ + ((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == TDX_TEST_SUCCESS_PORT) && \ + ((VCPU)->run->io.size == TDX_TEST_SUCCESS_SIZE) && \ + ((VCPU)->run->io.direction == \ + TDG_VP_VMCALL_INSTRUCTION_IO_WRITE), \ + "Unexpected exit values while waiting for test completion: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction)) + +/** +* Run a test in a new process. +* +* There might be multiple tests we are running and if one test fails, it will +* prevent the subsequent tests to run due to how tests are failing with +* TEST_ASSERT function. The run_in_new_process function will run a test in a +* new process context and wait for it to finish or fail to prevent TEST_ASSERT +* to kill the main testing process. +*/ +void run_in_new_process (void (*func)(void )); + +/** +* Verify that the TDX is supported by KVM. +*/ +bool is_tdx_enabled (void ); + +/** +* Report test success to userspace. +* +* Use TDX_TEST_ASSERT_SUCCESS() to assert that this function was called in the +* guest. +*/ +void tdx_test_success (void ); + +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +90
-0@@ -0,0 +1,90 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/coco/tdx/tdcall.S */ + +#define TDX_HYPERCALL_r10 0 /* offsetof(struct tdx_hypercall_args, r10) */ +#define TDX_HYPERCALL_r11 8 /* offsetof(struct tdx_hypercall_args, r11) */ +#define TDX_HYPERCALL_r12 16 /* offsetof(struct tdx_hypercall_args, r12) */ +#define TDX_HYPERCALL_r13 24 /* offsetof(struct tdx_hypercall_args, r13) */ +#define TDX_HYPERCALL_r14 32 /* offsetof(struct tdx_hypercall_args, r14) */ +#define TDX_HYPERCALL_r15 40 /* offsetof(struct tdx_hypercall_args, r15) */ + +/* + * Bitmasks of exposed registers (with VMM). + */ +#define TDX_R10 0x400 +#define TDX_R11 0x800 +#define TDX_R12 0x1000 +#define TDX_R13 0x2000 +#define TDX_R14 0x4000 +#define TDX_R15 0x8000 + +#define TDX_HCALL_HAS_OUTPUT 0x1 + +/* + * These registers are clobbered to hold arguments for each + * TDVMCALL. They are safe to expose to the VMM. + * Each bit in this mask represents a register ID. Bit field + * details can be found in TDX GHCI specification, section + * titled "TDCALL [TDG.VP.VMCALL] leaf". + */ +#define TDVMCALL_EXPOSE_REGS_MASK ( TDX_R10 | TDX_R11 | \ + TDX_R12 | TDX_R13 | \ + TDX_R14 | TDX_R15 ) + +.code64 +.section .text + +.globl __tdx_hypercall +.type __tdx_hypercall, @function +__tdx_hypercall: + /* Set up stack frame */ + push %rbp + movq %rsp, %rbp + + /* Save callee-saved GPRs as mandated by the x86_64 ABI */ + push %r15 + push %r14 + push %r13 + push %r12 + + /* Mangle function call ABI into TDCALL ABI: */ + /* Set TDCALL leaf ID (TDVMCALL (0)) in RAX */ + xor %eax, %eax + + /* Copy hypercall registers from arg struct: */ + movq TDX_HYPERCALL_r10(%rdi), %r10 + movq TDX_HYPERCALL_r11(%rdi), %r11 + movq TDX_HYPERCALL_r12(%rdi), %r12 + movq TDX_HYPERCALL_r13(%rdi), %r13 + movq TDX_HYPERCALL_r14(%rdi), %r14 + movq TDX_HYPERCALL_r15(%rdi), %r15 + + movl $TDVMCALL_EXPOSE_REGS_MASK, %ecx + + tdcall + + /* TDVMCALL leaf return code is in R10 */ + movq %r10, %rax + + /* Copy hypercall result registers to arg struct if needed */ + testq $TDX_HCALL_HAS_OUTPUT, %rsi + jz .Lout + + movq %r10, TDX_HYPERCALL_r10(%rdi) + movq %r11, TDX_HYPERCALL_r11(%rdi) + movq %r12, TDX_HYPERCALL_r12(%rdi) + movq %r13, TDX_HYPERCALL_r13(%rdi) + movq %r14, TDX_HYPERCALL_r14(%rdi) + movq %r15, TDX_HYPERCALL_r15(%rdi) +.Lout: + /* Restore callee-saved GPRs as mandated by the x86_64 ABI */ + pop %r12 + pop %r13 + pop %r14 + pop %r15 + + pop %rbp + ret + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c new file +27
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "tdx/tdcall.h" +#include "tdx/tdx.h" + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r10 =TDX_HYPERCALL_STANDARD , + .r11 =TDG_VP_VMCALL_INSTRUCTION_IO , + .r12 = size, + .r13 = write, + .r14 = port, + }; + +if (write) + args.r15 = *data; + + ret =__tdx_hypercall (&args, write ?0 :TDX_HCALL_HAS_OUTPUT ); + +if (!write) + *data = args.r11; + +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1
-0@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 ); }static void tdx_configure_memory_encryption (struct kvm_vm *vm)tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c new file +34
-0@@ -0,0 +1,34 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <stdbool.h> +#include <stdint.h> +#include <stdlib.h> +#include <sys/wait.h> +#include <unistd.h> + +#include "kvm_util_base.h" +#include "tdx/tdx.h" +#include "tdx/test_util.h" + +void run_in_new_process (void (*func)(void )) +{ +if (fork () ==0 ) { +func (); +exit (0 ); + } +wait (NULL ); +} + +bool is_tdx_enabled (void ) +{ +return !!(kvm_check_cap (KVM_CAP_VM_TYPES ) &BIT (KVM_X86_TDX_VM )); +} + +void tdx_test_success (void ) +{ +uint64_t code =0 ; + +tdg_vp_vmcall_instruction_io (TDX_TEST_SUCCESS_PORT , +TDX_TEST_SUCCESS_SIZE , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , &code); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +21
-0@@ -0,0 +1,45 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <signal.h> +#include "kvm_util_base.h" +#include "tdx/tdx_util.h" +#include "tdx/test_util.h" +#include "test_util.h" + +void guest_code_lifecycle (void ) +{ +tdx_test_success (); +} + +void verify_td_lifecycle (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_lifecycle);
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c line 31
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +10
-0+td_finalize (vm); + +printf ("Verifying TD lifecycle:\n" ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +}
Nit:
All the functions used locally inside tdx_vm_tests.c can be declared static:
static void guest_code_lifecycle(void)
static void verify_td_lifecycle(void)
Quoted 14 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c new file +14
-0+ +int main (int argc,char **argv) +{ +setbuf (stdout,NULL ); + +if (!is_tdx_enabled ()) { +print_skip ("TDX is not supported by the KVM" ); +exit (KSFT_SKIP ); + } + +run_in_new_process (&verify_td_lifecycle); + +return 0 ; +}
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
Quoted 76 lines · Dongsheng X
Quoted 58 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.ctools/testing/selftests/kvm/Makefile +4
-0@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_testtools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +1
-0@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h line 11
Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +10
-0+/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1Nit:
Probably we can define the following instead intest_util.c? /* Port I/O direction */
#definePORT_READ0
#definePORT_WRITE1
Quoted 3 lines
Then use them in place of TDG_VP_VMCALL_INSTRUCTION_IO_READ/TDG_VP_VMCALL_INSTRUCTION_IO_WRITE? which are too long
I was actually thinking to align all the macro definitions with the definitions in the Intel GHCI Spec, so
3.9 TDG.VP.VMCALL<Instruction.IO>
becomes TDG_VP_VMCALL_INSTRUCTION_IO and then add suffixes READ and WRITE for the directions.
PORT_READ and PORT_WRITE seem a little too unspecific, but I agree that TDG_VP_VMCALL_INSTRUCTION_IO_READ/TDG_VP_VMCALL_INSTRUCTION_IO_WRITE are long.
Quoted 53 lines
Quoted 30 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +24
-0+ +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +0
-0tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h line 7
Quoted 7 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +7
-0@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30Nit:
arch/x86/include/uapi/asm/vmx.halready exports the following define:
#defineEXIT_REASON_IO_INSTRUCTION30Linux kernel example (
arch/x86/coco/tdx/tdx.c):
static boolhandle_in(struct pt_regs *regs, int size, int port){ struct tdx_module_args args = { .r10 = TDX_HYPERCALL_STANDARD, .r11 = hcall_func(EXIT_REASON_IO_INSTRUCTION), .r12 = size, .r13 = PORT_READ, .r14 = port, };
Quoted 3 lines
So just like the kernel, here we can also use
EXIT_REASON_IO_INSTRUCTIONin place ofTDG_VP_VMCALL_INSTRUCTION_IO, just need to do a '#include "vmx.h"' or '#include <asm/vmx.h>' to bring in the define
I think aligning macro definitions with the spec is better in this case.
It seems odd to be calling an EXIT_REASON_* when making a hypercall.
Later on in this patch series this macro is added
#define TDG_VP_VMCALL_VE_REQUEST_MMIO 48
which matches
3.7 TDG.VP.VMCALL<#VE.RequestMMIO>
in the Intel GHCI Spec.
The equivalent EXIT_REASON is EXIT_REASON_EPT_VIOLATION, which I feel doesn't carry the same meaning as an explicit request for MMIO, as in TDG_VP_VMCALL_VE_REQUEST_MMIO.
So I think even though the numbers are the same, they don't carry the same meaning and it's probably better to have different macro definitions.
Or we could define one in terms of the other?
Later on in this patch series other macros are also added, specific to TDX
#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000
#define TDG_VP_VMCALL_MAP_GPA 0x10001
#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003
which matches
3.1 TDG.VP.VMCALL<GetTdVmCallInfo>
3.2 TDG.VP.VMCALL<MapGPA>
3.4 TDG.VP.VMCALL<ReportFatalError>
in the Intel GHCI Spec.
It's nice to have the naming convention for all the VMCALLs line up. :)
Quoted 22 lines
Quoted 22 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +19
-0+ +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +void verify_td_lifecycle (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_lifecycle); +td_finalize (vm); + +printf ("Verifying TD lifecycle:\n" ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); +
Quoted 9 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h
Quoted 3 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +3
-0+kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +}Nit:
All the functions used locally insidetdx_vm_tests.ccan be declared static:
static voidguest_code_lifecycle(void)
static voidverify_td_lifecycle(void)
Will fix this, thanks!
Quoted 14 lines
Quoted 14 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +14
-0+ +int main (int argc,char **argv) +{ +setbuf (stdout,NULL ); + +if (!is_tdx_enabled ()) { +print_skip ("TDX is not supported by the KVM" ); +exit (KSFT_SKIP ); + } + +run_in_new_process (&verify_td_lifecycle); + +return 0 ; +}
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
In reply to Sagi ShaharQuoted 302 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.ctools/testing/selftests/kvm/Makefile +4
-0@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_testtools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +35
-0@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 + +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +12
-0@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h new file +52
-0@@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TEST_UTIL_H +#define SELFTEST_TDX_TEST_UTIL_H + +#include <stdbool.h> + +#include "tdcall.h" + +#define TDX_TEST_SUCCESS_PORT 0x30 +#define TDX_TEST_SUCCESS_SIZE 4 + +/** +* Assert that tdx_test_success() was called in the guest. +*/ +#define TDX_TEST_ASSERT_SUCCESS (VCPU ) \ + (TEST_ASSERT( \ + ((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == TDX_TEST_SUCCESS_PORT) && \ + ((VCPU)->run->io.size == TDX_TEST_SUCCESS_SIZE) && \ + ((VCPU)->run->io.direction == \ + TDG_VP_VMCALL_INSTRUCTION_IO_WRITE), \ + "Unexpected exit values while waiting for test completion: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction)) + +/** +* Run a test in a new process. +* +* There might be multiple tests we are running and if one test fails, it will +* prevent the subsequent tests to run due to how tests are failing with +* TEST_ASSERT function. The run_in_new_process function will run a test in a +* new process context and wait for it to finish or fail to prevent TEST_ASSERT +* to kill the main testing process. +*/ +void run_in_new_process (void (*func)(void )); + +/** +* Verify that the TDX is supported by KVM. +*/ +bool is_tdx_enabled (void ); + +/** +* Report test success to userspace. +* +* Use TDX_TEST_ASSERT_SUCCESS() to assert that this function was called in the +* guest. +*/ +void tdx_test_success (void ); + +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +90
-0@@ -0,0 +1,90 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/coco/tdx/tdcall.S */ + +#define TDX_HYPERCALL_r10 0 /* offsetof(struct tdx_hypercall_args, r10) */ +#define TDX_HYPERCALL_r11 8 /* offsetof(struct tdx_hypercall_args, r11) */ +#define TDX_HYPERCALL_r12 16 /* offsetof(struct tdx_hypercall_args, r12) */ +#define TDX_HYPERCALL_r13 24 /* offsetof(struct tdx_hypercall_args, r13) */ +#define TDX_HYPERCALL_r14 32 /* offsetof(struct tdx_hypercall_args, r14) */ +#define TDX_HYPERCALL_r15 40 /* offsetof(struct tdx_hypercall_args, r15) */ + +/* + * Bitmasks of exposed registers (with VMM). + */ +#define TDX_R10 0x400 +#define TDX_R11 0x800 +#define TDX_R12 0x1000 +#define TDX_R13 0x2000 +#define TDX_R14 0x4000 +#define TDX_R15 0x8000 + +#define TDX_HCALL_HAS_OUTPUT 0x1 + +/* + * These registers are clobbered to hold arguments for each + * TDVMCALL. They are safe to expose to the VMM. + * Each bit in this mask represents a register ID. Bit field + * details can be found in TDX GHCI specification, section + * titled "TDCALL [TDG.VP.VMCALL] leaf". + */ +#define TDVMCALL_EXPOSE_REGS_MASK ( TDX_R10 | TDX_R11 | \ + TDX_R12 | TDX_R13 | \ + TDX_R14 | TDX_R15 ) + +.code64 +.section .text + +.globl __tdx_hypercall +.type __tdx_hypercall, @function +__tdx_hypercall: + /* Set up stack frame */ + push %rbp + movq %rsp, %rbp + + /* Save callee-saved GPRs as mandated by the x86_64 ABI */ + push %r15 + push %r14 + push %r13 + push %r12 + + /* Mangle function call ABI into TDCALL ABI: */ + /* Set TDCALL leaf ID (TDVMCALL (0)) in RAX */ + xor %eax, %eax + + /* Copy hypercall registers from arg struct: */ + movq TDX_HYPERCALL_r10(%rdi), %r10 + movq TDX_HYPERCALL_r11(%rdi), %r11 + movq TDX_HYPERCALL_r12(%rdi), %r12 + movq TDX_HYPERCALL_r13(%rdi), %r13 + movq TDX_HYPERCALL_r14(%rdi), %r14 + movq TDX_HYPERCALL_r15(%rdi), %r15 + + movl $TDVMCALL_EXPOSE_REGS_MASK, %ecx + + tdcall + + /* TDVMCALL leaf return code is in R10 */ + movq %r10, %rax + + /* Copy hypercall result registers to arg struct if needed */ + testq $TDX_HCALL_HAS_OUTPUT, %rsi + jz .Lout + + movq %r10, TDX_HYPERCALL_r10(%rdi) + movq %r11, TDX_HYPERCALL_r11(%rdi) + movq %r12, TDX_HYPERCALL_r12(%rdi) + movq %r13, TDX_HYPERCALL_r13(%rdi) + movq %r14, TDX_HYPERCALL_r14(%rdi) + movq %r15, TDX_HYPERCALL_r15(%rdi) +.Lout: + /* Restore callee-saved GPRs as mandated by the x86_64 ABI */ + pop %r12 + pop %r13 + pop %r14 + pop %r15 + + pop %rbp + ret + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c new file +27
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "tdx/tdcall.h" +#include "tdx/tdx.h" + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r10 =TDX_HYPERCALL_STANDARD , + .r11 =TDG_VP_VMCALL_INSTRUCTION_IO , + .r12 = size, + .r13 = write, + .r14 = port, + }; + +if (write) + args.r15 = *data; + + ret =__tdx_hypercall (&args, write ?0 :TDX_HCALL_HAS_OUTPUT ); + +if (!write) + *data = args.r11; + +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +0
-0
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c static void tdx_enable_capabilities(struct kvm_vm *vm) · line 227
Quoted 4 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1
-0@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 );
Since TDX spec doesn't define max vCPUs, is it a good idea to fix it to 512 in this common code?
How about to move this line to the specific test case where you are actually verifying this capability?
For example, move it to PATCH v5 21/29] KVM: selftests: TDX: Add TDG.VP.INFO test
+ vm_enable_cap(vm, KVM_CAP_MAX_VCPUS, 512);
...
TEST_ASSERT_EQ(ret_max_vcpus, 512);
Re: [RFC PATCH v5 08/29] KVM: selftests: TDX: Add TDX lifecycle test
Quoted 317 lines · Zide
Quoted 302 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Adding a test to verify TDX lifecycle by creating a TD and running a dummy TDG.VP.VMCALL <Instruction.IO> inside it.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Co-developed-by Ackerley Tng <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 4 + .../selftests/kvm/include/x86_64/tdx/tdcall.h | 35 ++++++++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 12 +++ .../kvm/include/x86_64/tdx/test_util.h | 52 +++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 90 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 1 + .../selftests/kvm/lib/x86_64/tdx/test_util.c | 34 +++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 ++++++++++ 9 files changed, 300 insertions(+) create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h create mode 100644 tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c create mode 100644 tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_vm_tests.ctools/testing/selftests/kvm/Makefile +4
-0@@ -52,6 +52,9 @@ LIBKVM_x86_64 += lib/x86_64/vmx.c LIBKVM_x86_64 += lib/x86_64/sev.c LIBKVM_x86_64 += lib/x86_64/tdx/tdx_util.c LIBKVM_x86_64 += lib/x86_64/tdx/td_boot.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdcall.S +LIBKVM_x86_64 += lib/x86_64/tdx/tdx.c +LIBKVM_x86_64 += lib/x86_64/tdx/test_util.c LIBKVM_aarch64 += lib/aarch64/gic.c LIBKVM_aarch64 += lib/aarch64/gic_v3.c@@ -152,6 +155,7 @@ TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test +TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_testtools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h new file +35
-0@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/include/asm/shared/tdx.h */ + +#ifndef SELFTESTS_TDX_TDCALL_H +#define SELFTESTS_TDX_TDCALL_H + +#include <linux/bits.h> +#include <linux/types.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0 +#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 + +#define TDX_HCALL_HAS_OUTPUT BIT(0) + +#define TDX_HYPERCALL_STANDARD 0 + +/* +* Used in __tdx_hypercall() to pass down and get back registers' values of +* the TDCALL instruction when requesting services from the VMM. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_hypercall_args { +u64 r10; +u64 r11; +u64 r12; +u64 r13; +u64 r14; +u64 r15; +}; + +/* Used to request services from the VMM */ +u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); + +#endif // SELFTESTS_TDX_TDCALL_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h new file +12
-0@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TDX_H +#define SELFTEST_TDX_TDX_H + +#include <stdint.h> + +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data); + +#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h new file +52
-0@@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +#ifndef SELFTEST_TDX_TEST_UTIL_H +#define SELFTEST_TDX_TEST_UTIL_H + +#include <stdbool.h> + +#include "tdcall.h" + +#define TDX_TEST_SUCCESS_PORT 0x30 +#define TDX_TEST_SUCCESS_SIZE 4 + +/** +* Assert that tdx_test_success() was called in the guest. +*/ +#define TDX_TEST_ASSERT_SUCCESS (VCPU ) \ + (TEST_ASSERT( \ + ((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == TDX_TEST_SUCCESS_PORT) && \ + ((VCPU)->run->io.size == TDX_TEST_SUCCESS_SIZE) && \ + ((VCPU)->run->io.direction == \ + TDG_VP_VMCALL_INSTRUCTION_IO_WRITE), \ + "Unexpected exit values while waiting for test completion: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction)) + +/** +* Run a test in a new process. +* +* There might be multiple tests we are running and if one test fails, it will +* prevent the subsequent tests to run due to how tests are failing with +* TEST_ASSERT function. The run_in_new_process function will run a test in a +* new process context and wait for it to finish or fail to prevent TEST_ASSERT +* to kill the main testing process. +*/ +void run_in_new_process (void (*func)(void )); + +/** +* Verify that the TDX is supported by KVM. +*/ +bool is_tdx_enabled (void ); + +/** +* Report test success to userspace. +* +* Use TDX_TEST_ASSERT_SUCCESS() to assert that this function was called in the +* guest. +*/ +void tdx_test_success (void ); + +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S new file +90
-0@@ -0,0 +1,90 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* Adapted from arch/x86/coco/tdx/tdcall.S */ + +#define TDX_HYPERCALL_r10 0 /* offsetof(struct tdx_hypercall_args, r10) */ +#define TDX_HYPERCALL_r11 8 /* offsetof(struct tdx_hypercall_args, r11) */ +#define TDX_HYPERCALL_r12 16 /* offsetof(struct tdx_hypercall_args, r12) */ +#define TDX_HYPERCALL_r13 24 /* offsetof(struct tdx_hypercall_args, r13) */ +#define TDX_HYPERCALL_r14 32 /* offsetof(struct tdx_hypercall_args, r14) */ +#define TDX_HYPERCALL_r15 40 /* offsetof(struct tdx_hypercall_args, r15) */ + +/* + * Bitmasks of exposed registers (with VMM). + */ +#define TDX_R10 0x400 +#define TDX_R11 0x800 +#define TDX_R12 0x1000 +#define TDX_R13 0x2000 +#define TDX_R14 0x4000 +#define TDX_R15 0x8000 + +#define TDX_HCALL_HAS_OUTPUT 0x1 + +/* + * These registers are clobbered to hold arguments for each + * TDVMCALL. They are safe to expose to the VMM. + * Each bit in this mask represents a register ID. Bit field + * details can be found in TDX GHCI specification, section + * titled "TDCALL [TDG.VP.VMCALL] leaf". + */ +#define TDVMCALL_EXPOSE_REGS_MASK ( TDX_R10 | TDX_R11 | \ + TDX_R12 | TDX_R13 | \ + TDX_R14 | TDX_R15 ) + +.code64 +.section .text + +.globl __tdx_hypercall +.type __tdx_hypercall, @function +__tdx_hypercall: + /* Set up stack frame */ + push %rbp + movq %rsp, %rbp + + /* Save callee-saved GPRs as mandated by the x86_64 ABI */ + push %r15 + push %r14 + push %r13 + push %r12 + + /* Mangle function call ABI into TDCALL ABI: */ + /* Set TDCALL leaf ID (TDVMCALL (0)) in RAX */ + xor %eax, %eax + + /* Copy hypercall registers from arg struct: */ + movq TDX_HYPERCALL_r10(%rdi), %r10 + movq TDX_HYPERCALL_r11(%rdi), %r11 + movq TDX_HYPERCALL_r12(%rdi), %r12 + movq TDX_HYPERCALL_r13(%rdi), %r13 + movq TDX_HYPERCALL_r14(%rdi), %r14 + movq TDX_HYPERCALL_r15(%rdi), %r15 + + movl $TDVMCALL_EXPOSE_REGS_MASK, %ecx + + tdcall + + /* TDVMCALL leaf return code is in R10 */ + movq %r10, %rax + + /* Copy hypercall result registers to arg struct if needed */ + testq $TDX_HCALL_HAS_OUTPUT, %rsi + jz .Lout + + movq %r10, TDX_HYPERCALL_r10(%rdi) + movq %r11, TDX_HYPERCALL_r11(%rdi) + movq %r12, TDX_HYPERCALL_r12(%rdi) + movq %r13, TDX_HYPERCALL_r13(%rdi) + movq %r14, TDX_HYPERCALL_r14(%rdi) + movq %r15, TDX_HYPERCALL_r15(%rdi) +.Lout: + /* Restore callee-saved GPRs as mandated by the x86_64 ABI */ + pop %r12 + pop %r13 + pop %r14 + pop %r15 + + pop %rbp + ret + +/* Disable executable stack */ +.section .note.GNU-stack,"",%progbitstools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c new file +27
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "tdx/tdcall.h" +#include "tdx/tdx.h" + +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size, +uint64_t write,uint64_t *data) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r10 =TDX_HYPERCALL_STANDARD , + .r11 =TDG_VP_VMCALL_INSTRUCTION_IO , + .r12 = size, + .r13 = write, + .r14 = port, + }; + +if (write) + args.r15 = *data; + + ret =__tdx_hypercall (&args, write ?0 :TDX_HCALL_HAS_OUTPUT ); + +if (!write) + *data = args.r11; + +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +0
-0tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c static void tdx_enable_capabilities(struct kvm_vm *vm) · line 227
Quoted 4 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +1
-0@@ -224,6 +224,7 @@ static void tdx_enable_capabilities(struct kvm_vm *vm)KVM_X2APIC_API_USE_32BIT_IDS | KVM_X2APIC_API_DISABLE_BROADCAST_QUIRK);vm_enable_cap (vm,KVM_CAP_SPLIT_IRQCHIP ,24 ); +vm_enable_cap (vm,KVM_CAP_MAX_VCPUS ,512 );Since TDX spec doesn't define max vCPUs, is it a good idea to fix it to 512 in this common code?
How about to move this line to the specific test case where you are actually verifying this capability?
Quoted 8 lines
For example, move it to PATCH v5 21/29] KVM: selftests: TDX: Add TDG.VP.INFO test
+
vm_enable_cap(vm, KVM_CAP_MAX_VCPUS, 512);
...
TEST_ASSERT_EQ(ret_max_vcpus, 512);
See Yan Zhao's comment above. This was needed in the previous implementation of TDX and without it the tests would fail. With the new fix I'm going to remove this from the common code.
Quoted 2 lines
RFC PATCH v5 9/29 KVM: selftests: TDX: Add report_fatal_error test
In reply to Sagi ShaharThe test checks report_fatal_error functionality.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 6 ++- .../kvm/include/x86_64/tdx/tdx_util.h | 1 + .../kvm/include/x86_64/tdx/test_util.h | 19 ++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 39 ++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 12 +++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 10 +++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 +++++++++++++++++++ 7 files changed, 131 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5 -1
@@ -3,10 +3,14 @@#define SELFTEST_TDX_TDX_H #include <stdint.h> +#include "kvm_util_base.h" -#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data); +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +1 -0
@@ -12,5 +12,6 @@ struct kvm_vm *td_create(void);void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type,uint64_t attributes);void td_finalize (struct kvm_vm *vm); +void td_vcpu_run (struct kvm_vcpu *vcpu);#endif // SELFTESTS_TDX_KVM_UTIL_H
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +19 -0
@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error +* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa); +#endif // SELFTEST_TDX_TEST_UTIL_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +39 -0
@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {
@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ; + + args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +12 -0
@@ -10,6 +10,7 @@#include "kvm_util.h" #include "test_util.h" +#include "tdx/tdx.h" #include "tdx/td_boot.h" #include "kvm_util_base.h" #include "processor.h"
@@ -519,3 +520,14 @@ void td_finalize(struct kvm_vm *vm)tdx_td_finalizemr (vm); } + +void td_vcpu_run (struct kvm_vcpu *vcpu) +{ +vcpu_run (vcpu); + +/* Handle TD VMCALLs that require userspace handling. */ +if (vcpu->run->exit_reason ==KVM_EXIT_TDX && + vcpu->run->tdx.type ==KVM_EXIT_TDX_VMCALL ) { +handle_userspace_tdg_vp_vmcall_exit (vcpu); + } +}
tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +10 -0
@@ -32,3 +32,13 @@ void tdx_test_success(void)TDX_TEST_SUCCESS_SIZE , TDG_VP_VMCALL_INSTRUCTION_IO_WRITE, &code); } + +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa) +{ +tdg_vp_vmcall_report_fatal_error (error_code, data_gpa); +} + +void tdx_test_fatal (uint64_t error_code) +{ +tdx_test_fatal_with_data (error_code,0 ); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +45 -0
63 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 194 lines · Sagi Shahar
The test checks
report_fatal_errorfunctionality.Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 6 ++- .../kvm/include/x86_64/tdx/tdx_util.h | 1 + .../kvm/include/x86_64/tdx/test_util.h | 19 ++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 39 ++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 12 +++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 10 +++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 +++++++++++++++++++ 7 files changed, 131 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5
-1@@ -3,10 +3,14 @@#define SELFTEST_TDX_TDX_H #include <stdint.h> +#include "kvm_util_base.h" -#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data); +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +1
-0@@ -12,5 +12,6 @@ struct kvm_vm *td_create(void);void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type,uint64_t attributes);void td_finalize (struct kvm_vm *vm); +void td_vcpu_run (struct kvm_vcpu *vcpu);#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +19
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error +* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa); +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +39
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ; + + args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +12
-0@@ -10,6 +10,7 @@#include "kvm_util.h" #include "test_util.h" +#include "tdx/tdx.h" #include "tdx/td_boot.h" #include "kvm_util_base.h" #include "processor.h" @@ -519,3 +520,14 @@ void td_finalize(struct kvm_vm *vm)tdx_td_finalizemr (vm); } + +void td_vcpu_run (struct kvm_vcpu *vcpu) +{ +vcpu_run (vcpu); + +/* Handle TD VMCALLs that require userspace handling. */ +if (vcpu->run->exit_reason ==KVM_EXIT_TDX && + vcpu->run->tdx.type ==KVM_EXIT_TDX_VMCALL ) { +handle_userspace_tdg_vp_vmcall_exit (vcpu); + } +}tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +10
-0@@ -32,3 +32,13 @@ void tdx_test_success(void)TDX_TEST_SUCCESS_SIZE , TDG_VP_VMCALL_INSTRUCTION_IO_WRITE, &code); } + +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa) +{ +tdg_vp_vmcall_report_fatal_error (error_code, data_gpa); +} + +void tdx_test_fatal (uint64_t error_code) +{ +tdx_test_fatal_with_data (error_code,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +4
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" #include "test_util.h" @@ -30,6 +31,49 @@ void verify_td_lifecycle(void)printf ("\t ... PASSED\n" ); } +void guest_code_report_fatal_error (void ) +{ +uint64_t err;
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_td_lifecycle(void) · line 46
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ +/* +* Note: err should follow the GHCI spec definition: +* bits 31:0 should be set to 0. +* bits 62:32 are used for TD-specific extended error code. +* bit 63 is used to mark additional information in shared memory. +*/ + err =0x0BAAAAAD00000000 ; +if (err) +tdx_test_fatal (err);
Nit:
Since the error code is a constant, no need to use if statement. Or even save the variable?
Quoted 41 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +31
-0+ +tdx_test_success (); +} +void verify_report_fatal_error (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_report_fatal_error); +td_finalize (vm); + +printf ("Verifying report_fatal_error:\n" ); + +td_vcpu_run (vcpu); + +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.ndata,3 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[0 ],TDG_VP_VMCALL_REPORT_FATAL_ERROR ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],0x0BAAAAAD00000000 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[2 ],0 ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -40,6 +84,7 @@ int main(int argc, char **argv) }run_in_new_process (&verify_td_lifecycle); +run_in_new_process (&verify_report_fatal_error);return 0 ; }
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
In reply to Sagi ShaharQuoted 194 lines · Sagi Shahar
The test checks
report_fatal_errorfunctionality.Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 6 ++- .../kvm/include/x86_64/tdx/tdx_util.h | 1 + .../kvm/include/x86_64/tdx/test_util.h | 19 ++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 39 ++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 12 +++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 10 +++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 +++++++++++++++++++ 7 files changed, 131 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5
-1@@ -3,10 +3,14 @@#define SELFTEST_TDX_TDX_H #include <stdint.h> +#include "kvm_util_base.h" -#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data); +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +1
-0@@ -12,5 +12,6 @@ struct kvm_vm *td_create(void);void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type,uint64_t attributes);void td_finalize (struct kvm_vm *vm); +void td_vcpu_run (struct kvm_vcpu *vcpu);#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +19
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error +* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa); +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +39
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ; + + args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +12
-0@@ -10,6 +10,7 @@#include "kvm_util.h" #include "test_util.h" +#include "tdx/tdx.h" #include "tdx/td_boot.h" #include "kvm_util_base.h" #include "processor.h" @@ -519,3 +520,14 @@ void td_finalize(struct kvm_vm *vm)tdx_td_finalizemr (vm); } + +void td_vcpu_run (struct kvm_vcpu *vcpu) +{ +vcpu_run (vcpu); + +/* Handle TD VMCALLs that require userspace handling. */ +if (vcpu->run->exit_reason ==KVM_EXIT_TDX && + vcpu->run->tdx.type ==KVM_EXIT_TDX_VMCALL ) { +handle_userspace_tdg_vp_vmcall_exit (vcpu); + } +}tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +10
-0@@ -32,3 +32,13 @@ void tdx_test_success(void)TDX_TEST_SUCCESS_SIZE , TDG_VP_VMCALL_INSTRUCTION_IO_WRITE, &code); } + +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa) +{ +tdg_vp_vmcall_report_fatal_error (error_code, data_gpa); +} + +void tdx_test_fatal (uint64_t error_code) +{ +tdx_test_fatal_with_data (error_code,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +4
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" #include "test_util.h" @@ -30,6 +31,49 @@ void verify_td_lifecycle(void)printf ("\t ... PASSED\n" ); } +void guest_code_report_fatal_error (void ) +{ +uint64_t err;
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_td_lifecycle(void) · line 46
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ +/* +* Note: err should follow the GHCI spec definition: +* bits 31:0 should be set to 0. +* bits 62:32 are used for TD-specific extended error code. +* bit 63 is used to mark additional information in shared memory. +*/ + err =0x0BAAAAAD00000000 ; +if (err) +tdx_test_fatal (err);
I find tdx_test_fatal() is called a lot and each call site checks the err before calling it. Is it simpler to move the check of err inside of tdx_test_fatal() so that the callers just call it without check it every time?
Quoted 41 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +31
-0+ +tdx_test_success (); +} +void verify_report_fatal_error (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_report_fatal_error); +td_finalize (vm); + +printf ("Verifying report_fatal_error:\n" ); + +td_vcpu_run (vcpu); + +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.ndata,3 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[0 ],TDG_VP_VMCALL_REPORT_FATAL_ERROR ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],0x0BAAAAAD00000000 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[2 ],0 ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -40,6 +84,7 @@ int main(int argc, char **argv) }run_in_new_process (&verify_td_lifecycle); +run_in_new_process (&verify_report_fatal_error);return 0 ; }
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 205 lines · Binbin Wu
Quoted 201 lines · Sagi Shahar
The test checks
report_fatal_errorfunctionality.Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 6 ++- .../kvm/include/x86_64/tdx/tdx_util.h | 1 + .../kvm/include/x86_64/tdx/test_util.h | 19 ++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 39 ++++++++++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 12 +++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 10 +++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 45 +++++++++++++++++++ 7 files changed, 131 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5
-1@@ -3,10 +3,14 @@#define SELFTEST_TDX_TDX_H #include <stdint.h> +#include "kvm_util_base.h" -#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data); +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +1
-0@@ -12,5 +12,6 @@ struct kvm_vm *td_create(void);void td_initialize (struct kvm_vm *vm,enum vm_mem_backing_src_type src_type,uint64_t attributes);void td_finalize (struct kvm_vm *vm); +void td_vcpu_run (struct kvm_vcpu *vcpu);#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +19
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error +* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa); +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +39
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ; + + args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +12
-0@@ -10,6 +10,7 @@#include "kvm_util.h" #include "test_util.h" +#include "tdx/tdx.h" #include "tdx/td_boot.h" #include "kvm_util_base.h" #include "processor.h" @@ -519,3 +520,14 @@ void td_finalize(struct kvm_vm *vm)tdx_td_finalizemr (vm); } + +void td_vcpu_run (struct kvm_vcpu *vcpu) +{ +vcpu_run (vcpu); + +/* Handle TD VMCALLs that require userspace handling. */ +if (vcpu->run->exit_reason ==KVM_EXIT_TDX && + vcpu->run->tdx.type ==KVM_EXIT_TDX_VMCALL ) { +handle_userspace_tdg_vp_vmcall_exit (vcpu); + } +}tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +10
-0@@ -32,3 +32,13 @@ void tdx_test_success(void)TDX_TEST_SUCCESS_SIZE , TDG_VP_VMCALL_INSTRUCTION_IO_WRITE, &code); } + +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa) +{ +tdg_vp_vmcall_report_fatal_error (error_code, data_gpa); +} + +void tdx_test_fatal (uint64_t error_code) +{ +tdx_test_fatal_with_data (error_code,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +11
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" #include "test_util.h" @@ -30,6 +31,49 @@ void verify_td_lifecycle(void)printf ("\t ... PASSED\n" ); } +void guest_code_report_fatal_error (void ) +{ +uint64_t err; + +/* +* Note: err should follow the GHCI spec definition: +* bits 31:0 should be set to 0. +* bits 62:32 are used for TD-specific extended error code. +* bit 63 is used to mark additional information in shared memory. +*/
Quoted 9 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_td_lifecycle(void) · line 46
Quoted 3 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +3
-0+ err =0x0BAAAAAD00000000 ; +if (err) +tdx_test_fatal (err);I find
tdx_test_fatal()is called a lot and each call site checks the err before calling it. Is it simpler to move the check of err inside oftdx_test_fatal()so that the callers just call it without check it every time?
tdx_test_fatal is used for more cases than just testing error code but we can add another higher level helper. Maybe tdx_assert_error.
Quoted 43 lines
Quoted 42 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +31
-0+ +tdx_test_success (); +} +void verify_report_fatal_error (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_report_fatal_error); +td_finalize (vm); + +printf ("Verifying report_fatal_error:\n" ); + +td_vcpu_run (vcpu); + +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.ndata,3 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[0 ],TDG_VP_VMCALL_REPORT_FATAL_ERROR ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],0x0BAAAAAD00000000 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[2 ],0 ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -40,6 +84,7 @@ int main(int argc, char **argv) }run_in_new_process (&verify_td_lifecycle); +run_in_new_process (&verify_report_fatal_error);return 0 ; }
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
In reply to Sagi Shahar...
Quoted 16 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +8
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); +
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h bool is_tdx_enabled(void); · line 69
Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +10
-0+/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error +* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa);
I found nowhere is using "data_gpa" as a gpa, even in patch 23, it's usage is to pass a line number ("tdx_test_fatal_with_data(ret, __LINE__)").
Quoted 41 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +0
-0#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret;
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, · line 59
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0} + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ;
So, why this error_code needs to set bit 63?
Quoted 125 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +6
-0+ args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +12
-0@@ -10,6 +10,7 @@#include "kvm_util.h" #include "test_util.h" +#include "tdx/tdx.h" #include "tdx/td_boot.h" #include "kvm_util_base.h" #include "processor.h" @@ -519,3 +520,14 @@ void td_finalize(struct kvm_vm *vm)tdx_td_finalizemr (vm); } + +void td_vcpu_run (struct kvm_vcpu *vcpu) +{ +vcpu_run (vcpu); + +/* Handle TD VMCALLs that require userspace handling. */ +if (vcpu->run->exit_reason ==KVM_EXIT_TDX && + vcpu->run->tdx.type ==KVM_EXIT_TDX_VMCALL ) { +handle_userspace_tdg_vp_vmcall_exit (vcpu); + } +}tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +10
-0@@ -32,3 +32,13 @@ void tdx_test_success(void)TDX_TEST_SUCCESS_SIZE , TDG_VP_VMCALL_INSTRUCTION_IO_WRITE, &code); } + +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa) +{ +tdg_vp_vmcall_report_fatal_error (error_code, data_gpa); +} + +void tdx_test_fatal (uint64_t error_code) +{ +tdx_test_fatal_with_data (error_code,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +45
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" #include "test_util.h" @@ -30,6 +31,49 @@ void verify_td_lifecycle(void)printf ("\t ... PASSED\n" ); } +void guest_code_report_fatal_error (void ) +{ +uint64_t err; + +/* +* Note: err should follow the GHCI spec definition: +* bits 31:0 should be set to 0. +* bits 62:32 are used for TD-specific extended error code. +* bit 63 is used to mark additional information in shared memory. +*/ + err =0x0BAAAAAD00000000 ; +if (err) +tdx_test_fatal (err); + +tdx_test_success (); +} +void verify_report_fatal_error (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_report_fatal_error); +td_finalize (vm); + +printf ("Verifying report_fatal_error:\n" ); + +td_vcpu_run (vcpu); + +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.ndata,3 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[0 ],TDG_VP_VMCALL_REPORT_FATAL_ERROR ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],0x0BAAAAAD00000000 ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[2 ],0 ); + +vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -40,6 +84,7 @@ int main(int argc, char **argv) }run_in_new_process (&verify_td_lifecycle); +run_in_new_process (&verify_report_fatal_error);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 21 lines · Yan Zhao
...
Quoted 20 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +12
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error
Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h bool is_tdx_enabled(void); · line 69
Quoted 6 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +6
-0+* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa);I found nowhere is using "
data_gpa" as a gpa, even in patch 23, it's usage is to pass a line number ("tdx_test_fatal_with_data(ret, __LINE__)").
This function tdx_test_fatal_with_data() is meant to provide a generic interface for TDX tests to use TDG.VP.VMCALL<ReportFatalError>, and so the parameters of tdx_test_fatal_with_data() generically allow error_code and data_gpa to be specified.
The tests just happen to use the data_gpa parameter to pass __LINE__ to the host VMM, but other tests in future that use the tdx_test_fatal_with_data() function in the TDX testing library could actually pass a GPA through using data_gpa.
Quoted 39 lines
Quoted 39 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +0
-0#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,
Quoted 15 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, · line 59
Quoted 12 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ;So, why this
error_codeneeds to set bit 63?
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a generic TDX testing library function, this check allows the user to use tdg_vp_vmcall_report_fatal_error() with error_code and data_gpa and not worry about setting bit 63 before calling tdg_vp_vmcall_report_fatal_error(), though if the user set bit 63 before that, there is no issue.
Quoted 8 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +6
-0+ args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 99 lines · Ackerley Tng
Quoted 21 lines · Yan Zhao
...
Quoted 20 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +12
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h bool is_tdx_enabled(void); · line 69
Quoted 6 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +6
-0+* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa);I found nowhere is using "
data_gpa" as a gpa, even in patch 23, it's usage is to pass a line number ("tdx_test_fatal_with_data(ret, __LINE__)").This function
tdx_test_fatal_with_data()is meant to provide a generic interface for TDX tests to use TDG.VP.VMCALL<ReportFatalError>, and so the parameters oftdx_test_fatal_with_data()generically allowerror_codeanddata_gpato be specified.The tests just happen to use the
data_gpaparameter to pass__LINE__to the host VMM, but other tests in future that use thetdx_test_fatal_with_data()function in the TDX testing library could actually pass a GPA through usingdata_gpa.Quoted 39 lines
Quoted 39 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +0
-0#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,Quoted 15 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, · line 59
Quoted 12 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0return ret; } + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ;So, why this
error_codeneeds to set bit 63?
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "__LINE__" is obviously not a valid GPA.
Do you think it's better to check "data_gpa" is with shared bit on and aligned in 4K before setting bit 63?
Quoted 15 lines
generic TDX testing library function, this check allows the user to use
tdg_vp_vmcall_report_fatal_error()witherror_codeanddata_gpaand not worry about setting bit 63 before callingtdg_vp_vmcall_report_fatal_error(), though if the user set bit 63 before that, there is no issue.Quoted 8 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +6
-0+ args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 100 lines · Yan Zhao
Quoted 99 lines · Ackerley Tng
Quoted 21 lines · Yan Zhao
...
Quoted 20 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +12
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h bool is_tdx_enabled(void); · line 69
Quoted 6 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +6
-0+* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa);I found nowhere is using "
data_gpa" as a gpa, even in patch 23, it's usage is to pass a line number ("tdx_test_fatal_with_data(ret, __LINE__)").This function
tdx_test_fatal_with_data()is meant to provide a generic interface for TDX tests to use TDG.VP.VMCALL<ReportFatalError>, and so the parameters oftdx_test_fatal_with_data()generically allowerror_codeanddata_gpato be specified.The tests just happen to use the
data_gpaparameter to pass__LINE__to the host VMM, but other tests in future that use thetdx_test_fatal_with_data()function in the TDX testing library could actually pass a GPA through usingdata_gpa.Quoted 54 lines
Quoted 41 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +0
-0#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret;tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, · line 59
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0} + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ;So, why this
error_codeneeds to set bit 63?
Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?
I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the data_gpa as you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that calls tdg_vp_vmcall_report_fatal_error()?
If it helps, shall we rename "data_gpa" to "data" for this lower-level, generic helper function and remove these two lines
if (data_gpa)
error_code |= 0x8000000000000000;
A higher-level function could perhaps do the validation as you suggested and then set bit 63.
Are you objecting to the use of R13 to hold extra test information, such as __LINE__?
I feel that R13 is just another register that could be used to hold error information, and in the case of this test, we can use it to send __LINE__ to aid in debugging selftests. On the host side of the selftest we can printf() :).
Quoted 15 lines
Quoted 15 lines
generic TDX testing library function, this check allows the user to use
tdg_vp_vmcall_report_fatal_error()witherror_codeanddata_gpaand not worry about setting bit 63 before callingtdg_vp_vmcall_report_fatal_error(), though if the user set bit 63 before that, there is no issue.Quoted 8 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +6
-0+ args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 117 lines · Ackerley Tng
Quoted 100 lines · Yan Zhao
Quoted 99 lines · Ackerley Tng
Quoted 21 lines · Yan Zhao
...
Quoted 20 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +12
-0@@ -49,4 +49,23 @@ bool is_tdx_enabled(void);*/ void tdx_test_success (void ); +/** +* Report an error with @error_code to userspace. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal (uint64_t error_code); + +/** +* Report an error with @error_code to userspace. +* +* @data_gpa may point to an optional shared guest memory holding the error Quoted 10 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h bool is_tdx_enabled(void); · line 69
Quoted 6 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +6
-0+* string. +* +* Return value from tdg_vp_vmcall_report_fatal_error is ignored since execution +* is not expected to continue beyond this point. +*/ +void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa);I found nowhere is using "
data_gpa" as a gpa, even in patch 23, it's usage is to pass a line number ("tdx_test_fatal_with_data(ret, __LINE__)").This function
tdx_test_fatal_with_data()is meant to provide a generic interface for TDX tests to use TDG.VP.VMCALL<ReportFatalError>, and so the parameters oftdx_test_fatal_with_data()generically allowerror_codeanddata_gpato be specified.The tests just happen to use the
data_gpaparameter to pass__LINE__to the host VMM, but other tests in future that use thetdx_test_fatal_with_data()function in the TDX testing library could actually pass a GPA through usingdata_gpa.Quoted 54 lines
Quoted 41 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +0
-0#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -1,8 +1,31 @@// SPDX-License-Identifier: GPL-2.0-only +#include <string.h> +#include "tdx/tdcall.h" #include "tdx/tdx.h" +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) +{ +struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall; +uint64_t vmcall_subfunction = vmcall_info->subfunction; + +switch (vmcall_subfunction) { +case TDG_VP_VMCALL_REPORT_FATAL_ERROR : + vcpu->run->exit_reason =KVM_EXIT_SYSTEM_EVENT ; + vcpu->run->system_event.ndata =3 ; + vcpu->run->system_event.data[0 ] = +TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + vcpu->run->system_event.data[1 ] = vmcall_info->in_r12; + vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; + vmcall_info->status_code =0 ; +break ; +default : +TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , + vmcall_subfunction); + } +} +uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data) {@@ -25,3 +48,19 @@ uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,return ret;tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, · line 59
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0} + +void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa) +{ +struct tdx_hypercall_args args; + +memset (&args,0 ,sizeof (struct tdx_hypercall_args )); + +if (data_gpa) + error_code |=0x8000000000000000 ;So, why this
error_codeneeds to set bit 63?Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the
data_gpaas you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that callstdg_vp_vmcall_report_fatal_error()?
Quoted 8 lines
If it helps, shall we rename "
data_gpa" to "data" for this lower-level, generic helper function and remove these two linesif (
data_gpa)error_code |= 0x8000000000000000;A higher-level function could perhaps do the validation as you suggested and then set bit 63.
This could be all right. But I'm not sure if it would be a burden for higher-level function to set bit 63 which is of GHCI details.
What about adding another "data_gpa_valid" parameter and then test "data_gpa_valid" rather than test "data_gpa" to set bit 63?
Quoted 9 lines
Are you objecting to the use of R13 to hold extra test information, such as
__LINE__?I feel that R13 is just another register that could be used to hold error information, and in the case of this test, we can use it to send
__LINE__to aid in debugging selftests. On the host side of the selftest we canprintf():).
Hmm, I just feel it's confusing to use R13 as error code holder and set gpa_valid bit on at the same time.
As it looks complicated to convert __LINE__ to a string in a shared GPA, maybe it's ok to pass it in R13 :)
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
generic TDX testing library function, this check allows the user to use
tdg_vp_vmcall_report_fatal_error()witherror_codeanddata_gpaand not worry about setting bit 63 before callingtdg_vp_vmcall_report_fatal_error(), though if the user set bit 63 before that, there is no issue.Quoted 8 lines
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +6
-0+ args.r11 =TDG_VP_VMCALL_REPORT_FATAL_ERROR ; + args.r12 = error_code; + args.r13 = data_gpa; + +__tdx_hypercall (&args,0 ); +}
Sean Christopherson
reviewerRe: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 22 lines · Yan Zhao
Quoted 21 lines · Ackerley Tng
Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the
data_gpaas you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that callstdg_vp_vmcall_report_fatal_error()?If it helps, shall we rename "
data_gpa" to "data" for this lower-level, generic helper function and remove these two linesif (
data_gpa)error_code |= 0x8000000000000000;
Quoted 7 lines
Quoted 2 lines
A higher-level function could perhaps do the validation as you suggested and then set bit 63.
This could be all right. But I'm not sure if it would be a burden for higher-level function to set bit 63 which is of GHCI details.
What about adding another "
data_gpa_valid" parameter and then test "data_gpa_valid" rather than test "data_gpa" to set bit 63?
Who cares what the GHCI says about validity? The GHCI is a spec for getting random guests to play nice with random hosts. Selftests own both, and the goal of selftests is to test that KVM (and KVM's dependencies) adhere to their relevant specs. And more importantly, KVM is NOT inheriting the GHCI ABI verbatim[*].
So except for the bits and bobs that *KVM* (or the TDX module) gets involved in, just ignore the GHCI (or even deliberately abuse it). To put it differently, use selftests verify *KVM's* ABI and functionality.
As it pertains to this thread, while I haven't looked at any of this in detail, I'm guessing that whether or not bit 63 is set is a complete "don't care", i.e. KVM and the TDX Module should pass it through as-is.
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 40 lines · Sean Christopherson
Quoted 22 lines · Yan Zhao
Quoted 21 lines · Ackerley Tng
Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the
data_gpaas you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that callstdg_vp_vmcall_report_fatal_error()?If it helps, shall we rename "
data_gpa" to "data" for this lower-level, generic helper function and remove these two linesif (
data_gpa)error_code |= 0x8000000000000000;Quoted 7 lines
Quoted 2 lines
A higher-level function could perhaps do the validation as you suggested and then set bit 63.
This could be all right. But I'm not sure if it would be a burden for higher-level function to set bit 63 which is of GHCI details.
What about adding another "
data_gpa_valid" parameter and then test "data_gpa_valid" rather than test "data_gpa" to set bit 63?Who cares what the GHCI says about validity? The GHCI is a spec for getting random guests to play nice with random hosts. Selftests own both, and the goal of selftests is to test that KVM (and KVM's dependencies) adhere to their relevant specs. And more importantly, KVM is NOT inheriting the GHCI ABI verbatim[*].
So except for the bits and bobs that *KVM* (or the TDX module) gets involved in, just ignore the GHCI (or even deliberately abuse it). To put it differently, use selftests verify *KVM's* ABI and functionality.
Quoted 5 lines
As it pertains to this thread, while I haven't looked at any of this in detail, I'm guessing that whether or not bit 63 is set is a complete "don't care", i.e. KVM and the TDX Module should pass it through as-is.
Ok. It makes sense to KVM_EXIT_TDX.
But what if the TDVMCALL is handled in TDX specific code in kernel in future? (not possible?)
Should guest set bits correctly according to GHCI?
Sean Christopherson
reviewerRe: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 41 lines · Yan Zhao
Quoted 40 lines · Sean Christopherson
Quoted 22 lines · Yan Zhao
Quoted 21 lines · Ackerley Tng
Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the
data_gpaas you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that callstdg_vp_vmcall_report_fatal_error()?If it helps, shall we rename "
data_gpa" to "data" for this lower-level, generic helper function and remove these two linesif (
data_gpa)error_code |= 0x8000000000000000;Quoted 7 lines
Quoted 2 lines
A higher-level function could perhaps do the validation as you suggested and then set bit 63.
This could be all right. But I'm not sure if it would be a burden for higher-level function to set bit 63 which is of GHCI details.
What about adding another "
data_gpa_valid" parameter and then test "data_gpa_valid" rather than test "data_gpa" to set bit 63?Who cares what the GHCI says about validity? The GHCI is a spec for getting random guests to play nice with random hosts. Selftests own both, and the goal of selftests is to test that KVM (and KVM's dependencies) adhere to their relevant specs. And more importantly, KVM is NOT inheriting the GHCI ABI verbatim[*].
So except for the bits and bobs that *KVM* (or the TDX module) gets involved in, just ignore the GHCI (or even deliberately abuse it). To put it differently, use selftests verify *KVM's* ABI and functionality.
Quoted 8 lines
Quoted 5 lines
As it pertains to this thread, while I haven't looked at any of this in detail, I'm guessing that whether or not bit 63 is set is a complete "don't care", i.e. KVM and the TDX Module should pass it through as-is.
Ok. It makes sense to
KVM_EXIT_TDX.
But what if the TDVMCALL is handled in TDX specific code in kernel in future? (not possible?)
KVM will "handle" ReportFatalError, and will do so before this code lands[*], but I *highly* doubt KVM will ever do anything but forward the information to userspace, e.g. as KVM_SYSTEM_EVENT_CRASH with data[] filled in with the raw register information.
Quoted 1 line
Should guest set bits correctly according to GHCI?
No. Selftests exist first and foremost to verify KVM behavior, not to verify firmware behavior. We can and should use selftests to verify that *KVM* doesn't *violate* the GHCI, but that doesn't mean that selftests themselves can't ignore and/or abuse the GCHI, especially since the GHCI definition for ReportFatalError is frankly awful.
E.g. the GHCI prescibes actual behavior for R13, but then doesn't say *anything* about what's in the data page. Why!?!?! If the format in the data page is completely undefined, what's the point of restricting R13 to only be allowed to hold a GPA?
And the wording is just as awful:
The VMM must validate that this GPA has the Shared bit set. In other words, that a shared-mapping is used, and that this is a valid mapping for the TD.
I'm pretty sure it's just saying that the TDX module isn't going to verify the operate, i.e. that the VMM needs to protect itself, but it would be so much better to simply state "The TDX Module does not verify this GPA", because saying the VMM "must" do something leads to pointless discussions like this one, where we're debating over whether or *our* VMM should inject an error into *our* guest.
Anyways, we should do what makes sense for selftests and ignore the stupidity of the GHCI when doing so yields better code. If that means abusing R13, go for it. If it's a sticking point for anyone, just use one of the "optional" registers.
Whatever we do, bury the host and guest side of selftests behind #defines or helpers so that there are at most two pieces of code that care which register holds which piece of information.
Re: [RFC PATCH v5 09/29] KVM: selftests: TDX: Add report_fatal_error test
Quoted 59 lines · Sean Christopherson
Quoted 39 lines · Yan Zhao
Quoted 38 lines · Sean Christopherson
Quoted 21 lines · Yan Zhao
Quoted 20 lines · Ackerley Tng
Quoted 6 lines
Quoted 1 line
The Intel GHCI Spec says in R12, bit 63 is set if the GPA is valid. As a
But above "
__LINE__" is obviously not a valid GPA.Do you think it's better to check "
data_gpa" is with shared bit on and aligned in 4K before setting bit 63?I read "valid" in the spec to mean that the value in R13 "should be considered as useful" or "should be passed on to the host VMM via the TDX module", and not so much as in "validated".
We could validate the
data_gpaas you suggested to check alignment and shared bit, but perhaps that could be a higher-level function that callstdg_vp_vmcall_report_fatal_error()?If it helps, shall we rename "
data_gpa" to "data" for this lower-level, generic helper function and remove these two linesif (
data_gpa)error_code |= 0x8000000000000000;Quoted 7 lines
Quoted 2 lines
A higher-level function could perhaps do the validation as you suggested and then set bit 63.
This could be all right. But I'm not sure if it would be a burden for higher-level function to set bit 63 which is of GHCI details.
What about adding another "
data_gpa_valid" parameter and then test "data_gpa_valid" rather than test "data_gpa" to set bit 63?Who cares what the GHCI says about validity? The GHCI is a spec for getting random guests to play nice with random hosts. Selftests own both, and the goal of selftests is to test that KVM (and KVM's dependencies) adhere to their relevant specs. And more importantly, KVM is NOT inheriting the GHCI ABI verbatim[*].
So except for the bits and bobs that *KVM* (or the TDX module) gets involved in, just ignore the GHCI (or even deliberately abuse it). To put it differently, use selftests verify *KVM's* ABI and functionality.
Quoted 8 lines
Quoted 5 lines
As it pertains to this thread, while I haven't looked at any of this in detail, I'm guessing that whether or not bit 63 is set is a complete "don't care", i.e. KVM and the TDX Module should pass it through as-is.
Ok. It makes sense to
KVM_EXIT_TDX.
But what if the TDVMCALL is handled in TDX specific code in kernel in future? (not possible?)KVM will "handle" ReportFatalError, and will do so before this code lands[*], but I *highly* doubt KVM will ever do anything but forward the information to userspace, e.g. as
KVM_SYSTEM_EVENT_CRASHwith data[] filled in with the raw register information.Quoted 1 line
Should guest set bits correctly according to GHCI?
No. Selftests exist first and foremost to verify KVM behavior, not to verify firmware behavior. We can and should use selftests to verify that *KVM* doesn't *violate* the GHCI, but that doesn't mean that selftests themselves can't ignore and/or abuse the GCHI, especially since the GHCI definition for ReportFatalError is frankly awful.
Quoted 4 lines
E.g. the GHCI prescibes actual behavior for R13, but then doesn't say *anything* about what's in the data page. Why!?!?! If the format in the data page is completely undefined, what's the point of restricting R13 to only be allowed to hold a GPA?
The description of R13 in GHCI:
4KB-aligned GPA where additional error data is shared by the TD. The VMM must validate that this GPA has the Shared bit set. In other words, that a shared-mapping is used, and that this is a valid mapping for the TD. This shared memory region is expected to hold a zero-terminated string.
IIUC, according the GHCI, R13 is a 4K aligned shared buffer provided by the TDX guest to pass additional error message to VMM, i.e., it needs to be a shared GPA. And the content in the buffer is expected to hold a zero-terminated string.
Do you think "a zero-terminated string" describes the format in the data page?
Quoted 22 lines
And the wording is just as awful:
The VMM must validate that this GPA has the Shared bit set. In other words, that a shared-mapping is used, and that this is a valid mapping for the TD.
I'm pretty sure it's just saying that the TDX module isn't going to verify the operate, i.e. that the VMM needs to protect itself, but it would be so much better to simply state "The TDX Module does not verify this GPA", because saying the VMM "must" do something leads to pointless discussions like this one, where we're debating over whether or *our* VMM should inject an error into *our* guest.
Anyways, we should do what makes sense for selftests and ignore the stupidity of the GHCI when doing so yields better code. If that means abusing R13, go for it. If it's a sticking point for anyone, just use one of the "optional" registers.
Whatever we do, bury the host and guest side of selftests behind #defines or helpers so that there are at most two pieces of code that care which register holds which piece of information.
RFC PATCH v5 10/29 KVM: selftests: TDX: Adding test case for TDX port IO
In reply to Sagi ShaharFrom: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34 -0
@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +82 -0
100 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 10/29] KVM: selftests: TDX: Adding test case for TDX port IO
Quoted 4 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
Quoted 8 lines
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)
One nit comment below.
Quoted 79 lines
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34
-0@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */ tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +18
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" @@ -74,6 +75,86 @@ void verify_report_fatal_error(void)printf ("\t ... PASSED\n" ); } +#define TDX_IOEXIT_TEST_PORT 0x50 + +/* +* Verifies IO functionality by writing a |value| to a predefined port. +* Verifies that the read value is |value| + 1 from the same port. +* If all the tests are passed then write a value to port TDX_TEST_PORT +*/ +void guest_ioexit (void ) +{ +uint64_t data_out, data_in, delta; +uint64_t ret; + + data_out =0xAB ; + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_out); +if (ret)
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 104
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data_in); +if (ret) +tdx_test_fatal (ret); + + delta = data_in - data_out; +if (delta !=1 )
Nit: Is it more direct to compare data_in with 0xAC?
Quoted 64 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +54
-0+tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_td_ioexit (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint32_t port_data; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_ioexit); +td_finalize (vm); + +printf ("Verifying TD IO Exit:\n" ); + +/* Wait for guest to do a IO write */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + port_data = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +printf ("\t ... IO WRITE: OK\n" ); + +/* +* Wait for the guest to do a IO read. Provide the previous written data +* + 1 back to the guest +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) = port_data +1 ; + +printf ("\t ... IO READ: OK\n" ); + +/* +* Wait for the guest to complete execution successfully. The read +* value is checked within the guest. +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... IO verify read/write values: OK\n" ); +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -85,6 +166,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_lifecycle);run_in_new_process (&verify_report_fatal_error); +run_in_new_process (&verify_td_ioexit);return 0 ; }
Re: [RFC PATCH v5 10/29] KVM: selftests: TDX: Adding test case for TDX port IO
In reply to Sagi ShaharQuoted 113 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34
-0@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */ tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +40
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" @@ -74,6 +75,86 @@ void verify_report_fatal_error(void)printf ("\t ... PASSED\n" ); } +#define TDX_IOEXIT_TEST_PORT 0x50 + +/* +* Verifies IO functionality by writing a |value| to a predefined port. +* Verifies that the read value is |value| + 1 from the same port. +* If all the tests are passed then write a value to port TDX_TEST_PORT +*/ +void guest_ioexit (void ) +{ +uint64_t data_out, data_in, delta; +uint64_t ret; + + data_out =0xAB ; + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_out); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data_in); +if (ret) +tdx_test_fatal (ret); + + delta = data_in - data_out; +if (delta !=1 ) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_td_ioexit (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint32_t port_data; +
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 126
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_ioexit); +td_finalize (vm); + +printf ("Verifying TD IO Exit:\n" ); + +/* Wait for guest to do a IO write */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);
This check is a vain, because the first VMExit from vcpu run is always KVM_EXIT_IO caused by tdg_vp_vmcall_instruction_io().
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 131
Quoted 5 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + port_data = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +printf ("\t ... IO WRITE: OK\n" );
So, even if there's an error in emulating writing of TDX_IOEXIT_TEST_PORT, and guest would then find a failure and trigger tdx_test_fatal(), this line will still print "IO WRITE: OK", which is not right.
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 138
Quoted 7 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +7
-0+ +/* +* Wait for the guest to do a IO read. Provide the previous written data +* + 1 back to the guest +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);
This check is a vain, too, as in write case.
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 143
Quoted 5 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) = port_data +1 ; + +printf ("\t ... IO READ: OK\n" );
Same as in write case, this line should not be printed until after guest finishing checking return code.
Quoted 29 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +15
-0+ +/* +* Wait for the guest to complete execution successfully. The read +* value is checked within the guest. +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... IO verify read/write values: OK\n" ); +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -85,6 +166,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_lifecycle);run_in_new_process (&verify_report_fatal_error); +run_in_new_process (&verify_td_ioexit);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 10/29] KVM: selftests: TDX: Adding test case for TDX port IO
Quoted 118 lines · Yan Zhao
Quoted 117 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34
-0@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */ tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +44
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" @@ -74,6 +75,86 @@ void verify_report_fatal_error(void)printf ("\t ... PASSED\n" ); } +#define TDX_IOEXIT_TEST_PORT 0x50 + +/* +* Verifies IO functionality by writing a |value| to a predefined port. +* Verifies that the read value is |value| + 1 from the same port. +* If all the tests are passed then write a value to port TDX_TEST_PORT +*/ +void guest_ioexit (void ) +{ +uint64_t data_out, data_in, delta; +uint64_t ret; + + data_out =0xAB ; + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_out); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data_in); +if (ret) +tdx_test_fatal (ret); + + delta = data_in - data_out; +if (delta !=1 ) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_td_ioexit (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint32_t port_data; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_ioexit); +td_finalize (vm);
Quoted 8 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 126
Quoted 6 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +6
-0+ +printf ("Verifying TD IO Exit:\n" ); + +/* Wait for guest to do a IO write */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, because the first VMExit from vcpu run is always
KVM_EXIT_IOcaused bytdg_vp_vmcall_instruction_io().
I think tdg_vp_vmcall_instruction_io() could fail if RCX (GPR select) doesn't meet the requirement (some bits must be 0).
Although RCX is set by guest code (in selftest, it set in __tdx_hypercall()) and it will not trigger the error, it still can be used as a guard to make sure guest doesn't pass a invalid RCX.
Quoted 57 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 131
Quoted 7 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + port_data = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +printf ("\t ... IO WRITE: OK\n" );So, even if there's an error in emulating writing of
TDX_IOEXIT_TEST_PORT, and guest would then find a failure and triggertdx_test_fatal(), this line will still print "IO WRITE: OK", which is not right.tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 138
Quoted 7 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +7
-0+ +/* +* Wait for the guest to do a IO read. Provide the previous written data +* + 1 back to the guest +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, too, as in write case.
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 143
Quoted 5 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) = port_data +1 ; + +printf ("\t ... IO READ: OK\n" );Same as in write case, this line should not be printed until after guest finishing checking return code.
Quoted 29 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +15
-0+ +/* +* Wait for the guest to complete execution successfully. The read +* value is checked within the guest. +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... IO verify read/write values: OK\n" ); +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -85,6 +166,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_lifecycle);run_in_new_process (&verify_report_fatal_error); +run_in_new_process (&verify_td_ioexit);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 10/29] KVM: selftests: TDX: Adding test case for TDX port IO
Quoted 127 lines · Binbin Wu
Quoted 115 lines · Yan Zhao
Quoted 114 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34
-0@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */ tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +44
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" @@ -74,6 +75,86 @@ void verify_report_fatal_error(void)printf ("\t ... PASSED\n" ); } +#define TDX_IOEXIT_TEST_PORT 0x50 + +/* +* Verifies IO functionality by writing a |value| to a predefined port. +* Verifies that the read value is |value| + 1 from the same port. +* If all the tests are passed then write a value to port TDX_TEST_PORT +*/ +void guest_ioexit (void ) +{ +uint64_t data_out, data_in, delta; +uint64_t ret; + + data_out =0xAB ; + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_out); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data_in); +if (ret) +tdx_test_fatal (ret); + + delta = data_in - data_out; +if (delta !=1 ) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_td_ioexit (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint32_t port_data; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_ioexit); +td_finalize (vm);Quoted 8 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 126
Quoted 6 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +6
-0+ +printf ("Verifying TD IO Exit:\n" ); + +/* Wait for guest to do a IO write */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, because the first VMExit from vcpu run is always
KVM_EXIT_IOcaused bytdg_vp_vmcall_instruction_io().
Quoted 7 lines
I think
tdg_vp_vmcall_instruction_io()could fail if RCX (GPR select) doesn't
meet the requirement (some bits must be 0).
Although RCX is set by guest code (in selftest, it set in__tdx_hypercall()) and it will not trigger the error, it still can be used as a guard to make sure guest doesn't pass a invalid RCX.
Right. This check can be kept in case an failure is delivered to TD in host kernel directly, though it cannot guard if the failure will trigger an exit to user space (e.g. if kernel TDX code has a bug).
Quoted 57 lines
Quoted 56 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 131
Quoted 8 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + port_data = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +printf ("\t ... IO WRITE: OK\n" );So, even if there's an error in emulating writing of
TDX_IOEXIT_TEST_PORT, and guest would then find a failure and triggertdx_test_fatal(), this line will still print "IO WRITE: OK", which is not right.tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 138
Quoted 7 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +7
-0+ +/* +* Wait for the guest to do a IO read. Provide the previous written data +* + 1 back to the guest +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, too, as in write case.
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 143
Quoted 5 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) = port_data +1 ; + +printf ("\t ... IO READ: OK\n" );Same as in write case, this line should not be printed until after guest finishing checking return code.
Quoted 27 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +15
-0+ +/* +* Wait for the guest to complete execution successfully. The read +* value is checked within the guest. +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... IO verify read/write values: OK\n" ); +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -85,6 +166,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_lifecycle);run_in_new_process (&verify_report_fatal_error); +run_in_new_process (&verify_td_ioexit);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 10/29] KVM: selftests: TDX: Adding test case for TDX port IO
In reply to Yan ZhaoQuoted 129 lines · Yan Zhao
Quoted 113 lines · Sagi Shahar
From: Erdem Aktas <[email protected]>
Verifies TDVMCALL<INSTRUCTION.IO> READ and WRITE operations.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../kvm/include/x86_64/tdx/test_util.h | 34 ++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 82 +++++++++++++++++++ 2 files changed, 116 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +34
-0@@ -9,6 +9,40 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +/** +* Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was +* called in the guest. +*/ +#define TDX_TEST_ASSERT_IO (VCPU ,PORT ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_IO, \ + "Got exit_reason other than KVM_EXIT_IO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_IO) && \ + ((VCPU)->run->io.port == (PORT)) && \ + ((VCPU)->run->io.size == (SIZE)) && \ + ((VCPU)->run->io.direction == (DIR)), \ + "Got unexpected IO exit values: %u (%s) %d %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->io.port, (VCPU)->run->io.size, \ + (VCPU)->run->io.direction); \ + } while (0) + +/** +* Check and report if there was some failure in the guest, either an exception +* like a triple fault, or if a tdx_test_fatal() was hit. +*/ +#define TDX_TEST_CHECK_GUEST_FAILURE (VCPU ) \ + do { \ + if ((VCPU)->run->exit_reason == KVM_EXIT_SYSTEM_EVENT) \ + TEST_FAIL("Guest reported error. error code: %lld (0x%llx)\n", \ + (VCPU)->run->system_event.data[1], \ + (VCPU)->run->system_event.data[1]); \ + } while (0) +/** * Assert that tdx_test_success() was called in the guest. */ tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +40
-0@@ -2,6 +2,7 @@#include <signal.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/tdx_util.h" #include "tdx/test_util.h" @@ -74,6 +75,86 @@ void verify_report_fatal_error(void)printf ("\t ... PASSED\n" ); } +#define TDX_IOEXIT_TEST_PORT 0x50 + +/* +* Verifies IO functionality by writing a |value| to a predefined port. +* Verifies that the read value is |value| + 1 from the same port. +* If all the tests are passed then write a value to port TDX_TEST_PORT +*/ +void guest_ioexit (void ) +{ +uint64_t data_out, data_in, delta; +uint64_t ret; + + data_out =0xAB ; + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_out); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data_in); +if (ret) +tdx_test_fatal (ret); + + delta = data_in - data_out; +if (delta !=1 ) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_td_ioexit (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint32_t port_data; +tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 126
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_ioexit); +td_finalize (vm); + +printf ("Verifying TD IO Exit:\n" ); + +/* Wait for guest to do a IO write */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, because the first VMExit from vcpu run is always
KVM_EXIT_IOcaused bytdg_vp_vmcall_instruction_io().
Quoted 8 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 131
Quoted 5 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + port_data = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +printf ("\t ... IO WRITE: OK\n" );So, even if there's an error in emulating writing of
TDX_IOEXIT_TEST_PORT, and guest would then find a failure and triggertdx_test_fatal(), this line will still print "IO WRITE: OK", which is not right.
Changed this to "IO WRITE: DONE". This is a useful for understanding errors if they happen so I don't want to remove this log entirely.
Quoted 9 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 138
Quoted 8 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +7
-0+ +/* +* Wait for the guest to do a IO read. Provide the previous written data +* + 1 back to the guest +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);This check is a vain, too, as in write case.
There's no harm in adding this check and it helps debugging issues if something unexpected happens.
Since this check always come together with td_vcpu_run I'm going to simplify the code and introduce a TDX_RUN macro that simply runs the CPU and checks for reported guest failures which is going to replace the td_vcpu_run/TDX_TEST_CHECK_GUEST_FAILURE combo.
Quoted 39 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_report_fatal_error(void) · line 143
Quoted 6 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +5
-0+TDX_TEST_ASSERT_IO (vcpu,TDX_IOEXIT_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) = port_data +1 ; + +printf ("\t ... IO READ: OK\n" );Same as in write case, this line should not be printed until after guest finishing checking return code.
Quoted 29 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +15
-1+ +/* +* Wait for the guest to complete execution successfully. The read +* value is checked within the guest. +*/ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... IO verify read/write values: OK\n" ); +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -85,6 +166,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_lifecycle);run_in_new_process (&verify_report_fatal_error); +run_in_new_process (&verify_td_ioexit);return 0 ; } --2.43.0.472.g3155946c3a-goog
RFC PATCH v5 11/29 KVM: selftests: TDX: Add basic TDX CPUID test
In reply to Sagi ShaharThe test reads CPUID values from inside a TD VM and compare them to expected values.
The test targets CPUID values which are virtualized as "As Configured", "As Configured (if Native)", "Calculated", "Fixed" and "Native" according to the TDX spec.
--- .../kvm/include/x86_64/tdx/test_util.h | 9 ++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 11 ++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 106 ++++++++++++++++++ 3 files changed, 126 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +9 -0
@@ -9,6 +9,9 @@#define TDX_TEST_SUCCESS_PORT 0x30#define TDX_TEST_SUCCESS_SIZE 4 +#define TDX_TEST_REPORT_PORT 0x31 +#define TDX_TEST_REPORT_SIZE 4 +/** * Assert that some IO operation involving tdg_vp_vmcall_instruction_io() was * called in the guest.
@@ -102,4 +105,10 @@ void tdx_test_fatal(uint64_t error_code);*/ void tdx_test_fatal_with_data (uint64_t error_code,uint64_t data_gpa); +/** +* Report a 32 bit value from the guest to user space using TDG.VP.VMCALL +* <Instruction.IO> call. Data is reported on port TDX_TEST_REPORT_PORT. +*/ +uint64_t tdx_test_report_to_user_space (uint32_t data); +#endif // SELFTEST_TDX_TEST_UTIL_H
tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +11 -0
@@ -42,3 +42,14 @@ void tdx_test_fatal(uint64_t error_code) {tdx_test_fatal_with_data (error_code,0 ); } + +uint64_t tdx_test_report_to_user_space (uint32_t data) +{ +/* Upcast data to match tdg_vp_vmcall_instruction_io signature */ +uint64_t data_64 = data; + +return tdg_vp_vmcall_instruction_io (TDX_TEST_REPORT_PORT , +TDX_TEST_REPORT_SIZE , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_64); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +106 -0
124 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 12/29 KVM: selftests: TDX: Add basic get_td_vmcall_info test
In reply to Sagi ShaharThe test calls get_td_vmcall_info from the guest and verifies the expected returned values.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 3 + .../kvm/include/x86_64/tdx/test_util.h | 27 +++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 23 ++++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 46 +++++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 80 +++++++++++++++++++ 5 files changed, 179 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +3 -0
@@ -5,6 +5,7 @@#include <stdint.h> #include "kvm_util_base.h" +#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_IO 30
@@ -12,5 +13,7 @@ void handle_userspace_tdg_vp_vmcall_exit(struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data);void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa); +uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12, +uint64_t *r13,uint64_t *r14);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +27 -0
@@ -4,6 +4,7 @@#include <stdbool.h> +#include "kvm_util_base.h" #include "tdcall.h" #define TDX_TEST_SUCCESS_PORT 0x30
@@ -111,4 +112,30 @@ void tdx_test_fatal_with_data(uint64_t error_code, uint64_t data_gpa);*/ uint64_t tdx_test_report_to_user_space (uint32_t data); +/** +* Report a 64 bit value from the guest to user space using TDG.VP.VMCALL +* <Instruction.IO> call. +* +* Data is sent to host in 2 calls. LSB is sent (and needs to be read) first. +*/ +uint64_t tdx_test_send_64bit (uint64_t port,uint64_t data); + +/** +* Report a 64 bit value from the guest to user space using TDG.VP.VMCALL +* <Instruction.IO> call. Data is reported on port TDX_TEST_REPORT_PORT. +*/ +uint64_t tdx_test_report_64bit_to_user_space (uint64_t data); + +/** +* Read a 64 bit value from the guest in user space, sent using +* tdx_test_send_64bit(). +*/ +uint64_t tdx_test_read_64bit (struct kvm_vcpu *vcpu,uint64_t port); + +/** +* Read a 64 bit value from the guest in user space, sent using +* tdx_test_report_64bit_to_user_space. +*/ +uint64_t tdx_test_read_64bit_report_from_guest (struct kvm_vcpu *vcpu); +#endif // SELFTEST_TDX_TEST_UTIL_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23 -0
@@ -64,3 +64,26 @@ void tdg_vp_vmcall_report_fatal_error(uint64_t error_code, uint64_t data_gpa)__tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12, +uint64_t *r13,uint64_t *r14) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_GET_TD_VM_CALL_INFO , + .r12 =0 , + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (r11) + *r11 = args.r11; +if (r12) + *r12 = args.r12; +if (r13) + *r13 = args.r13; +if (r14) + *r14 = args.r14; + +return ret; +}
tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +46 -0
55 lines not on this page · raw message
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +80 -0
92 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 12/29] KVM: selftests: TDX: Add basic get_td_vmcall_info test
Quoted 6 lines · Sagi Shahar
The test calls
get_td_vmcall_infofrom the guest and verifies the expected returned values.Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>
Quoted 7 lines
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 3 + .../kvm/include/x86_64/tdx/test_util.h | 27 +++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 23 ++++++ .../selftests/kvm/lib/x86_64/tdx/test_util.c | 46 +++++++++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 80 +++++++++++++++++++ 5 files changed, 179 insertions(+)
Also, does it need to add another case for the non-zero value of r12 to test the VMCALL_INVALID_OPERAND path?
Quoted 254 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +3
-0@@ -5,6 +5,7 @@#include <stdint.h> #include "kvm_util_base.h" +#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_IO 30@@ -12,5 +13,7 @@ void handle_userspace_tdg_vp_vmcall_exit(struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data);void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa); +uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12, +uint64_t *r13,uint64_t *r14);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +27
-0@@ -4,6 +4,7 @@#include <stdbool.h> +#include "kvm_util_base.h" #include "tdcall.h" #define TDX_TEST_SUCCESS_PORT 0x30@@ -111,4 +112,30 @@ void tdx_test_fatal_with_data(uint64_t error_code, uint64_t data_gpa);*/ uint64_t tdx_test_report_to_user_space (uint32_t data); +/** +* Report a 64 bit value from the guest to user space using TDG.VP.VMCALL +* <Instruction.IO> call. +* +* Data is sent to host in 2 calls. LSB is sent (and needs to be read) first. +*/ +uint64_t tdx_test_send_64bit (uint64_t port,uint64_t data); + +/** +* Report a 64 bit value from the guest to user space using TDG.VP.VMCALL +* <Instruction.IO> call. Data is reported on port TDX_TEST_REPORT_PORT. +*/ +uint64_t tdx_test_report_64bit_to_user_space (uint64_t data); + +/** +* Read a 64 bit value from the guest in user space, sent using +* tdx_test_send_64bit(). +*/ +uint64_t tdx_test_read_64bit (struct kvm_vcpu *vcpu,uint64_t port); + +/** +* Read a 64 bit value from the guest in user space, sent using +* tdx_test_report_64bit_to_user_space. +*/ +uint64_t tdx_test_read_64bit_report_from_guest (struct kvm_vcpu *vcpu); +#endif // SELFTEST_TDX_TEST_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +23
-0@@ -64,3 +64,26 @@ void tdg_vp_vmcall_report_fatal_error(uint64_t error_code, uint64_t data_gpa)__tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12, +uint64_t *r13,uint64_t *r14) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_GET_TD_VM_CALL_INFO , + .r12 =0 , + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (r11) + *r11 = args.r11; +if (r12) + *r12 = args.r12; +if (r13) + *r13 = args.r13; +if (r14) + *r14 = args.r14; + +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/test_util.c +46
-0@@ -7,6 +7,7 @@#include <unistd.h> #include "kvm_util_base.h" +#include "tdx/tdcall.h" #include "tdx/tdx.h" #include "tdx/test_util.h" @@ -53,3 +54,48 @@ uint64_t tdx_test_report_to_user_space(uint32_t data)TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , &data_64); } + +uint64_t tdx_test_send_64bit (uint64_t port,uint64_t data) +{ +uint64_t err; +uint64_t data_lo = data &0xFFFFFFFF ; +uint64_t data_hi = (data >>32 ) &0xFFFFFFFF ; + + err =tdg_vp_vmcall_instruction_io (port,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_lo); +if (err) +return err; + +return tdg_vp_vmcall_instruction_io (port,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &data_hi); +} + +uint64_t tdx_test_report_64bit_to_user_space (uint64_t data) +{ +return tdx_test_send_64bit (TDX_TEST_REPORT_PORT , data); +} + +uint64_t tdx_test_read_64bit (struct kvm_vcpu *vcpu,uint64_t port) +{ +uint32_t lo, hi; +uint64_t res; + +TDX_TEST_ASSERT_IO (vcpu, port,4 ,TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + lo = *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +vcpu_run (vcpu); + +TDX_TEST_ASSERT_IO (vcpu, port,4 ,TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + hi = *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + + res = hi; + res = (res <<32 ) | lo; +return res; +} + +uint64_t tdx_test_read_64bit_report_from_guest (struct kvm_vcpu *vcpu) +{ +return tdx_test_read_64bit (vcpu,TDX_TEST_REPORT_PORT ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +80
-0@@ -260,6 +260,85 @@ void verify_td_cpuid(void)printf ("\t ... PASSED\n" ); } +/* +* Verifies get_td_vmcall_info functionality. +*/ +void guest_code_get_td_vmcall_info (void ) +{ +uint64_t err; +uint64_t r11, r12, r13, r14; + + err =tdg_vp_vmcall_get_td_vmcall_info (&r11, &r12, &r13, &r14); +if (err) +tdx_test_fatal (err); + + err =tdx_test_report_64bit_to_user_space (r11); +if (err) +tdx_test_fatal (err); + + err =tdx_test_report_64bit_to_user_space (r12); +if (err) +tdx_test_fatal (err); + + err =tdx_test_report_64bit_to_user_space (r13); +if (err) +tdx_test_fatal (err); + + err =tdx_test_report_64bit_to_user_space (r14); +if (err) +tdx_test_fatal (err); + +tdx_test_success (); +} + +void verify_get_td_vmcall_info (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint64_t r11, r12, r13, r14; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_code_get_td_vmcall_info); +td_finalize (vm); + +printf ("Verifying TD get vmcall info:\n" ); + +/* Wait for guest to report r11 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r11 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r12 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r12 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r13 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r13 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r14 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r14 =tdx_test_read_64bit_report_from_guest (vcpu); + +TEST_ASSERT_EQ (r11,0 ); +TEST_ASSERT_EQ (r12,0 ); +TEST_ASSERT_EQ (r13,0 ); +TEST_ASSERT_EQ (r14,0 ); + +/* Wait for guest to complete execution */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -273,6 +352,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_report_fatal_error);run_in_new_process (&verify_td_ioexit);run_in_new_process (&verify_td_cpuid); +run_in_new_process (&verify_get_td_vmcall_info);return 0 ; }
RFC PATCH v5 13/29 KVM: selftests: TDX: Add TDX IO writes test
In reply to Sagi ShaharThe test verifies IO writes of various sizes from the guest to the host.
--- .../selftests/kvm/include/x86_64/tdx/tdcall.h | 3 + .../selftests/kvm/x86_64/tdx_vm_tests.c | 91 +++++++++++++++++++ 2 files changed, 94 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h +3 -0
@@ -10,6 +10,9 @@#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 +#define TDG_VP_VMCALL_SUCCESS 0x0000000000000000 +#define TDG_VP_VMCALL_INVALID_OPERAND 0x8000000000000000 +#define TDX_HCALL_HAS_OUTPUT BIT(0)#define TDX_HYPERCALL_STANDARD 0
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +91 -0
103 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 13/29] KVM: selftests: TDX: Add TDX IO writes test
Quoted 9 lines · Sagi Shahar
The test verifies IO writes of various sizes from the guest to the host.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdcall.h | 3 + .../selftests/kvm/x86_64/tdx_vm_tests.c | 91 +++++++++++++++++++ 2 files changed, 94 insertions(+)
Quoted 124 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h +3
-0@@ -10,6 +10,9 @@#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 +#define TDG_VP_VMCALL_SUCCESS 0x0000000000000000 +#define TDG_VP_VMCALL_INVALID_OPERAND 0x8000000000000000 +#define TDX_HCALL_HAS_OUTPUT BIT(0)#define TDX_HYPERCALL_STANDARD 0tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +91
-0@@ -339,6 +339,96 @@ void verify_get_td_vmcall_info(void)printf ("\t ... PASSED\n" ); } +#define TDX_IO_WRITES_TEST_PORT 0x51 + +/* +* Verifies IO functionality by writing values of different sizes +* to the host. +*/ +void guest_io_writes (void ) +{ +uint64_t byte_1 =0xAB ; +uint64_t byte_2 =0xABCD ; +uint64_t byte_4 =0xFFABCDEF ; +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_WRITES_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &byte_1); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_WRITES_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &byte_2); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_WRITES_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &byte_4); +if (ret) +tdx_test_fatal (ret); + +// Write an invalid number of bytes. + ret =tdg_vp_vmcall_instruction_io (TDX_IO_WRITES_TEST_PORT ,5 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &byte_4); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_guest_writes (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint8_t byte_1; +uint16_t byte_2; +uint32_t byte_4; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_io_writes); +td_finalize (vm); + +printf ("Verifying guest writes:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_WRITES_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + byte_1 = *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_WRITES_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + byte_2 = *(uint16_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_WRITES_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); + byte_4 = *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset); + +TEST_ASSERT_EQ (byte_1,0xAB ); +TEST_ASSERT_EQ (byte_2,0xABCD ); +TEST_ASSERT_EQ (byte_4,0xFFABCDEF ); + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -353,6 +443,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_ioexit);run_in_new_process (&verify_td_cpuid);run_in_new_process (&verify_get_td_vmcall_info); +run_in_new_process (&verify_guest_writes);return 0 ; }
RFC PATCH v5 14/29 KVM: selftests: TDX: Add TDX IO reads test
In reply to Sagi ShaharThe test verifies IO reads of various sizes from the host to the guest.
--- .../selftests/kvm/x86_64/tdx_vm_tests.c | 87 +++++++++++++++++++ 1 file changed, 87 insertions(+)
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +87 -0
@@ -429,6 +429,92 @@ void verify_guest_writes(void)printf ("\t ... PASSED\n" ); } +#define TDX_IO_READS_TEST_PORT 0x52 + +/* +* Verifies IO functionality by reading values of different sizes +* from the host. +*/ +void guest_io_reads (void ) +{ +uint64_t data; +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xAB ) +tdx_test_fatal (1 ); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xABCD ) +tdx_test_fatal (2 ); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xFFABCDEF ) +tdx_test_fatal (4 ); + +// Read an invalid number of bytes. + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,5 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_guest_reads (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_io_reads); +td_finalize (vm); + +printf ("Verifying guest reads:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xAB ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint16_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xABCD ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xFFABCDEF ; + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );
@@ -444,6 +530,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_cpuid);run_in_new_process (&verify_get_td_vmcall_info);run_in_new_process (&verify_guest_writes); +run_in_new_process (&verify_guest_reads);return 0 ; }
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 14/29] KVM: selftests: TDX: Add TDX IO reads test
Quoted 8 lines · Sagi Shahar
The test verifies IO reads of various sizes from the host to the guest.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/x86_64/tdx_vm_tests.c | 87 +++++++++++++++++++ 1 file changed, 87 insertions(+)
Quoted 106 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +87
-0@@ -429,6 +429,92 @@ void verify_guest_writes(void)printf ("\t ... PASSED\n" ); } +#define TDX_IO_READS_TEST_PORT 0x52 + +/* +* Verifies IO functionality by reading values of different sizes +* from the host. +*/ +void guest_io_reads (void ) +{ +uint64_t data; +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xAB ) +tdx_test_fatal (1 ); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xABCD ) +tdx_test_fatal (2 ); + + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0xFFABCDEF ) +tdx_test_fatal (4 ); + +// Read an invalid number of bytes. + ret =tdg_vp_vmcall_instruction_io (TDX_IO_READS_TEST_PORT ,5 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ , + &data); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_guest_reads (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_io_reads); +td_finalize (vm); + +printf ("Verifying guest reads:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,1 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint8_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xAB ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,2 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint16_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xABCD ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_IO_READS_TEST_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_READ ); + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset) =0xFFABCDEF ; + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -444,6 +530,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_td_cpuid);run_in_new_process (&verify_get_td_vmcall_info);run_in_new_process (&verify_guest_writes); +run_in_new_process (&verify_guest_reads);return 0 ; }
RFC PATCH v5 15/29 KVM: selftests: TDX: Add TDX MSR read/write tests
In reply to Sagi ShaharThe test verifies reads and writes for MSR registers with different access level.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 5 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 209 ++++++++++++++++++ 3 files changed, 241 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5 -0
@@ -9,11 +9,16 @@#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31 +#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data);void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12,uint64_t *r13,uint64_t *r14); +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value); +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +27 -0
@@ -87,3 +87,30 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12,return ret; } + +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_RDMSR , + .r12 = index, + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (ret_value) + *ret_value = args.r11; + +return ret; +} + +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_WRMSR , + .r12 = index, + .r13 = value, + }; + +return __tdx_hypercall (&args,0 ); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +209 -0
221 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 15/29] KVM: selftests: TDX: Add TDX MSR read/write tests
Quoted 73 lines · Sagi Shahar
The test verifies reads and writes for MSR registers with different access level.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 5 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 209 ++++++++++++++++++ 3 files changed, 241 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5
-0@@ -9,11 +9,16 @@#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31 +#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32 +void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data);void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12,uint64_t *r13,uint64_t *r14); +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value); +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +27
-0@@ -87,3 +87,30 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12,return ret; } + +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_RDMSR , + .r12 = index, + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (ret_value) + *ret_value = args.r11; + +return ret; +} + +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_WRMSR , + .r12 = index, + .r13 = value, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +0
-0
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_reads(void) · line 520
Quoted 6 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +3
-0@@ -515,6 +515,213 @@ void verify_guest_reads(void)printf ("\t ... PASSED\n" ); } +/* +* Define a filter which denies all MSR access except the following: +* MSR_X2APIC_APIC_ICR: Allow read/write access (allowed by default)
The default filtering behavior of tdx_msr_test_filter is KVM_MSR_FILTER_DEFAULT_DENY, and MSR_X2APIC_APIC_ICR is not covered by any specific range, shouldn't MSR_X2APIC_APIC_ICR be denied by default?
Quoted 216 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +206
-0+* MSR_IA32_MISC_ENABLE: Allow read access +* MSR_IA32_POWER_CTL: Allow write access +*/ +#define MSR_X2APIC_APIC_ICR 0x830 +static u64 tdx_msr_test_allow_bits =0xFFFFFFFFFFFFFFFF ; +struct kvm_msr_filter tdx_msr_test_filter = { + .flags =KVM_MSR_FILTER_DEFAULT_DENY , + .ranges = { + { + .flags =KVM_MSR_FILTER_READ , + .nmsrs =1 , + .base =MSR_IA32_MISC_ENABLE , + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, { + .flags =KVM_MSR_FILTER_WRITE , + .nmsrs =1 , + .base =MSR_IA32_POWER_CTL , + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, + }, +}; + +/* +* Verifies MSR read functionality. +*/ +void guest_msr_read (void ) +{ +uint64_t data; +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_X2APIC_APIC_ICR , &data); +if (ret) +tdx_test_fatal (ret); + + ret =tdx_test_report_64bit_to_user_space (data); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_IA32_MISC_ENABLE , &data); +if (ret) +tdx_test_fatal (ret); + + ret =tdx_test_report_64bit_to_user_space (data); +if (ret) +tdx_test_fatal (ret); + +/* We expect this call to fail since MSR_IA32_POWER_CTL is write only */ + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_IA32_POWER_CTL , &data); +if (ret) { + ret =tdx_test_report_64bit_to_user_space (ret); +if (ret) +tdx_test_fatal (ret); + }else { +tdx_test_fatal (-99 ); + } + +tdx_test_success (); +} + +void verify_guest_msr_reads (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint64_t data; +int ret; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + +/* +* Set explicit MSR filter map to control access to the MSR registers +* used in the test. +*/ +printf ("\t ... Setting test MSR filter\n" ); + ret =kvm_check_cap (KVM_CAP_X86_USER_SPACE_MSR ); +TEST_ASSERT (ret,"KVM_CAP_X86_USER_SPACE_MSR is unavailable" ); +vm_enable_cap (vm,KVM_CAP_X86_USER_SPACE_MSR ,KVM_MSR_EXIT_REASON_FILTER ); + + ret =kvm_check_cap (KVM_CAP_X86_MSR_FILTER ); +TEST_ASSERT (ret,"KVM_CAP_X86_MSR_FILTER is unavailable" ); + + ret =ioctl (vm->fd,KVM_X86_SET_MSR_FILTER , &tdx_msr_test_filter); +TEST_ASSERT (ret ==0 , +"KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)" , + ret, errno,strerror (errno)); + + vcpu =td_vcpu_add (vm,0 , guest_msr_read); +td_finalize (vm); + +printf ("Verifying guest msr reads:\n" ); + +printf ("\t ... Setting test MSR values\n" ); +/* Write arbitrary to the MSRs. */ +vcpu_set_msr (vcpu,MSR_X2APIC_APIC_ICR ,4 ); +vcpu_set_msr (vcpu,MSR_IA32_MISC_ENABLE ,5 ); +vcpu_set_msr (vcpu,MSR_IA32_POWER_CTL ,6 ); + +printf ("\t ... Running guest\n" ); +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,4 ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,5 ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +/* +* Verifies MSR write functionality. +*/ +void guest_msr_write (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_X2APIC_APIC_ICR ,4 ); +if (ret) +tdx_test_fatal (ret); + +/* We expect this call to fail since MSR_IA32_MISC_ENABLE is read only */ + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_IA32_MISC_ENABLE ,5 ); +if (ret) { + ret =tdx_test_report_64bit_to_user_space (ret); +if (ret) +tdx_test_fatal (ret); + }else { +tdx_test_fatal (-99 ); + } + + + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_IA32_POWER_CTL ,6 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_guest_msr_writes (void ) +{ +struct kvm_vcpu *vcpu; +struct kvm_vm *vm; + +uint64_t data; +int ret; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + +/* +* Set explicit MSR filter map to control access to the MSR registers +* used in the test. +*/ +printf ("\t ... Setting test MSR filter\n" ); + ret =kvm_check_cap (KVM_CAP_X86_USER_SPACE_MSR ); +TEST_ASSERT (ret,"KVM_CAP_X86_USER_SPACE_MSR is unavailable" ); +vm_enable_cap (vm,KVM_CAP_X86_USER_SPACE_MSR ,KVM_MSR_EXIT_REASON_FILTER ); + + ret =kvm_check_cap (KVM_CAP_X86_MSR_FILTER ); +TEST_ASSERT (ret,"KVM_CAP_X86_MSR_FILTER is unavailable" ); + + ret =ioctl (vm->fd,KVM_X86_SET_MSR_FILTER , &tdx_msr_test_filter); +TEST_ASSERT (ret ==0 , +"KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)" , + ret, errno,strerror (errno)); + + vcpu =td_vcpu_add (vm,0 , guest_msr_write); +td_finalize (vm); + +printf ("Verifying guest msr writes:\n" ); + +printf ("\t ... Running guest\n" ); +/* Only the write to MSR_IA32_MISC_ENABLE should trigger an exit */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... Verifying MSR values writen by guest\n" ); + +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_X2APIC_APIC_ICR ),4 ); +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_MISC_ENABLE ),0x1800 ); +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_POWER_CTL ),6 ); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -531,6 +738,8 @@ int main(int argc, char **argv)run_in_new_process (&verify_get_td_vmcall_info);run_in_new_process (&verify_guest_writes);run_in_new_process (&verify_guest_reads); +run_in_new_process (&verify_guest_msr_writes); +run_in_new_process (&verify_guest_msr_reads);return 0 ; }
Re: [RFC PATCH v5 15/29] KVM: selftests: TDX: Add TDX MSR read/write tests
Quoted 79 lines · Binbin Wu
Quoted 76 lines · Sagi Shahar
The test verifies reads and writes for MSR registers with different access level.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>---
.../selftests/kvm/include/x86_64/tdx/tdx.h | 5 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 209 ++++++++++++++++++3 files changed, 241 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5
-0@@ -9,11 +9,16 @@ #define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 #define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31 +#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32 + void handle_userspace_tdg_vp_vmcall_exit(struct kvm_vcpu *vcpu); uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size, uint64_t write, uint64_t *data); void tdg_vp_vmcall_report_fatal_error(uint64_t error_code, uint64_t data_gpa); uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, uint64_t *r13, uint64_t *r14); +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value); +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value); #endif // SELFTEST_TDX_TDX_Htools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +2
-0@@ -87,3 +87,30 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, return ret; } + +uint64_t tdg_vp_vmcall_instruction_rdmsr(uint64_t index, uint64_t
*ret_value)tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +16
-0+{ + uint64_t ret; + struct tdx_hypercall_args args = { + .r11 = TDG_VP_VMCALL_INSTRUCTION_RDMSR, + .r12 = index, + }; + + ret = __tdx_hypercall(&args, TDX_HCALL_HAS_OUTPUT); + + if (ret_value) + *ret_value = args.r11; + + return ret; +} + +uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_tvalue)
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +9
-0+{ + struct tdx_hypercall_args args = { + .r11 = TDG_VP_VMCALL_INSTRUCTION_WRMSR, + .r12 = index, + .r13 = value, + }; + + return __tdx_hypercall(&args, 0); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +0
-0@@ -515,6 +515,213 @@ void verify_guest_reads(void) printf("\t ... PASSED\n");
Quoted 8 lines
Quoted 4 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +0
-0}+/*
+ * Define a filter which denies all MSR access except the following:
+ *MSR_X2APIC_APIC_ICR: Allow read/write access (allowed by default)The default filtering behavior of
tdx_msr_test_filterisKVM_MSR_FILTER_DEFAULT_DENY, andMSR_X2APIC_APIC_ICRis not covered by any specific range, shouldn'tMSR_X2APIC_APIC_ICRbe denied by default?
Sorry, please ignore this comment.
I see the description from the KVM document later:
"x2APIC MSR accesses cannot be filtered (KVM silently ignores filters that cover any x2APIC MSRs)."
Quoted 224 lines
Quoted 222 lines
+ *
MSR_IA32_MISC_ENABLE: Allow read access
+ *MSR_IA32_POWER_CTL: Allow write access
+ */tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +44
-0+#define MSR_X2APIC_APIC_ICR 0x830 +static u64 tdx_msr_test_allow_bits =0xFFFFFFFFFFFFFFFF ; +struct kvm_msr_filter tdx_msr_test_filter = { + .flags = KVM_MSR_FILTER_DEFAULT_DENY, + .ranges = { + { + .flags = KVM_MSR_FILTER_READ, + .nmsrs = 1, + .base = MSR_IA32_MISC_ENABLE, + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, { + .flags = KVM_MSR_FILTER_WRITE, + .nmsrs = 1, + .base = MSR_IA32_POWER_CTL, + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, + }, +}; + +/* +* Verifies MSR read functionality. +*/ +void guest_msr_read (void ) +{ + uint64_t data; + uint64_t ret; + + ret = tdg_vp_vmcall_instruction_rdmsr(MSR_X2APIC_APIC_ICR, &data); + if (ret) + tdx_test_fatal(ret); + + ret = tdx_test_report_64bit_to_user_space(data); + if (ret) + tdx_test_fatal(ret); + + ret = tdg_vp_vmcall_instruction_rdmsr(MSR_IA32_MISC_ENABLE, &data); + if (ret) + tdx_test_fatal(ret); + + ret = tdx_test_report_64bit_to_user_space(data); + if (ret) + tdx_test_fatal(ret); + + /* We expect this call to fail since MSR_IA32_POWER_CTL is writeonly */
+ ret =tdg_vp_vmcall_instruction_rdmsr(MSR_IA32_POWER_CTL, &data); + if (ret) {
+ ret =tdx_test_report_64bit_to_user_space(ret);
+ if (ret)
+tdx_test_fatal(ret);
+ } else {
+tdx_test_fatal(-99);
+ }tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +17
-0+ + tdx_test_success(); +} + +void verify_guest_msr_reads (void ) +{ + struct kvm_vm *vm; + struct kvm_vcpu *vcpu; + + uint64_t data; + int ret; + + vm = td_create(); + td_initialize(vm, VM_MEM_SRC_ANONYMOUS, 0); + + /* +* Set explicit MSR filter map to control access to the MSR registers
+ * used in the test.
+ */
+ printf("\t ... Setting test MSR filter\n");
+ ret =kvm_check_cap(KVM_CAP_X86_USER_SPACE_MSR);
+TEST_ASSERT(ret, "KVM_CAP_X86_USER_SPACE_MSR is unavailable"); +vm_enable_cap(vm, KVM_CAP_X86_USER_SPACE_MSR, KVM_MSR_EXIT_REASON_FILTER);tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +55
-0+ + ret = kvm_check_cap(KVM_CAP_X86_MSR_FILTER); + TEST_ASSERT(ret, "KVM_CAP_X86_MSR_FILTER is unavailable"); + + ret = ioctl(vm->fd, KVM_X86_SET_MSR_FILTER, &tdx_msr_test_filter); + TEST_ASSERT(ret == 0, + "KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)", + ret, errno, strerror(errno)); + + vcpu = td_vcpu_add(vm, 0, guest_msr_read); + td_finalize(vm); + + printf("Verifying guest msr reads:\n"); + + printf("\t ... Setting test MSR values\n"); + /* Write arbitrary to the MSRs. */ + vcpu_set_msr(vcpu, MSR_X2APIC_APIC_ICR, 4); + vcpu_set_msr(vcpu, MSR_IA32_MISC_ENABLE, 5); + vcpu_set_msr(vcpu, MSR_IA32_POWER_CTL, 6); + + printf("\t ... Running guest\n"); + td_vcpu_run(vcpu); + TDX_TEST_CHECK_GUEST_FAILURE(vcpu); + data = tdx_test_read_64bit_report_from_guest(vcpu); + TEST_ASSERT_EQ(data, 4); + + td_vcpu_run(vcpu); + TDX_TEST_CHECK_GUEST_FAILURE(vcpu); + data = tdx_test_read_64bit_report_from_guest(vcpu); + TEST_ASSERT_EQ(data, 5); + + td_vcpu_run(vcpu); + TDX_TEST_CHECK_GUEST_FAILURE(vcpu); + data = tdx_test_read_64bit_report_from_guest(vcpu); + TEST_ASSERT_EQ(data, TDG_VP_VMCALL_INVALID_OPERAND); + + td_vcpu_run(vcpu); + TDX_TEST_ASSERT_SUCCESS(vcpu); + + kvm_vm_free(vm); + printf("\t ... PASSED\n"); +} + +/* +* Verifies MSR write functionality. +*/ +void guest_msr_write (void ) +{ + uint64_t ret; + + ret = tdg_vp_vmcall_instruction_wrmsr(MSR_X2APIC_APIC_ICR, 4); + if (ret) + tdx_test_fatal(ret); + + /* We expect this call to fail since MSR_IA32_MISC_ENABLE isread only */
+ ret =tdg_vp_vmcall_instruction_wrmsr(MSR_IA32_MISC_ENABLE, 5); + if (ret) {
+ ret =tdx_test_report_64bit_to_user_space(ret); + if (ret)
+tdx_test_fatal(ret);
+ } else {
+tdx_test_fatal(-99);
+ }tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +22
-0+ + + ret = tdg_vp_vmcall_instruction_wrmsr(MSR_IA32_POWER_CTL, 6); + if (ret) + tdx_test_fatal(ret); + + tdx_test_success(); +} + +void verify_guest_msr_writes (void ) +{ + struct kvm_vcpu *vcpu; + struct kvm_vm *vm; + + uint64_t data; + int ret; + + vm = td_create(); + td_initialize(vm, VM_MEM_SRC_ANONYMOUS, 0); + + /* +* Set explicit MSR filter map to control access to the MSR registers
+ * used in the test.
+ */
+ printf("\t ... Setting test MSR filter\n");
+ ret =kvm_check_cap(KVM_CAP_X86_USER_SPACE_MSR);
+TEST_ASSERT(ret, "KVM_CAP_X86_USER_SPACE_MSR is unavailable"); +vm_enable_cap(vm, KVM_CAP_X86_USER_SPACE_MSR, KVM_MSR_EXIT_REASON_FILTER);tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +35
-0+ + ret = kvm_check_cap(KVM_CAP_X86_MSR_FILTER); + TEST_ASSERT(ret, "KVM_CAP_X86_MSR_FILTER is unavailable"); + + ret = ioctl(vm->fd, KVM_X86_SET_MSR_FILTER, &tdx_msr_test_filter); + TEST_ASSERT(ret == 0, + "KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)", + ret, errno, strerror(errno)); + + vcpu = td_vcpu_add(vm, 0, guest_msr_write); + td_finalize(vm); + + printf("Verifying guest msr writes:\n"); + + printf("\t ... Running guest\n"); + /* Only the write to MSR_IA32_MISC_ENABLE should trigger an exit */ + td_vcpu_run(vcpu); + TDX_TEST_CHECK_GUEST_FAILURE(vcpu); + data = tdx_test_read_64bit_report_from_guest(vcpu); + TEST_ASSERT_EQ(data, TDG_VP_VMCALL_INVALID_OPERAND); + + td_vcpu_run(vcpu); + TDX_TEST_ASSERT_SUCCESS(vcpu); + + printf("\t ... Verifying MSR values writen by guest\n"); + + TEST_ASSERT_EQ(vcpu_get_msr(vcpu, MSR_X2APIC_APIC_ICR), 4); + TEST_ASSERT_EQ(vcpu_get_msr(vcpu, MSR_IA32_MISC_ENABLE), 0x1800); + TEST_ASSERT_EQ(vcpu_get_msr(vcpu, MSR_IA32_POWER_CTL), 6); + + kvm_vm_free(vm); + printf("\t ... PASSED\n"); +} + +int
main(int argc, char **argv)
{
setbuf(stdout, NULL);tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +2
-0@@ -531,6 +738,8 @@ int main(int argc, char **argv) run_in_new_process(&verify_get_td_vmcall_info); run_in_new_process(&verify_guest_writes); run_in_new_process(&verify_guest_reads); + run_in_new_process(&verify_guest_msr_writes); + run_in_new_process(&verify_guest_msr_reads); return 0; }
Re: [RFC PATCH v5 15/29] KVM: selftests: TDX: Add TDX MSR read/write tests
In reply to Sagi ShaharQuoted 37 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +37
-0+void verify_guest_msr_writes (void ) +{ +struct kvm_vcpu *vcpu; +struct kvm_vm *vm; + +uint64_t data; +int ret; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + +/* +* Set explicit MSR filter map to control access to the MSR registers +* used in the test. +*/ +printf ("\t ... Setting test MSR filter\n" ); + ret =kvm_check_cap (KVM_CAP_X86_USER_SPACE_MSR ); +TEST_ASSERT (ret,"KVM_CAP_X86_USER_SPACE_MSR is unavailable" ); +vm_enable_cap (vm,KVM_CAP_X86_USER_SPACE_MSR ,KVM_MSR_EXIT_REASON_FILTER ); + + ret =kvm_check_cap (KVM_CAP_X86_MSR_FILTER ); +TEST_ASSERT (ret,"KVM_CAP_X86_MSR_FILTER is unavailable" ); + + ret =ioctl (vm->fd,KVM_X86_SET_MSR_FILTER , &tdx_msr_test_filter); +TEST_ASSERT (ret ==0 , +"KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)" , + ret, errno,strerror (errno)); + + vcpu =td_vcpu_add (vm,0 , guest_msr_write); +td_finalize (vm); + +printf ("Verifying guest msr writes:\n" ); + +printf ("\t ... Running guest\n" ); +/* Only the write to MSR_IA32_MISC_ENABLE should trigger an exit */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_reads(void) · line 717
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... Verifying MSR values writen by guest\n" ); + +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_X2APIC_APIC_ICR ),4 ); +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_MISC_ENABLE ),0x1800 );
It's not staightforward to assert MSR_IA32_MISC_ENABLE is 0x1800. Rather than assume MSR_IA32_MISC_ENABLE is reset to (MSR_IA32_MISC_ENABLE_PEBS_UNAVAIL | MSR_IA32_MISC_ENABLE_BTS_UNAVAIL) which is 0x1800, why not call vcpu_get_msr() before guest write and compare the saved value here?
Quoted 23 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +9
-0+TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_POWER_CTL ),6 ); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -531,6 +738,8 @@ int main(int argc, char **argv)run_in_new_process (&verify_get_td_vmcall_info);run_in_new_process (&verify_guest_writes);run_in_new_process (&verify_guest_reads); +run_in_new_process (&verify_guest_msr_writes); +run_in_new_process (&verify_guest_msr_reads);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 15/29] KVM: selftests: TDX: Add TDX MSR read/write tests
In reply to Sagi ShaharQuoted 17 lines · Sagi Shahar
The test verifies reads and writes for MSR registers with different access level.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 5 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 209 ++++++++++++++++++ 3 files changed, 241 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +0
-0
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h line 13
Quoted 5 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -9,11 +9,16 @@#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_IO 30 +#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31 +#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32
Nit:
"arch/x86/include/uapi/asm/vmx.h" already defined the following defs:
#define EXIT_REASON_IO_INSTRUCTION 30 #define EXIT_REASON_MSR_READ 31 #define EXIT_REASON_MSR_WRITE 32
Quoted 52 lines
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +3
-0+void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu);uint64_t tdg_vp_vmcall_instruction_io (uint64_t port,uint64_t size,uint64_t write,uint64_t *data);void tdg_vp_vmcall_report_fatal_error (uint64_t error_code,uint64_t data_gpa);uint64_t tdg_vp_vmcall_get_td_vmcall_info (uint64_t *r11,uint64_t *r12,uint64_t *r13,uint64_t *r14); +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value); +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +27
-0@@ -87,3 +87,30 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12,return ret; } + +uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_RDMSR , + .r12 = index, + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (ret_value) + *ret_value = args.r11; + +return ret; +} + +uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_WRMSR , + .r12 = index, + .r13 = value, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +0
-0@@ -515,6 +515,213 @@ void verify_guest_reads(void)printf ("\t ... PASSED\n" );
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_reads(void) · line 525
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +8
-0} +/* +* Define a filter which denies all MSR access except the following: +* MSR_X2APIC_APIC_ICR: Allow read/write access (allowed by default) +* MSR_IA32_MISC_ENABLE: Allow read access +* MSR_IA32_POWER_CTL: Allow write access +*/ +#define MSR_X2APIC_APIC_ICR 0x830 +static u64 tdx_msr_test_allow_bits =0xFFFFFFFFFFFFFFFF ;
Nit:0xFFFFFFFFFFFFFFFF is error prone to define? the following? static u64 tdx_msr_test_allow_bits = ~0ULL;
Quoted 211 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +201
-0+struct kvm_msr_filter tdx_msr_test_filter = { + .flags =KVM_MSR_FILTER_DEFAULT_DENY , + .ranges = { + { + .flags =KVM_MSR_FILTER_READ , + .nmsrs =1 , + .base =MSR_IA32_MISC_ENABLE , + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, { + .flags =KVM_MSR_FILTER_WRITE , + .nmsrs =1 , + .base =MSR_IA32_POWER_CTL , + .bitmap = (uint8_t *)&tdx_msr_test_allow_bits, + }, + }, +}; + +/* +* Verifies MSR read functionality. +*/ +void guest_msr_read (void ) +{ +uint64_t data; +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_X2APIC_APIC_ICR , &data); +if (ret) +tdx_test_fatal (ret); + + ret =tdx_test_report_64bit_to_user_space (data); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_IA32_MISC_ENABLE , &data); +if (ret) +tdx_test_fatal (ret); + + ret =tdx_test_report_64bit_to_user_space (data); +if (ret) +tdx_test_fatal (ret); + +/* We expect this call to fail since MSR_IA32_POWER_CTL is write only */ + ret =tdg_vp_vmcall_instruction_rdmsr (MSR_IA32_POWER_CTL , &data); +if (ret) { + ret =tdx_test_report_64bit_to_user_space (ret); +if (ret) +tdx_test_fatal (ret); + }else { +tdx_test_fatal (-99 ); + } + +tdx_test_success (); +} + +void verify_guest_msr_reads (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint64_t data; +int ret; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + +/* +* Set explicit MSR filter map to control access to the MSR registers +* used in the test. +*/ +printf ("\t ... Setting test MSR filter\n" ); + ret =kvm_check_cap (KVM_CAP_X86_USER_SPACE_MSR ); +TEST_ASSERT (ret,"KVM_CAP_X86_USER_SPACE_MSR is unavailable" ); +vm_enable_cap (vm,KVM_CAP_X86_USER_SPACE_MSR ,KVM_MSR_EXIT_REASON_FILTER ); + + ret =kvm_check_cap (KVM_CAP_X86_MSR_FILTER ); +TEST_ASSERT (ret,"KVM_CAP_X86_MSR_FILTER is unavailable" ); + + ret =ioctl (vm->fd,KVM_X86_SET_MSR_FILTER , &tdx_msr_test_filter); +TEST_ASSERT (ret ==0 , +"KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)" , + ret, errno,strerror (errno)); + + vcpu =td_vcpu_add (vm,0 , guest_msr_read); +td_finalize (vm); + +printf ("Verifying guest msr reads:\n" ); + +printf ("\t ... Setting test MSR values\n" ); +/* Write arbitrary to the MSRs. */ +vcpu_set_msr (vcpu,MSR_X2APIC_APIC_ICR ,4 ); +vcpu_set_msr (vcpu,MSR_IA32_MISC_ENABLE ,5 ); +vcpu_set_msr (vcpu,MSR_IA32_POWER_CTL ,6 ); + +printf ("\t ... Running guest\n" ); +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,4 ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,5 ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +/* +* Verifies MSR write functionality. +*/ +void guest_msr_write (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_X2APIC_APIC_ICR ,4 ); +if (ret) +tdx_test_fatal (ret); + +/* We expect this call to fail since MSR_IA32_MISC_ENABLE is read only */ + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_IA32_MISC_ENABLE ,5 ); +if (ret) { + ret =tdx_test_report_64bit_to_user_space (ret); +if (ret) +tdx_test_fatal (ret); + }else { +tdx_test_fatal (-99 ); + } + + + ret =tdg_vp_vmcall_instruction_wrmsr (MSR_IA32_POWER_CTL ,6 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void verify_guest_msr_writes (void ) +{ +struct kvm_vcpu *vcpu; +struct kvm_vm *vm; + +uint64_t data; +int ret; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + +/* +* Set explicit MSR filter map to control access to the MSR registers +* used in the test. +*/ +printf ("\t ... Setting test MSR filter\n" ); + ret =kvm_check_cap (KVM_CAP_X86_USER_SPACE_MSR ); +TEST_ASSERT (ret,"KVM_CAP_X86_USER_SPACE_MSR is unavailable" ); +vm_enable_cap (vm,KVM_CAP_X86_USER_SPACE_MSR ,KVM_MSR_EXIT_REASON_FILTER ); + + ret =kvm_check_cap (KVM_CAP_X86_MSR_FILTER ); +TEST_ASSERT (ret,"KVM_CAP_X86_MSR_FILTER is unavailable" ); + + ret =ioctl (vm->fd,KVM_X86_SET_MSR_FILTER , &tdx_msr_test_filter); +TEST_ASSERT (ret ==0 , +"KVM_X86_SET_MSR_FILTER failed, ret: %i errno: %i (%s)" , + ret, errno,strerror (errno)); + + vcpu =td_vcpu_add (vm,0 , guest_msr_write); +td_finalize (vm); + +printf ("Verifying guest msr writes:\n" ); + +printf ("\t ... Running guest\n" ); +/* Only the write to MSR_IA32_MISC_ENABLE should trigger an exit */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + data =tdx_test_read_64bit_report_from_guest (vcpu); +TEST_ASSERT_EQ (data,TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... Verifying MSR values writen by guest\n" ); + +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_X2APIC_APIC_ICR ),4 ); +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_MISC_ENABLE ),0x1800 ); +TEST_ASSERT_EQ (vcpu_get_msr (vcpu,MSR_IA32_POWER_CTL ),6 ); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -531,6 +738,8 @@ int main(int argc, char **argv)run_in_new_process (&verify_get_td_vmcall_info);run_in_new_process (&verify_guest_writes);run_in_new_process (&verify_guest_reads); +run_in_new_process (&verify_guest_msr_writes); +run_in_new_process (&verify_guest_msr_reads);return 0 ; }
RFC PATCH v5 16/29 KVM: selftests: TDX: Add TDX HLT exit test
In reply to Sagi ShaharThe test verifies that the guest runs TDVMCALL<INSTRUCTION.HLT> and the guest vCPU enters to the halted state.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 10 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 78 +++++++++++++++++++ 3 files changed, 90 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2 -0
@@ -8,6 +8,7 @@#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_HLT 12#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32
@@ -20,5 +21,6 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, uint64_t *r13, uint64_t *r14);uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value); +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +10 -0
@@ -114,3 +114,13 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_HLT , + .r12 = interrupt_blocked_flag, + }; + +return __tdx_hypercall (&args,0 ); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +78 -0
90 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 16/29] KVM: selftests: TDX: Add TDX HLT exit test
Quoted 91 lines · Sagi Shahar
The test verifies that the guest runs TDVMCALL<INSTRUCTION.HLT> and the guest vCPU enters to the halted state.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 10 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 78 +++++++++++++++++++ 3 files changed, 90 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -8,6 +8,7 @@#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_HLT 12#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32@@ -20,5 +21,6 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, uint64_t *r13, uint64_t *r14);uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value); +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +10
-0@@ -114,3 +114,13 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_HLT , + .r12 = interrupt_blocked_flag, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +33
-0@@ -721,6 +721,83 @@ void verify_guest_msr_writes(void)printf ("\t ... PASSED\n" ); } +/* +* Verifies HLT functionality. +*/ +void guest_hlt (void ) +{ +uint64_t ret; +uint64_t interrupt_blocked_flag; + + interrupt_blocked_flag =0 ; + ret =tdg_vp_vmcall_instruction_hlt (interrupt_blocked_flag); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void _verify_guest_hlt (int signum); + +void wake_me (int interval) +{ +struct sigaction action; + + action.sa_handler = _verify_guest_hlt; +sigemptyset (&action.sa_mask); + action.sa_flags =0 ; + +TEST_ASSERT (sigaction (SIGALRM , &action,NULL ) ==0 , +"Could not set the alarm handler!" ); + +alarm (interval); +} + +void _verify_guest_hlt (int signum)
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_msr_writes(void) · line 766
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+{ +struct kvm_vm *vm; +static struct kvm_vcpu *vcpu; + +/* +* This function will also be called by SIGALRM handler to check the +* vCPU MP State. If vm has been initialized, then we are in the signal +* handler. Check the MP state and let the guest run again. +*/ +if (vcpu !=NULL ) {
What if the following case if there is a bug in KVM so that:
In guest, execution of tdg_vp_vmcall_instruction_hlt() return 0, but the vcpu is not actually halted. Then guest will call tdx_test_success().
And the first call of _verify_guest_hlt() will call kvm_vm_free(vm) to free the vm, which also frees the vcpu, and 1 second later, in this path vcpu will be accessed after free.
Quoted 45 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +35
-0+struct kvm_mp_state mp_state; + +vcpu_mp_state_get (vcpu, &mp_state); +TEST_ASSERT_EQ (mp_state.mp_state,KVM_MP_STATE_HALTED ); + +/* Let the guest to run and finish the test.*/ + mp_state.mp_state =KVM_MP_STATE_RUNNABLE ; +vcpu_mp_state_set (vcpu, &mp_state); +return ; + } + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_hlt); +td_finalize (vm); + +printf ("Verifying HLT:\n" ); + +printf ("\t ... Running guest\n" ); + +/* Wait 1 second for guest to execute HLT */ +wake_me (1 ); +td_vcpu_run (vcpu); + +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +void verify_guest_hlt (void ) +{ +_verify_guest_hlt (0 ); +}int main (int argc,char **argv) {@@ -740,6 +817,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_reads);run_in_new_process (&verify_guest_msr_writes);run_in_new_process (&verify_guest_msr_reads); +run_in_new_process (&verify_guest_hlt);return 0 ; }
Re: [RFC PATCH v5 16/29] KVM: selftests: TDX: Add TDX HLT exit test
Quoted 101 lines · Binbin Wu
Quoted 87 lines · Sagi Shahar
The test verifies that the guest runs TDVMCALL<INSTRUCTION.HLT> and the guest vCPU enters to the halted state.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 10 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 78 +++++++++++++++++++ 3 files changed, 90 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -8,6 +8,7 @@#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_HLT 12#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32@@ -20,5 +21,6 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, uint64_t *r13, uint64_t *r14);uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value); +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +10
-0@@ -114,3 +114,13 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_HLT , + .r12 = interrupt_blocked_flag, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +33
-0@@ -721,6 +721,83 @@ void verify_guest_msr_writes(void)printf ("\t ... PASSED\n" ); } +/* +* Verifies HLT functionality. +*/ +void guest_hlt (void ) +{ +uint64_t ret; +uint64_t interrupt_blocked_flag; + + interrupt_blocked_flag =0 ; + ret =tdg_vp_vmcall_instruction_hlt (interrupt_blocked_flag); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void _verify_guest_hlt (int signum); + +void wake_me (int interval) +{ +struct sigaction action; + + action.sa_handler = _verify_guest_hlt; +sigemptyset (&action.sa_mask); + action.sa_flags =0 ; + +TEST_ASSERT (sigaction (SIGALRM , &action,NULL ) ==0 , +"Could not set the alarm handler!" ); + +alarm (interval); +} + +void _verify_guest_hlt (int signum)tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_msr_writes(void) · line 765
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+{ +struct kvm_vm *vm; +static struct kvm_vcpu *vcpu; + +/* +* This function will also be called by SIGALRM handler to check the +* vCPU MP State. If vm has been initialized, then we are in the signal +* handler. Check the MP state and let the guest run again. +*/ +if (vcpu !=NULL ) {What if the following case if there is a bug in KVM so that:
Quoted 8 lines
In guest, execution of
tdg_vp_vmcall_instruction_hlt()return 0, but the vcpu is not actually halted. Then guest will calltdx_test_success().And the first call of
_verify_guest_hlt()will callkvm_vm_free(vm)to free the vm, which also frees the vcpu, and 1 second later, in this path vcpu will
be accessed after free.
Right. Another possibility is that if buggy KVM returns success to guest without putting guest to halted state, the selftest will still print "PASSED" because the second _verify_guest_hlt() (after waiting for 1s) has no chance to get executed before the process exits.
Quoted 45 lines
Quoted 43 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +35
-0+struct kvm_mp_state mp_state; + +vcpu_mp_state_get (vcpu, &mp_state); +TEST_ASSERT_EQ (mp_state.mp_state,KVM_MP_STATE_HALTED ); + +/* Let the guest to run and finish the test.*/ + mp_state.mp_state =KVM_MP_STATE_RUNNABLE ; +vcpu_mp_state_set (vcpu, &mp_state); +return ; + } + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_hlt); +td_finalize (vm); + +printf ("Verifying HLT:\n" ); + +printf ("\t ... Running guest\n" ); + +/* Wait 1 second for guest to execute HLT */ +wake_me (1 ); +td_vcpu_run (vcpu); + +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +void verify_guest_hlt (void ) +{ +_verify_guest_hlt (0 ); +}int main (int argc,char **argv) {@@ -740,6 +817,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_reads);run_in_new_process (&verify_guest_msr_writes);run_in_new_process (&verify_guest_msr_reads); +run_in_new_process (&verify_guest_hlt);return 0 ; }
Re: [RFC PATCH v5 16/29] KVM: selftests: TDX: Add TDX HLT exit test
Quoted 111 lines · Yan Zhao
Quoted 101 lines · Binbin Wu
Quoted 87 lines · Sagi Shahar
The test verifies that the guest runs TDVMCALL<INSTRUCTION.HLT> and the guest vCPU enters to the halted state.
Signed-off-by Erdem Aktas <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 10 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 78 +++++++++++++++++++ 3 files changed, 90 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -8,6 +8,7 @@#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_HLT 12#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32@@ -20,5 +21,6 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12, uint64_t *r13, uint64_t *r14);uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value); +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +10
-0@@ -114,3 +114,13 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_HLT , + .r12 = interrupt_blocked_flag, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +33
-0@@ -721,6 +721,83 @@ void verify_guest_msr_writes(void)printf ("\t ... PASSED\n" ); } +/* +* Verifies HLT functionality. +*/ +void guest_hlt (void ) +{ +uint64_t ret; +uint64_t interrupt_blocked_flag; + + interrupt_blocked_flag =0 ; + ret =tdg_vp_vmcall_instruction_hlt (interrupt_blocked_flag); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +void _verify_guest_hlt (int signum); + +void wake_me (int interval) +{ +struct sigaction action; + + action.sa_handler = _verify_guest_hlt; +sigemptyset (&action.sa_mask); + action.sa_flags =0 ; + +TEST_ASSERT (sigaction (SIGALRM , &action,NULL ) ==0 , +"Could not set the alarm handler!" ); + +alarm (interval); +} + +void _verify_guest_hlt (int signum)tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_msr_writes(void) · line 765
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+{ +struct kvm_vm *vm; +static struct kvm_vcpu *vcpu; + +/* +* This function will also be called by SIGALRM handler to check the +* vCPU MP State. If vm has been initialized, then we are in the signal +* handler. Check the MP state and let the guest run again. +*/ +if (vcpu !=NULL ) {What if the following case if there is a bug in KVM so that:
Quoted 8 lines
In guest, execution of
tdg_vp_vmcall_instruction_hlt()return 0, but the vcpu is not actually halted. Then guest will calltdx_test_success().And the first call of
_verify_guest_hlt()will callkvm_vm_free(vm)to free the vm, which also frees the vcpu, and 1 second later, in this path vcpu will
be accessed after free.
Quoted 5 lines
Right. Another possibility is that if buggy KVM returns success to guest without putting guest to halted state, the selftest will still print "PASSED" because the second
_verify_guest_hlt()(after waiting for 1s) has no chance to get executed before the process exits.
It sounds like in both cases we're going to hit an assert at some point. If the VM was already freed then vcpu_mp_state_get will fail the ioctl and assert internally or crash the process. If the guest never halts and vcpu is still valid then the mp state assert will fire. Either way it would be pretty obvious that something is wrong.
Quoted 45 lines
Quoted 45 lines
Quoted 43 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +35
-0+struct kvm_mp_state mp_state; + +vcpu_mp_state_get (vcpu, &mp_state); +TEST_ASSERT_EQ (mp_state.mp_state,KVM_MP_STATE_HALTED ); + +/* Let the guest to run and finish the test.*/ + mp_state.mp_state =KVM_MP_STATE_RUNNABLE ; +vcpu_mp_state_set (vcpu, &mp_state); +return ; + } + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_hlt); +td_finalize (vm); + +printf ("Verifying HLT:\n" ); + +printf ("\t ... Running guest\n" ); + +/* Wait 1 second for guest to execute HLT */ +wake_me (1 ); +td_vcpu_run (vcpu); + +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} + +void verify_guest_hlt (void ) +{ +_verify_guest_hlt (0 ); +}int main (int argc,char **argv) {@@ -740,6 +817,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_reads);run_in_new_process (&verify_guest_msr_writes);run_in_new_process (&verify_guest_msr_reads); +run_in_new_process (&verify_guest_hlt);return 0 ; }
RFC PATCH v5 17/29 KVM: selftests: TDX: Add TDX MMIO reads test
In reply to Sagi ShaharThe test verifies MMIO reads of various sizes from the host to the guest.
--- .../selftests/kvm/include/x86_64/tdx/tdcall.h | 2 + .../selftests/kvm/include/x86_64/tdx/tdx.h | 3 + .../kvm/include/x86_64/tdx/test_util.h | 23 +++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 19 ++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 87 +++++++++++++++++++ 5 files changed, 134 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h +2 -0
@@ -9,6 +9,8 @@#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO_READ 0 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE 1#define TDG_VP_VMCALL_SUCCESS 0x0000000000000000#define TDG_VP_VMCALL_INVALID_OPERAND 0x8000000000000000
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +3 -0
@@ -12,6 +12,7 @@#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO 48void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu); uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,
@@ -22,5 +23,7 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12,uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag); +uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size, +uint64_t *data_out);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +23 -0
@@ -35,6 +35,29 @@ (VCPU)->run->io.direction); \ }while (0 ) + +/** +* Assert that some MMIO operation involving TDG.VP.VMCALL <#VERequestMMIO> was +* called in the guest. + */ +#define TDX_TEST_ASSERT_MMIO (VCPU ,ADDR ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_MMIO, \ + "Got exit_reason other than KVM_EXIT_MMIO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_MMIO) && \ + ((VCPU)->run->mmio.phys_addr == (ADDR)) && \ + ((VCPU)->run->mmio.len == (SIZE)) && \ + ((VCPU)->run->mmio.is_write == (DIR)), \ + "Got an unexpected MMIO exit values: %u (%s) %llu %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->mmio.phys_addr, (VCPU)->run->mmio.len, \ + (VCPU)->run->mmio.is_write); \ + } while (0) +/** * Check and report if there was some failure in the guest, either an exception * like a triple fault, or if a tdx_test_fatal() was hit.
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +19 -0
@@ -124,3 +124,22 @@ uint64_t tdg_vp_vmcall_instruction_hlt(uint64_t interrupt_blocked_flag)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size, +uint64_t *data_out) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_READ , + .r14 = address, + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (data_out) + *data_out = args.r11; + +return ret; +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +87 -0
99 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 17/29] KVM: selftests: TDX: Add TDX MMIO reads test
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_hlt(void) · line 803
Quoted 2 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +2
-0+/* Pick any address that was not mapped into the guest to test MMIO */ +#define TDX_MMIO_TEST_ADDR 0x200000000
Also need to test below MMIO addresses
(1) GPA with shared bit on.
(2) GPA in memslot
Re: [RFC PATCH v5 17/29] KVM: selftests: TDX: Add TDX MMIO reads test
In reply to Sagi ShaharQuoted 147 lines · Sagi Shahar
The test verifies MMIO reads of various sizes from the host to the guest.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdcall.h | 2 + .../selftests/kvm/include/x86_64/tdx/tdx.h | 3 + .../kvm/include/x86_64/tdx/test_util.h | 23 +++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 19 ++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 87 +++++++++++++++++++ 5 files changed, 134 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h +2
-0@@ -9,6 +9,8 @@#define TDG_VP_VMCALL_INSTRUCTION_IO_READ 0#define TDG_VP_VMCALL_INSTRUCTION_IO_WRITE 1 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO_READ 0 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE 1#define TDG_VP_VMCALL_SUCCESS 0x0000000000000000#define TDG_VP_VMCALL_INVALID_OPERAND 0x8000000000000000tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +3
-0@@ -12,6 +12,7 @@#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31#define TDG_VP_VMCALL_INSTRUCTION_WRMSR 32 +#define TDG_VP_VMCALL_VE_REQUEST_MMIO 48void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu); uint64_t tdg_vp_vmcall_instruction_io(uint64_t port, uint64_t size,@@ -22,5 +23,7 @@ uint64_t tdg_vp_vmcall_get_td_vmcall_info(uint64_t *r11, uint64_t *r12,uint64_t tdg_vp_vmcall_instruction_rdmsr (uint64_t index,uint64_t *ret_value);uint64_t tdg_vp_vmcall_instruction_wrmsr (uint64_t index,uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag); +uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size, +uint64_t *data_out);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/test_util.h +23
-0@@ -35,6 +35,29 @@ (VCPU)->run->io.direction); \ }while (0 ) + +/** +* Assert that some MMIO operation involving TDG.VP.VMCALL <#VERequestMMIO> was +* called in the guest. + */ +#define TDX_TEST_ASSERT_MMIO (VCPU ,ADDR ,SIZE ,DIR ) \ + do { \ + TEST_ASSERT((VCPU)->run->exit_reason == KVM_EXIT_MMIO, \ + "Got exit_reason other than KVM_EXIT_MMIO: %u (%s)\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason)); \ + \ + TEST_ASSERT(((VCPU)->run->exit_reason == KVM_EXIT_MMIO) && \ + ((VCPU)->run->mmio.phys_addr == (ADDR)) && \ + ((VCPU)->run->mmio.len == (SIZE)) && \ + ((VCPU)->run->mmio.is_write == (DIR)), \ + "Got an unexpected MMIO exit values: %u (%s) %llu %d %d\n", \ + (VCPU)->run->exit_reason, \ + exit_reason_str((VCPU)->run->exit_reason), \ + (VCPU)->run->mmio.phys_addr, (VCPU)->run->mmio.len, \ + (VCPU)->run->mmio.is_write); \ + } while (0) +/** * Check and report if there was some failure in the guest, either an exception * like a triple fault, or if a tdx_test_fatal() was hit. tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +19
-0@@ -124,3 +124,22 @@ uint64_t tdg_vp_vmcall_instruction_hlt(uint64_t interrupt_blocked_flag)return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size, +uint64_t *data_out) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_READ , + .r14 = address, + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (data_out) + *data_out = args.r11; + +return ret; +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +32
-0@@ -799,6 +799,92 @@ void verify_guest_hlt(void)_verify_guest_hlt (0 ); } +/* Pick any address that was not mapped into the guest to test MMIO */ +#define TDX_MMIO_TEST_ADDR 0x200000000 + +void guest_mmio_reads (void ) +{ +uint64_t data; +uint64_t ret; + + ret =tdg_vp_vmcall_ve_request_mmio_read (TDX_MMIO_TEST_ADDR ,1 , &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0x12 ) +tdx_test_fatal (1 ); + + ret =tdg_vp_vmcall_ve_request_mmio_read (TDX_MMIO_TEST_ADDR ,2 , &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0x1234 ) +tdx_test_fatal (2 ); + + ret =tdg_vp_vmcall_ve_request_mmio_read (TDX_MMIO_TEST_ADDR ,4 , &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0x12345678 ) +tdx_test_fatal (4 ); + + ret =tdg_vp_vmcall_ve_request_mmio_read (TDX_MMIO_TEST_ADDR ,8 , &data); +if (ret) +tdx_test_fatal (ret); +if (data !=0x1234567890ABCDEF ) +tdx_test_fatal (8 ); +
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_guest_hlt(void) · line 843
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+// Read an invalid number of bytes. + ret =tdg_vp_vmcall_ve_request_mmio_read (TDX_MMIO_TEST_ADDR ,10 , &data); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +/* +* Varifies guest MMIO reads.
Nit: typo? Varifies ==> Verifies
Quoted 55 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +45
-0+*/ +void verify_mmio_reads (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_mmio_reads); +td_finalize (vm); + +printf ("Verifying TD MMIO reads:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,1 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_READ ); + *(uint8_t *)vcpu->run->mmio.data =0x12 ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,2 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_READ ); + *(uint16_t *)vcpu->run->mmio.data =0x1234 ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,4 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_READ ); + *(uint32_t *)vcpu->run->mmio.data =0x12345678 ; + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,8 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_READ ); + *(uint64_t *)vcpu->run->mmio.data =0x1234567890ABCDEF ; + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -818,6 +904,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_msr_writes);run_in_new_process (&verify_guest_msr_reads);run_in_new_process (&verify_guest_hlt); +run_in_new_process (&verify_mmio_reads);return 0 ; }
RFC PATCH v5 18/29 KVM: selftests: TDX: Add TDX MMIO writes test
In reply to Sagi ShaharThe test verifies MMIO writes of various sizes from the guest to the host.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 14 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 3 files changed, 101 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2 -0
@@ -25,5 +25,7 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size,uint64_t *data_out); +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +14 -0
@@ -143,3 +143,17 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size,return ret; } + +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE , + .r14 = address, + .r15 = data_in, + }; + +return __tdx_hypercall (&args,0 ); +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +85 -0
97 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 18/29] KVM: selftests: TDX: Add TDX MMIO writes test
Quoted 5 lines · Sagi Shahar
The test verifies MMIO writes of various sizes from the guest to the host.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>
Patch 17 and 18 test the part that guest has received the #VE caused by MMIO access, so calls the td vmcall to kvm to do the emulation.
Should the generation of #VE due to MMIO access be covered as well?
Quoted 143 lines
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 14 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 3 files changed, 101 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -25,5 +25,7 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size,uint64_t *data_out); +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +14
-0@@ -143,3 +143,17 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size,return ret; } + +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE , + .r14 = address, + .r15 = data_in, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +85
-0@@ -885,6 +885,90 @@ void verify_mmio_reads(void)printf ("\t ... PASSED\n" ); } +void guest_mmio_writes (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,1 ,0x12 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,2 ,0x1234 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,4 ,0x12345678 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,8 ,0x1234567890ABCDEF ); +if (ret) +tdx_test_fatal (ret); + +// Write across page boundary. + ret =tdg_vp_vmcall_ve_request_mmio_write (PAGE_SIZE -1 ,8 ,0 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +/* +* Varifies guest MMIO writes. +*/ +void verify_mmio_writes (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint8_t byte_1; +uint16_t byte_2; +uint32_t byte_4; +uint64_t byte_8; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_mmio_writes); +td_finalize (vm); + +printf ("Verifying TD MMIO writes:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,1 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_1 = *(uint8_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,2 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_2 = *(uint16_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,4 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_4 = *(uint32_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,8 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_8 = *(uint64_t *)(vcpu->run->mmio.data); + +TEST_ASSERT_EQ (byte_1,0x12 ); +TEST_ASSERT_EQ (byte_2,0x1234 ); +TEST_ASSERT_EQ (byte_4,0x12345678 ); +TEST_ASSERT_EQ (byte_8,0x1234567890ABCDEF ); + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -905,6 +989,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_msr_reads);run_in_new_process (&verify_guest_hlt);run_in_new_process (&verify_mmio_reads); +run_in_new_process (&verify_mmio_writes);return 0 ; }
Re: [RFC PATCH v5 18/29] KVM: selftests: TDX: Add TDX MMIO writes test
In reply to Sagi ShaharQuoted 119 lines · Sagi Shahar
The test verifies MMIO writes of various sizes from the guest to the host.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 14 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 3 files changed, 101 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -25,5 +25,7 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size,uint64_t *data_out); +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +14
-0@@ -143,3 +143,17 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size,return ret; } + +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE , + .r14 = address, + .r15 = data_in, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +66
-0@@ -885,6 +885,90 @@ void verify_mmio_reads(void)printf ("\t ... PASSED\n" ); } +void guest_mmio_writes (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,1 ,0x12 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,2 ,0x1234 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,4 ,0x12345678 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,8 ,0x1234567890ABCDEF ); +if (ret) +tdx_test_fatal (ret); + +// Write across page boundary. + ret =tdg_vp_vmcall_ve_request_mmio_write (PAGE_SIZE -1 ,8 ,0 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +/* +* Varifies guest MMIO writes. +*/ +void verify_mmio_writes (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint8_t byte_1; +uint16_t byte_2; +uint32_t byte_4; +uint64_t byte_8; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_mmio_writes); +td_finalize (vm); + +printf ("Verifying TD MMIO writes:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,1 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_1 = *(uint8_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,2 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_2 = *(uint16_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,4 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_4 = *(uint32_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,8 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE );
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_mmio_reads(void) · line 963
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ byte_8 = *(uint64_t *)(vcpu->run->mmio.data); + +TEST_ASSERT_EQ (byte_1,0x12 ); +TEST_ASSERT_EQ (byte_2,0x1234 ); +TEST_ASSERT_EQ (byte_4,0x12345678 ); +TEST_ASSERT_EQ (byte_8,0x1234567890ABCDEF ); + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND );
Is it possible that this event is caused by an failure of the last 8 byte write? i.e. though MMIO exit to host with correct value 0x1234567890ABCDEF, but guest sees ret as TDG_VP_VMCALL_INVALID_OPERAND.
And if, coincidently, guest gets a ret=0 in the next across page boundary write, the selftest will show "PASSED", which is not right.
Quoted 22 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +8
-0+td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -905,6 +989,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_msr_reads);run_in_new_process (&verify_guest_hlt);run_in_new_process (&verify_mmio_reads); +run_in_new_process (&verify_mmio_writes);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 18/29] KVM: selftests: TDX: Add TDX MMIO writes test
Quoted 135 lines · Yan Zhao
Quoted 119 lines · Sagi Shahar
The test verifies MMIO writes of various sizes from the guest to the host.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 14 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 3 files changed, 101 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -25,5 +25,7 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size,uint64_t *data_out); +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +14
-0@@ -143,3 +143,17 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size,return ret; } + +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE , + .r14 = address, + .r15 = data_in, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +66
-0@@ -885,6 +885,90 @@ void verify_mmio_reads(void)printf ("\t ... PASSED\n" ); } +void guest_mmio_writes (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,1 ,0x12 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,2 ,0x1234 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,4 ,0x12345678 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,8 ,0x1234567890ABCDEF ); +if (ret) +tdx_test_fatal (ret); + +// Write across page boundary. + ret =tdg_vp_vmcall_ve_request_mmio_write (PAGE_SIZE -1 ,8 ,0 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +/* +* Varifies guest MMIO writes. +*/ +void verify_mmio_writes (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint8_t byte_1; +uint16_t byte_2; +uint32_t byte_4; +uint64_t byte_8; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_mmio_writes); +td_finalize (vm); + +printf ("Verifying TD MMIO writes:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,1 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_1 = *(uint8_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,2 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_2 = *(uint16_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,4 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_4 = *(uint32_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,8 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE );tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_mmio_reads(void) · line 963
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ byte_8 = *(uint64_t *)(vcpu->run->mmio.data); + +TEST_ASSERT_EQ (byte_1,0x12 ); +TEST_ASSERT_EQ (byte_2,0x1234 ); +TEST_ASSERT_EQ (byte_4,0x12345678 ); +TEST_ASSERT_EQ (byte_8,0x1234567890ABCDEF ); + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND );Is it possible that this event is caused by an failure of the last 8 byte write? i.e. though MMIO exit to host with correct value
0x1234567890ABCDEF, but guest sees ret asTDG_VP_VMCALL_INVALID_OPERAND.
Quoted 3 lines
And if, coincidently, guest gets a ret=0 in the next across page boundary write, the selftest will show "PASSED", which is not right.
We can add another tdx_test_report_to_user_space to synchronize between guest and host execution making sure that the guest is done with all the valid writes before testing the negative case.
Quoted 23 lines
Quoted 23 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +8
-1+td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -905,6 +989,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_msr_reads);run_in_new_process (&verify_guest_hlt);run_in_new_process (&verify_mmio_reads); +run_in_new_process (&verify_mmio_writes);return 0 ; } --2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 18/29] KVM: selftests: TDX: Add TDX MMIO writes test
In reply to Sagi ShaharQuoted 74 lines · Sagi Shahar
The test verifies MMIO writes of various sizes from the guest to the host.
Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 14 +++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 3 files changed, 101 insertions(+)tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0@@ -25,5 +25,7 @@ uint64_t tdg_vp_vmcall_instruction_wrmsr(uint64_t index, uint64_t value);uint64_t tdg_vp_vmcall_instruction_hlt (uint64_t interrupt_blocked_flag);uint64_t tdg_vp_vmcall_ve_request_mmio_read (uint64_t address,uint64_t size,uint64_t *data_out); +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +14
-0@@ -143,3 +143,17 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size,return ret; } + +uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size, +uint64_t data_in) +{ +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_VE_REQUEST_MMIO , + .r12 = size, + .r13 =TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE , + .r14 = address, + .r15 = data_in, + }; + +return __tdx_hypercall (&args,0 ); +}tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +21
-0@@ -885,6 +885,90 @@ void verify_mmio_reads(void)printf ("\t ... PASSED\n" ); } +void guest_mmio_writes (void ) +{ +uint64_t ret; + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,1 ,0x12 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,2 ,0x1234 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,4 ,0x12345678 ); +if (ret) +tdx_test_fatal (ret); + + ret =tdg_vp_vmcall_ve_request_mmio_write (TDX_MMIO_TEST_ADDR ,8 ,0x1234567890ABCDEF ); +if (ret) +tdx_test_fatal (ret); + +// Write across page boundary.
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_mmio_reads(void) · line 918
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ ret =tdg_vp_vmcall_ve_request_mmio_write (PAGE_SIZE -1 ,8 ,0 ); +if (ret) +tdx_test_fatal (ret); + +tdx_test_success (); +} + +/* +* Varifies guest MMIO writes. +*/
Nit: typo? Varifies ==> Verifies
Quoted 64 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +54
-0+void verify_mmio_writes (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +uint8_t byte_1; +uint16_t byte_2; +uint32_t byte_4; +uint64_t byte_8; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_mmio_writes); +td_finalize (vm); + +printf ("Verifying TD MMIO writes:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,1 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_1 = *(uint8_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,2 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_2 = *(uint16_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,4 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_4 = *(uint32_t *)(vcpu->run->mmio.data); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_MMIO (vcpu,TDX_MMIO_TEST_ADDR ,8 ,TDG_VP_VMCALL_VE_REQUEST_MMIO_WRITE ); + byte_8 = *(uint64_t *)(vcpu->run->mmio.data); + +TEST_ASSERT_EQ (byte_1,0x12 ); +TEST_ASSERT_EQ (byte_2,0x1234 ); +TEST_ASSERT_EQ (byte_4,0x12345678 ); +TEST_ASSERT_EQ (byte_8,0x1234567890ABCDEF ); + +td_vcpu_run (vcpu); +TEST_ASSERT_EQ (vcpu->run->exit_reason,KVM_EXIT_SYSTEM_EVENT ); +TEST_ASSERT_EQ (vcpu->run->system_event.data[1 ],TDG_VP_VMCALL_INVALID_OPERAND ); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -905,6 +989,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_guest_msr_reads);run_in_new_process (&verify_guest_hlt);run_in_new_process (&verify_mmio_reads); +run_in_new_process (&verify_mmio_writes);return 0 ; }
RFC PATCH v5 19/29 KVM: selftests: TDX: Add TDX CPUID TDVMCALL test
In reply to Sagi ShaharThis test issues a CPUID TDVMCALL from inside the guest to get the CPUID values as seen by KVM.
--- .../selftests/kvm/include/x86_64/tdx/tdx.h | 4 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 26 +++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 94 +++++++++++++++++++ 3 files changed, 124 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +4 -0
@@ -8,6 +8,7 @@#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003 +#define TDG_VP_VMCALL_INSTRUCTION_CPUID 10#define TDG_VP_VMCALL_INSTRUCTION_HLT 12#define TDG_VP_VMCALL_INSTRUCTION_IO 30#define TDG_VP_VMCALL_INSTRUCTION_RDMSR 31
@@ -27,5 +28,8 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_read(uint64_t address, uint64_t size, uint64_t *data_out);uint64_t tdg_vp_vmcall_ve_request_mmio_write (uint64_t address,uint64_t size,uint64_t data_in); +uint64_t tdg_vp_vmcall_instruction_cpuid (uint32_t eax,uint32_t ecx, +uint32_t *ret_eax,uint32_t *ret_ebx, +uint32_t *ret_ecx,uint32_t *ret_edx);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +26 -0
@@ -157,3 +157,29 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_write(uint64_t address, uint64_t size,return __tdx_hypercall (&args,0 ); } + +uint64_t tdg_vp_vmcall_instruction_cpuid (uint32_t eax,uint32_t ecx, +uint32_t *ret_eax,uint32_t *ret_ebx, +uint32_t *ret_ecx,uint32_t *ret_edx) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_INSTRUCTION_CPUID , + .r12 = eax, + .r13 = ecx, + }; + + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (ret_eax) + *ret_eax = args.r12; +if (ret_ebx) + *ret_ebx = args.r13; +if (ret_ecx) + *ret_ecx = args.r14; +if (ret_edx) + *ret_edx = args.r15; + +return ret; +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +94 -0
106 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 20/29 KVM: selftests: TDX: Verify the behavior when host consumes a TD private memory
In reply to Sagi ShaharFrom: Ryan Afranji <[email protected]>
The test checks that host can only read fixed values when trying to access the guest's private memory.
--- .../selftests/kvm/x86_64/tdx_vm_tests.c | 85 +++++++++++++++++++ 1 file changed, 85 insertions(+)
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +85 -0
@@ -1062,6 +1062,90 @@ void verify_td_cpuid_tdcall(void)printf ("\t ... PASSED\n" ); } +/* +* Shared variables between guest and host for host reading private mem test +*/ +static uint64_t tdx_test_host_read_private_mem_addr; +#define TDX_HOST_READ_PRIVATE_MEM_PORT_TEST 0x53 + +void guest_host_read_priv_mem (void ) +{ +uint64_t ret; +uint64_t placeholder =0 ; + +/* Set value */ + *((uint32_t *) tdx_test_host_read_private_mem_addr) =0xABCD ; + +/* Exit so host can read value */ + ret =tdg_vp_vmcall_instruction_io ( +TDX_HOST_READ_PRIVATE_MEM_PORT_TEST ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , &placeholder); +if (ret) +tdx_test_fatal (ret); + +/* Update guest_var's value and have host reread it. */ + *((uint32_t *) tdx_test_host_read_private_mem_addr) =0xFEDC ; + +tdx_test_success (); +} + +void verify_host_reading_private_mem (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +vm_vaddr_t test_page; +uint64_t *host_virt; +uint64_t first_host_read; +uint64_t second_host_read; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_host_read_priv_mem); + + test_page =vm_vaddr_alloc_page (vm); +TEST_ASSERT (test_page <BIT_ULL (32 ), +"Test address should fit in 32 bits so it can be sent to the guest" ); + + host_virt =addr_gva2hva (vm, test_page); +TEST_ASSERT (host_virt !=NULL , +"Guest address not found in guest memory regions\n" ); + + tdx_test_host_read_private_mem_addr = test_page; +sync_global_to_guest (vm, tdx_test_host_read_private_mem_addr); + +td_finalize (vm); + +printf ("Verifying host's behavior when reading TD private memory:\n" ); + +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_HOST_READ_PRIVATE_MEM_PORT_TEST , +4 ,TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +printf ("\t ... Guest's variable contains 0xABCD\n" ); + +/* Host reads guest's variable. */ + first_host_read = *host_virt; +printf ("\t ... Host's read attempt value: %lu\n" , first_host_read); + +/* Guest updates variable and host rereads it. */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +printf ("\t ... Guest's variable updated to 0xFEDC\n" ); + + second_host_read = *host_virt; +printf ("\t ... Host's second read attempt value: %lu\n" , + second_host_read); + +TEST_ASSERT (first_host_read == second_host_read, +"Host did not read a fixed pattern\n" ); + +printf ("\t ... Fixed pattern was returned to the host\n" ); + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );
@@ -1084,6 +1168,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_mmio_reads);run_in_new_process (&verify_mmio_writes);run_in_new_process (&verify_td_cpuid_tdcall); +run_in_new_process (&verify_host_reading_private_mem);return 0 ; }
Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 21/29 KVM: selftests: TDX: Add TDG.VP.INFO test
In reply to Sagi ShaharFrom: Roger Wang <[email protected]>
Adds a test for TDG.VP.INFO
--- .../selftests/kvm/include/x86_64/tdx/tdcall.h | 19 +++ .../selftests/kvm/include/x86_64/tdx/tdx.h | 5 + .../selftests/kvm/lib/x86_64/tdx/tdcall.S | 68 ++++++++ .../selftests/kvm/lib/x86_64/tdx/tdx.c | 27 ++++ .../selftests/kvm/x86_64/tdx_vm_tests.c | 145 ++++++++++++++++++ 5 files changed, 264 insertions(+)
tools/testing/selftests/kvm/include/x86_64/tdx/tdcall.h +19 -0
@@ -37,4 +37,23 @@ struct tdx_hypercall_args {/* Used to request services from the VMM */ u64 __tdx_hypercall (struct tdx_hypercall_args *args,unsigned long flags); +/* +* Used to gather the output registers values of the TDCALL and SEAMCALL +* instructions when requesting services from the TDX module. +* +* This is a software only structure and not part of the TDX module/VMM ABI. +*/ +struct tdx_module_output { +u64 rcx; +u64 rdx; +u64 r8; +u64 r9; +u64 r10; +u64 r11; +}; + +/* Used to communicate with the TDX module */ +u64 __tdx_module_call (u64 fn,u64 rcx,u64 rdx,u64 r8,u64 r9, +struct tdx_module_output *out); +#endif // SELFTESTS_TDX_TDCALL_H
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +5 -0
@@ -5,6 +5,8 @@#include <stdint.h> #include "kvm_util_base.h" +#define TDG_VP_INFO 1 +#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003
@@ -31,5 +33,8 @@ uint64_t tdg_vp_vmcall_ve_request_mmio_write(uint64_t address, uint64_t size,uint64_t tdg_vp_vmcall_instruction_cpuid (uint32_t eax,uint32_t ecx,uint32_t *ret_eax,uint32_t *ret_ebx,uint32_t *ret_ecx,uint32_t *ret_edx); +uint64_t tdg_vp_info (uint64_t *rcx,uint64_t *rdx, +uint64_t *r8,uint64_t *r9, +uint64_t *r10,uint64_t *r11);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdcall.S +68 -0
73 lines not on this page · raw message
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +27 -0
@@ -183,3 +183,30 @@ uint64_t tdg_vp_vmcall_instruction_cpuid(uint32_t eax, uint32_t ecx,return ret; } + +uint64_t tdg_vp_info (uint64_t *rcx,uint64_t *rdx, +uint64_t *r8,uint64_t *r9, +uint64_t *r10,uint64_t *r11) +{ +uint64_t ret; +struct tdx_module_output out; + +memset (&out,0 ,sizeof (struct tdx_module_output )); + + ret =__tdx_module_call (TDG_VP_INFO ,0 ,0 ,0 ,0 , &out); + +if (rcx) + *rcx = out.rcx; +if (rdx) + *rdx = out.rdx; +if (r8) + *r8 = out.r8; +if (r9) + *r9 = out.r9; +if (r10) + *r10 = out.r10; +if (r11) + *r11 = out.r11; + +return ret; +}
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +145 -0
157 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 21/29] KVM: selftests: TDX: Add TDG.VP.INFO test
Quoted 71 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +71
-0+/* +* TDG.VP.INFO call from the guest. Verify the right values are returned +*/ +void verify_tdcall_vp_info (void ) +{ +const int num_vcpus =2 ; +struct kvm_vcpu *vcpus[num_vcpus]; +struct kvm_vm *vm; + +uint64_t rcx, rdx, r8, r9, r10, r11; +uint32_t ret_num_vcpus, ret_max_vcpus; +uint64_t attributes; +uint32_t i; +const struct kvm_cpuid_entry2 *cpuid_entry; +int max_pa =-1 ; + + vm =td_create (); + +#define TDX_TDPARAM_ATTR_SEPT_VE_DISABLE_BIT (1UL << 28) +#define TDX_TDPARAM_ATTR_PKS_BIT (1UL << 30) +/* Setting attributes parameter used by TDH.MNG.INIT to 0x50000000 */ + attributes =TDX_TDPARAM_ATTR_SEPT_VE_DISABLE_BIT | +TDX_TDPARAM_ATTR_PKS_BIT ; + +td_initialize (vm,VM_MEM_SRC_ANONYMOUS , attributes); + +for (i =0 ; i < num_vcpus; i++) + vcpus[i] =td_vcpu_add (vm, i, guest_tdcall_vp_info); + +td_finalize (vm); + +printf ("Verifying TDG.VP.INFO call:\n" ); + +/* Get KVM CPUIDs for reference */ + cpuid_entry =get_cpuid_entry (kvm_get_supported_cpuid (),0x80000008 ,0 ); +TEST_ASSERT (cpuid_entry,"CPUID entry missing\n" ); + max_pa = cpuid_entry->eax &0xff ; + +for (i =0 ; i < num_vcpus; i++) { +struct kvm_vcpu *vcpu = vcpus[i]; + +/* Wait for guest to report rcx value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + rcx =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report rdx value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + rdx =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r8 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r8 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r9 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r9 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r10 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r10 =tdx_test_read_64bit_report_from_guest (vcpu); + +/* Wait for guest to report r11 value */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + r11 =tdx_test_read_64bit_report_from_guest (vcpu); +
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c void verify_host_reading_private_mem(void) · line 1269
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +10
-0+ ret_num_vcpus = r8 &0xFFFFFFFF ; + ret_max_vcpus = (r8 >>32 ) &0xFFFFFFFF ; + +/* first bits 5:0 of rcx represent the GPAW */ +TEST_ASSERT_EQ (rcx &0x3F , max_pa); +/* next 63:6 bits of rcx is reserved and must be 0 */ +TEST_ASSERT_EQ (rcx >>6 ,0 ); +TEST_ASSERT_EQ (rdx, attributes); +TEST_ASSERT_EQ (ret_num_vcpus, num_vcpus); +TEST_ASSERT_EQ (ret_max_vcpus,512 );
Better to assert of kvm_check_cap(KVM_CAP_MAX_VCPUS) here .
Quoted 38 lines
tools/testing/selftests/kvm/x86_64/tdx_vm_tests.c +24
-0+/* VCPU_INDEX = i */ +TEST_ASSERT_EQ (r9, i); +/* +* verify reserved bits are 0 +* r10 bit 0 (SYS_RD) indicates that the TDG.SYS.RD/RDM/RDALL +* functions are available and can be either 0 or 1. +*/ +TEST_ASSERT_EQ (r10 & ~1 ,0 ); +TEST_ASSERT_EQ (r11,0 ); + +/* Wait for guest to complete execution */ +td_vcpu_run (vcpu); + +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); +TDX_TEST_ASSERT_SUCCESS (vcpu); + +printf ("\t ... Guest completed run on VCPU=%u\n" , i); + } + +kvm_vm_free (vm); +printf ("\t ... PASSED\n" ); +} +int main (int argc,char **argv) {setbuf (stdout,NULL );@@ -1169,6 +1313,7 @@ int main(int argc, char **argv)run_in_new_process (&verify_mmio_writes);run_in_new_process (&verify_td_cpuid_tdcall);run_in_new_process (&verify_host_reading_private_mem); +run_in_new_process (&verify_tdcall_vp_info);return 0 ; }Signature · 1 line
2.43.0.472.g3155946c3a-goog
RFC PATCH v5 22/29 KVM: selftests: Add functions to allow mapping as shared
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
--- .../selftests/kvm/include/kvm_util_base.h | 24 ++++++++++++++ tools/testing/selftests/kvm/lib/kvm_util.c | 32 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/processor.c | 15 +++++++-- 3 files changed, 69 insertions(+), 2 deletions(-)
tools/testing/selftests/kvm/include/kvm_util_base.h +24 -0
@@ -574,6 +574,8 @@ vm_vaddr_t vm_vaddr_alloc_page(struct kvm_vm *vm);void virt_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,unsigned int npages); +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages);void *addr_gpa2hva (struct kvm_vm *vm,vm_paddr_t gpa);void *addr_gva2hva (struct kvm_vm *vm,vm_vaddr_t gva);vm_paddr_t addr_hva2gpa (struct kvm_vm *vm,void *hva);
@@ -1034,6 +1036,28 @@ static inline void virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddrvirt_arch_pg_map (vm, vaddr, paddr); } +/* +* VM Virtual Page Map as Shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - VM Virtual Address +* paddr - VM Physical Address +* memslot - Memory region slot for new virtual translation tables +* +* Output Args: None +* +* Return: None +* +* Within @vm, creates a virtual translation for the page starting +* at @vaddr to the page starting at @paddr. +*/ +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr); + +static inline void virt_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) +{ +virt_arch_pg_map_shared (vm, vaddr, paddr); +}/* * Address Guest Virtual to Guest Physical
tools/testing/selftests/kvm/lib/kvm_util.c +32 -0
@@ -1573,6 +1573,38 @@ void virt_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, } } +/* +* Map a range of VM virtual address to the VM's physical address as shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - Virtuall address to map +* paddr - VM Physical Address +* npages - The number of pages to map +* +* Output Args: None +* +* Return: None +* +* Within the VM given by @vm, creates a virtual translation for +* @npages starting at @vaddr to the page range starting at @paddr. +*/ +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages) +{ +size_t page_size = vm->page_size; +size_t size = npages * page_size; + +TEST_ASSERT (vaddr + size > vaddr,"Vaddr overflow" ); +TEST_ASSERT (paddr + size > paddr,"Paddr overflow" ); + +while (npages--) { +virt_pg_map_shared (vm, vaddr, paddr); + vaddr += page_size; + paddr += page_size; + } +} +/* * Address VM Physical to Host Virtual *
tools/testing/selftests/kvm/lib/x86_64/processor.c +13 -2
@@ -190,7 +190,8 @@ static uint64_t *virt_create_upper_pte(struct kvm_vm *vm,return pte; } -void __virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,int level) +static void ___virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +int level,bool protected) {const uint64_t pg_size =PG_LEVEL_SIZE (level);uint64_t *pml4e, *pdpe, *pde;
@@ -235,17 +236,27 @@ void __virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, int level) "PTE already present for 4k page at vaddr: 0x%lx\n", vaddr); *pte =PTE_PRESENT_MASK |PTE_WRITABLE_MASK | (paddr &PHYSICAL_PAGE_MASK ); -if (vm_is_gpa_protected (vm, paddr)) +if (protected) *pte |= vm->arch.c_bit;else *pte |= vm->arch.s_bit; } +void __virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,int level) +{ +___virt_pg_map (vm, vaddr, paddr, level,vm_is_gpa_protected (vm, paddr)); +} +void virt_arch_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) {__virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K ); } +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) +{ +___virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K , false); +} +void virt_map_level (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,uint64_t nr_bytes,int level) {
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 22/29] KVM: selftests: Add functions to allow mapping as shared
Quoted 82 lines · Sagi Shahar
From: Ackerley Tng <[email protected]>
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 24 ++++++++++++++ tools/testing/selftests/kvm/lib/kvm_util.c | 32 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/processor.c | 15 +++++++-- 3 files changed, 69 insertions(+), 2 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +24
-0@@ -574,6 +574,8 @@ vm_vaddr_t vm_vaddr_alloc_page(struct kvm_vm *vm);void virt_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,unsigned int npages); +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages);void *addr_gpa2hva (struct kvm_vm *vm,vm_paddr_t gpa);void *addr_gva2hva (struct kvm_vm *vm,vm_vaddr_t gva);vm_paddr_t addr_hva2gpa (struct kvm_vm *vm,void *hva);@@ -1034,6 +1036,28 @@ static inline void virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddrvirt_arch_pg_map (vm, vaddr, paddr); } +/* +* VM Virtual Page Map as Shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - VM Virtual Address +* paddr - VM Physical Address +* memslot - Memory region slot for new virtual translation tables +* +* Output Args: None +* +* Return: None +* +* Within @vm, creates a virtual translation for the page starting +* at @vaddr to the page starting at @paddr. +*/ +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr); + +static inline void virt_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) +{ +virt_arch_pg_map_shared (vm, vaddr, paddr); +}/* * Address Guest Virtual to Guest Physical tools/testing/selftests/kvm/lib/kvm_util.c +21
-0@@ -1573,6 +1573,38 @@ void virt_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, } } +/* +* Map a range of VM virtual address to the VM's physical address as shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - Virtuall address to map +* paddr - VM Physical Address +* npages - The number of pages to map +* +* Output Args: None +* +* Return: None +* +* Within the VM given by @vm, creates a virtual translation for +* @npages starting at @vaddr to the page range starting at @paddr. +*/ +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages) +{ +size_t page_size = vm->page_size; +size_t size = npages * page_size;
tools/testing/selftests/kvm/lib/kvm_util.c void virt_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, · line 1606
Quoted 10 lines
tools/testing/selftests/kvm/lib/kvm_util.c +10
-0+ +TEST_ASSERT (vaddr + size > vaddr,"Vaddr overflow" ); +TEST_ASSERT (paddr + size > paddr,"Paddr overflow" ); + +while (npages--) { +virt_pg_map_shared (vm, vaddr, paddr); + vaddr += page_size; + paddr += page_size; + } +}
Set vm->vpages_mapped as what's done in virt_map() ?
Quoted 51 lines
tools/testing/selftests/kvm/lib/kvm_util.c +1
-0+/* * Address VM Physical to Host Virtual * tools/testing/selftests/kvm/lib/x86_64/processor.c +13
-2@@ -190,7 +190,8 @@ static uint64_t *virt_create_upper_pte(struct kvm_vm *vm,return pte; } -void __virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,int level) +static void ___virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +int level,bool protected) {const uint64_t pg_size =PG_LEVEL_SIZE (level);uint64_t *pml4e, *pdpe, *pde;@@ -235,17 +236,27 @@ void __virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, int level) "PTE already present for 4k page at vaddr: 0x%lx\n", vaddr); *pte =PTE_PRESENT_MASK |PTE_WRITABLE_MASK | (paddr &PHYSICAL_PAGE_MASK ); -if (vm_is_gpa_protected (vm, paddr)) +if (protected) *pte |= vm->arch.c_bit;else *pte |= vm->arch.s_bit; } +void __virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,int level) +{ +___virt_pg_map (vm, vaddr, paddr, level,vm_is_gpa_protected (vm, paddr)); +} +void virt_arch_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) {__virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K ); } +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) +{ +___virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K , false); +} +void virt_map_level (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,uint64_t nr_bytes,int level) {Signature · 1 line
2.43.0.472.g3155946c3a-goog
A message that is not in the archive (sent off-list or not yet received): DS7PR11MB7886BD37E5E56DAB9A0087A3F6292@DS7PR11MB7886.namprd11.prod.outlook.com
Re: [RFC PATCH v5 22/29] KVM: selftests: Add functions to allow mapping as shared
Quoted 8 lines · Sagi Shahar
-----Original Message-----
From: Sagi Shahar <[email protected]>
Sent: Tuesday, December 12, 2023 12:47 PM
To: [email protected]; Ackerley Tng <[email protected]>; Afranji, Ryan <[email protected]>; Aktas, Erdem <[email protected]>; Sagi Shahar <[email protected]>; Yamahata, Isaku <[email protected]>
Cc: Sean Christopherson <[email protected]>; Paolo Bonzini <[email protected]>; Shuah Khan <[email protected]>; Peter Gonda <[email protected]>; Xu, Haibo1 <[email protected]>; Chao Peng <[email protected]>; Annapurve, Vishal <[email protected]>; Roger Wang <[email protected]>; Vipin Sharma <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: [RFC PATCH v5 22/29] KVM: selftests: Add functions to allow mapping as shared
Since protected_phy_pages is introduced to keep track of the guest memory's private/shared property, it's better to keep it consistent with the guest mappings.
Instead of having a set of new APIs to force it to map shared guest pages, how about to update protected_phy_pages sparsebits right before the mapping, and just call the existing virt_pg_map() to do the mapping?
Quoted 118 lines
From: Ackerley Tng <[email protected]>
Signed-off-by Ackerley Tng <[email protected]>Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>--- .../selftests/kvm/include/kvm_util_base.h | 24 ++++++++++++++ tools/testing/selftests/kvm/lib/kvm_util.c | 32 +++++++++++++++++++ .../selftests/kvm/lib/x86_64/processor.c | 15 +++++++-- 3 files changed, 69 insertions(+), 2 deletions(-)tools/testing/selftests/kvm/include/kvm_util_base.h +24
-0@@ -574,6 +574,8 @@ vm_vaddr_t vm_vaddr_alloc_page(struct kvm_vm *vm);void virt_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,unsigned int npages); +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages); void *addr_gpa2hva(struct kvm_vm *vm, vm_paddr_t gpa); void *addr_gva2hva(struct kvm_vm *vm, vm_vaddr_t gva); vm_paddr_t addr_hva2gpa(struct kvm_vm *vm, void *hva); @@ -1034,6 +1036,28 @@ static inline void virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr virt_arch_pg_map(vm, vaddr, paddr); } +/* +* VM Virtual Page Map as Shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - VM Virtual Address +* paddr - VM Physical Address +* memslot - Memory region slot for new virtual translation tables +* +* Output Args: None +* +* Return: None +* +* Within @vm, creates a virtual translation for the page starting +* at @vaddr to the page starting at @paddr. +*/ +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr, +uint64_t paddr); + +static inline void virt_pg_map_shared (struct kvm_vm *vm,uint64_t +vaddr,uint64_t paddr) { +virt_arch_pg_map_shared (vm, vaddr, paddr); }/* * Address Guest Virtual to Guest Physical diff --git a/tools/testing/selftests/kvm/lib/kvm_util.c b/tools/testing/selftests/kvm/lib/kvm_util.c index
4f1ae0f1eef0..28780fa1f0f2100644tools/testing/selftests/kvm/lib/kvm_util.c +33
-0@@ -1573,6 +1573,38 @@ void virt_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, } } +/* +* Map a range of VM virtual address to the VM's physical address as +shared +* +* Input Args: +* vm - Virtual Machine +* vaddr - Virtuall address to map +* paddr - VM Physical Address +* npages - The number of pages to map +* +* Output Args: None +* +* Return: None +* +* Within the VM given by @vm, creates a virtual translation for +* @npages starting at @vaddr to the page range starting at @paddr. +*/ +void virt_map_shared (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +unsigned int npages) +{ +size_t page_size = vm->page_size; +size_t size = npages * page_size; + +TEST_ASSERT (vaddr + size > vaddr,"Vaddr overflow" ); +TEST_ASSERT (paddr + size > paddr,"Paddr overflow" ); + +while (npages--) { +virt_pg_map_shared (vm, vaddr, paddr); + vaddr += page_size; + paddr += page_size; + } +} +/* * Address VM Physical to Host Virtual * tools/testing/selftests/kvm/lib/x86_64/processor.c +4
-2@@ -190,7 +190,8 @@ static uint64_t *virt_create_upper_pte(struct kvm_vm *vm,return pte; } -void __virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,int level) +static void ___virt_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr, +int level,bool protected) {const uint64_t pg_size =PG_LEVEL_SIZE (level);uint64_t *pml4e, *pdpe, *pde;@@ -235,17 +236,27 @@ void __virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, int level) "PTE already present for 4k page at vaddr: 0x%lx\n", vaddr); *pte =PTE_PRESENT_MASK |PTE_WRITABLE_MASK | (paddr &PHYSICAL_PAGE_MASK ); -if (vm_is_gpa_protected (vm, paddr)) + if (protected)> *pte |= vm->arch.c_bit;else *pte |= vm->arch.s_bit; } +void __virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr,
tools/testing/selftests/kvm/lib/x86_64/processor.c void __virt_pg_map(struct kvm_vm *vm, uint64_t vaddr, uint64_t paddr, int level) · line 254
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +7
-0+int level) { +___virt_pg_map (vm, vaddr, paddr, level,vm_is_gpa_protected (vm, +paddr)); } +void virt_arch_pg_map (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr) {__virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K ); } +void virt_arch_pg_map_shared (struct kvm_vm *vm,uint64_t vaddr, +uint64_t paddr) { +___virt_pg_map (vm, vaddr, paddr,PG_LEVEL_4K , false); }
Here, it tries to create the guest mappings regardless of what the value of protected_phy_pages is, which could create confusion.
Quoted 7 lines
tools/testing/selftests/kvm/lib/x86_64/processor.c +1
-1+void virt_map_level (struct kvm_vm *vm,uint64_t vaddr,uint64_t paddr,uint64_t nr_bytes,int level) { --2.43.0.472.g3155946c3a-goog
RFC PATCH v5 23/29 KVM: selftests: TDX: Add shared memory test
In reply to Sagi ShaharFrom: Ryan Afranji <[email protected]>
Adds a test that sets up shared memory between the host and guest.
--- tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../kvm/include/x86_64/tdx/tdx_util.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 26 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 25 ++++ .../kvm/x86_64/tdx_shared_mem_test.c | 135 ++++++++++++++++++ 6 files changed, 191 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c
tools/testing/selftests/kvm/Makefile +1 -0
@@ -156,6 +156,7 @@ TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests +TEST_GEN_PROGS_x86_64 += x86_64/tdx_shared_mem_test # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_test
tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2 -0
@@ -8,6 +8,7 @@#define TDG_VP_INFO 1#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000 +#define TDG_VP_VMCALL_MAP_GPA 0x10001#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_CPUID 10
@@ -36,5 +37,6 @@ uint64_t tdg_vp_vmcall_instruction_cpuid(uint32_t eax, uint32_t ecx,uint64_t tdg_vp_info (uint64_t *rcx,uint64_t *rdx,uint64_t *r8,uint64_t *r9,uint64_t *r10,uint64_t *r11); +uint64_t tdg_vp_vmcall_map_gpa (uint64_t address,uint64_t size,uint64_t *data_out);#endif // SELFTEST_TDX_TDX_H
tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +2 -0
@@ -13,5 +13,7 @@ void td_initialize(struct kvm_vm *vm, enum vm_mem_backing_src_type src_type, uint64_t attributes);void td_finalize (struct kvm_vm *vm);void td_vcpu_run (struct kvm_vcpu *vcpu); +void handle_memory_conversion (struct kvm_vm *vm,uint64_t gpa,uint64_t size, +bool shared_to_private);#endif // SELFTESTS_TDX_KVM_UTIL_H
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +26 -0
@@ -4,9 +4,11 @@#include "tdx/tdcall.h" #include "tdx/tdx.h" +#include "tdx/tdx_util.h" void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) { +struct kvm_vm *vm = vcpu->vm;struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall;uint64_t vmcall_subfunction = vmcall_info->subfunction;
@@ -20,6 +22,14 @@ void handle_userspace_tdg_vp_vmcall_exit(struct kvm_vcpu *vcpu) vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; vmcall_info->status_code =0 ;break ; +case TDG_VP_VMCALL_MAP_GPA : +uint64_t gpa = vmcall_info->in_r12 & ~vm->arch.s_bit; +bool shared_to_private = !(vm->arch.s_bit & + vmcall_info->in_r12); +handle_memory_conversion (vm, gpa, vmcall_info->in_r13, + shared_to_private); + vmcall_info->status_code =0 ; +break ;default :TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , vmcall_subfunction);
@@ -210,3 +220,19 @@ uint64_t tdg_vp_info(uint64_t *rcx, uint64_t *rdx,return ret; } + +uint64_t tdg_vp_vmcall_map_gpa (uint64_t address,uint64_t size,uint64_t *data_out) +{ +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_MAP_GPA , + .r12 = address, + .r13 = size + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (data_out) + *data_out = args.r11; +return ret; +}
tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +25 -0
@@ -531,3 +531,28 @@ void td_vcpu_run(struct kvm_vcpu *vcpu)handle_userspace_tdg_vp_vmcall_exit (vcpu); } } + +/** +* Handle conversion of memory with @size beginning @gpa for @vm. Set +* @shared_to_private to true for shared to private conversions and false +* otherwise. +* +* Since this is just for selftests, we will just keep both pieces of backing +* memory allocated and not deallocate/allocate memory; we'll just do the +* minimum of calling KVM_MEMORY_ENCRYPT_REG_REGION and +* KVM_MEMORY_ENCRYPT_UNREG_REGION. +*/ +void handle_memory_conversion (struct kvm_vm *vm,uint64_t gpa,uint64_t size, +bool shared_to_private) +{ +struct kvm_memory_attributes range; + + range.address = gpa; + range.size = size; + range.attributes = shared_to_private ?KVM_MEMORY_ATTRIBUTE_PRIVATE :0 ; + range.flags =0 ; + +printf ("\t ... calling KVM_SET_MEMORY_ATTRIBUTES ioctl with gpa=%#lx, size=%#lx, attributes=%#llx\n" , gpa, size, range.attributes); + +vm_ioctl (vm,KVM_SET_MEMORY_ATTRIBUTES , &range); +}
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +135 -0
135 lines not on this page · raw message
Signature · 1 line
2.43.0.472.g3155946c3a-goog
Re: [RFC PATCH v5 23/29] KVM: selftests: TDX: Add shared memory test
Quoted 64 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +64
-0+void guest_shared_mem (void ) +{ +uint32_t *test_mem_shared_gva = + (uint32_t *)TDX_SHARED_MEM_TEST_SHARED_GVA ; + +uint64_t placeholder; +uint64_t ret; + +/* Map gpa as shared */ + ret =tdg_vp_vmcall_map_gpa (test_mem_shared_gpa,PAGE_SIZE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + + *test_mem_shared_gva =TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ; + +/* Exit so host can read shared value */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + +/* Read value written by host and send it back out for verification */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + (uint64_t *)test_mem_shared_gva); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); +} + +int verify_shared_mem (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +vm_vaddr_t test_mem_private_gva; +uint32_t *test_mem_hva; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_shared_mem); + +/* +* Set up shared memory page for testing by first allocating as private +* and then mapping the same GPA again as shared. This way, the TD does +* not have to remap its page tables at runtime. +*/ + test_mem_private_gva =vm_vaddr_alloc (vm, vm->page_size, +TDX_SHARED_MEM_TEST_PRIVATE_GVA ); +TEST_ASSERT_EQ (test_mem_private_gva,TDX_SHARED_MEM_TEST_PRIVATE_GVA ); + + test_mem_hva =addr_gva2hva (vm, test_mem_private_gva); +TEST_ASSERT (test_mem_hva !=NULL , +"Guest address not found in guest memory regions\n" ); + + test_mem_private_gpa =addr_gva2gpa (vm, test_mem_private_gva); +virt_pg_map_shared (vm,TDX_SHARED_MEM_TEST_SHARED_GVA , + test_mem_private_gpa); + + test_mem_shared_gpa = test_mem_private_gpa |BIT_ULL (vm->pa_bits -1 ); +sync_global_to_guest (vm, test_mem_private_gpa); +sync_global_to_guest (vm, test_mem_shared_gpa); +
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c line 104
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +10
-0+td_finalize (vm); + +printf ("Verifying shared memory accesses for TDX\n" ); + +/* Begin guest execution; guest writes to shared memory. */ +printf ("\t ... Starting guest execution\n" ); + +/* Handle map gpa as shared */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);
The first VMExit should be caused by tdvmcall map gpa, so it's impossible to be guest failure.
Move this line TDX_TEST_CHECK_GUEST_FAILURE(vcpu) to after the next td_vcpu_run() is better.
Quoted 20 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +20
-0+ +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ (*test_mem_hva,TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ); + + *test_mem_hva =TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ; +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ ( + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset), +TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ); + +printf ("\t ... PASSED\n" ); + +kvm_vm_free (vm); + +return 0 ; +}
Re: [RFC PATCH v5 23/29] KVM: selftests: TDX: Add shared memory test
Quoted 68 lines · Yan Zhao
Quoted 68 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +68
-0+void guest_shared_mem (void ) +{ +uint32_t *test_mem_shared_gva = + (uint32_t *)TDX_SHARED_MEM_TEST_SHARED_GVA ; + +uint64_t placeholder; +uint64_t ret; + +/* Map gpa as shared */ + ret =tdg_vp_vmcall_map_gpa (test_mem_shared_gpa,PAGE_SIZE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + + *test_mem_shared_gva =TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ; + +/* Exit so host can read shared value */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + +/* Read value written by host and send it back out for verification */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + (uint64_t *)test_mem_shared_gva); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); +} + +int verify_shared_mem (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +vm_vaddr_t test_mem_private_gva; +uint32_t *test_mem_hva; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_shared_mem); + +/* +* Set up shared memory page for testing by first allocating as private +* and then mapping the same GPA again as shared. This way, the TD does +* not have to remap its page tables at runtime. +*/ + test_mem_private_gva =vm_vaddr_alloc (vm, vm->page_size, +TDX_SHARED_MEM_TEST_PRIVATE_GVA ); +TEST_ASSERT_EQ (test_mem_private_gva,TDX_SHARED_MEM_TEST_PRIVATE_GVA ); + + test_mem_hva =addr_gva2hva (vm, test_mem_private_gva); +TEST_ASSERT (test_mem_hva !=NULL , +"Guest address not found in guest memory regions\n" ); + + test_mem_private_gpa =addr_gva2gpa (vm, test_mem_private_gva); +virt_pg_map_shared (vm,TDX_SHARED_MEM_TEST_SHARED_GVA , + test_mem_private_gpa); + + test_mem_shared_gpa = test_mem_private_gpa |BIT_ULL (vm->pa_bits -1 ); +sync_global_to_guest (vm, test_mem_private_gpa); +sync_global_to_guest (vm, test_mem_shared_gpa); + +td_finalize (vm); + +printf ("Verifying shared memory accesses for TDX\n" ); +
Quoted 9 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c line 104
Quoted 6 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +6
-0+/* Begin guest execution; guest writes to shared memory. */ +printf ("\t ... Starting guest execution\n" ); + +/* Handle map gpa as shared */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu);The first VMExit should be caused by tdvmcall map gpa, so it's impossible to be guest failure.
Ah, if KVM has bugs and returns to guest's map gpa tdvmcall as error without exiting to user space, then it's possible to meet guest failure here.
Quoted 2 lines
Move this line
TDX_TEST_CHECK_GUEST_FAILURE(vcpu)to after the nexttd_vcpu_run()is better.
So, looks it's required to be checked after every vcpu run. Without checking it (as in below), the selftest will not be able to print out the guest reported fatal error.
Quoted 22 lines
Quoted 20 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +20
-0+ +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ (*test_mem_hva,TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ); + + *test_mem_hva =TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ; +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ ( + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset), +TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ); + +printf ("\t ... PASSED\n" ); + +kvm_vm_free (vm); + +return 0 ; +}
Re: [RFC PATCH v5 23/29] KVM: selftests: TDX: Add shared memory test
In reply to Sagi ShaharQuoted 20 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +20
-0+int verify_shared_mem (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +vm_vaddr_t test_mem_private_gva; +uint32_t *test_mem_hva; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_shared_mem); + +/* +* Set up shared memory page for testing by first allocating as private +* and then mapping the same GPA again as shared. This way, the TD does +* not have to remap its page tables at runtime. +*/ + test_mem_private_gva =vm_vaddr_alloc (vm, vm->page_size, +TDX_SHARED_MEM_TEST_PRIVATE_GVA ); +TEST_ASSERT_EQ (test_mem_private_gva,TDX_SHARED_MEM_TEST_PRIVATE_GVA );
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c line 91
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +10
-0+ + test_mem_hva =addr_gva2hva (vm, test_mem_private_gva); +TEST_ASSERT (test_mem_hva !=NULL , +"Guest address not found in guest memory regions\n" ); + + test_mem_private_gpa =addr_gva2gpa (vm, test_mem_private_gva); +virt_pg_map_shared (vm,TDX_SHARED_MEM_TEST_SHARED_GVA , + test_mem_private_gpa); + + test_mem_shared_gpa = test_mem_private_gpa |BIT_ULL (vm->pa_bits -1 );
Why not use vm->arch.s_bit?
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c line 92
Quoted 1 line
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +1
-0+sync_global_to_guest (vm, test_mem_private_gpa);
test_mem_private_gpa is not used in guest. No need to sync.
Quoted 32 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +32
-0+sync_global_to_guest (vm, test_mem_shared_gpa); + +td_finalize (vm); + +printf ("Verifying shared memory accesses for TDX\n" ); + +/* Begin guest execution; guest writes to shared memory. */ +printf ("\t ... Starting guest execution\n" ); + +/* Handle map gpa as shared */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ (*test_mem_hva,TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ); + + *test_mem_hva =TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ; +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ ( + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset), +TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ); + +printf ("\t ... PASSED\n" ); + +kvm_vm_free (vm); + +return 0 ; +}
A message that is not in the archive (sent off-list or not yet received): DS7PR11MB7886AA5F8A19CDFCB5566B0EF6292@DS7PR11MB7886.namprd11.prod.outlook.com
Re: [RFC PATCH v5 23/29] KVM: selftests: TDX: Add shared memory test
Quoted 235 lines · Sagi Shahar
-----Original Message-----
From: Sagi Shahar <[email protected]>
Sent: Tuesday, December 12, 2023 12:47 PM
To: [email protected]; Ackerley Tng <[email protected]>; Afranji, Ryan <[email protected]>; Aktas, Erdem <[email protected]>; Sagi Shahar <[email protected]>; Yamahata, Isaku <[email protected]>
Cc: Sean Christopherson <[email protected]>; Paolo Bonzini <[email protected]>; Shuah Khan <[email protected]>; Peter Gonda <[email protected]>; Xu, Haibo1 <[email protected]>; Chao Peng <[email protected]>; Annapurve, Vishal <[email protected]>; Roger Wang <[email protected]>; Vipin Sharma <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: [RFC PATCH v5 23/29] KVM: selftests: TDX: Add shared memory testFrom: Ryan Afranji <[email protected]>
Adds a test that sets up shared memory between the host and guest.
Signed-off-by Ryan Afranji <[email protected]>Signed-off-by Sagi Shahar <[email protected]>Signed-off-by Ackerley Tng <[email protected]>--- tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/x86_64/tdx/tdx.h | 2 + .../kvm/include/x86_64/tdx/tdx_util.h | 2 + .../selftests/kvm/lib/x86_64/tdx/tdx.c | 26 ++++ .../selftests/kvm/lib/x86_64/tdx/tdx_util.c | 25 ++++ .../kvm/x86_64/tdx_shared_mem_test.c | 135 ++++++++++++++++++ 6 files changed, 191 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.ctools/testing/selftests/kvm/Makefile +1
-0@@ -156,6 +156,7 @@ TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_x86_64 += x86_64/tdx_vm_tests +TEST_GEN_PROGS_x86_64 += x86_64/tdx_shared_mem_test # Compiled outputs used by test targets TEST_GEN_PROGS_EXTENDED_x86_64 += x86_64/nx_huge_pages_test diff --git a/tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h b/tools/testing/selftests/kvm/include/x86_64/tdx/tdx.hindex
6b176de1e795..db4cc62abb5d100644tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +1
-0@@ -8,6 +8,7 @@#define TDG_VP_INFO 1#define TDG_VP_VMCALL_GET_TD_VM_CALL_INFO 0x10000 +#define TDG_VP_VMCALL_MAP_GPA 0x10001#define TDG_VP_VMCALL_REPORT_FATAL_ERROR 0x10003#define TDG_VP_VMCALL_INSTRUCTION_CPUID 10 @@ -36,5 +37,6 @@ uint64_t tdg_vp_vmcall_instruction_cpuid(uint32_t eax, uint32_t ecx, uint64_t tdg_vp_info(uint64_t *rcx, uint64_t *rdx,tools/testing/selftests/kvm/include/x86_64/tdx/tdx.h +2
-0uint64_t *r8, uint64_t *r9, uint64_t *r10, uint64_t *r11); +uint64_t tdg_vp_vmcall_map_gpa (uint64_t address,uint64_t size, +uint64_t *data_out);#endif // SELFTEST_TDX_TDX_H tools/testing/selftests/kvm/include/x86_64/tdx/tdx_util.h +2
-0@@ -13,5 +13,7 @@ void td_initialize(struct kvm_vm *vm, enum vm_mem_backing_src_type src_type, uint64_t attributes);void td_finalize (struct kvm_vm *vm);void td_vcpu_run (struct kvm_vcpu *vcpu); +void handle_memory_conversion (struct kvm_vm *vm,uint64_t gpa,uint64_t size, +bool shared_to_private);#endif // SELFTESTS_TDX_KVM_UTIL_H tools/testing/selftests/kvm/lib/x86_64/tdx/tdx.c +26
-0@@ -4,9 +4,11 @@#include "tdx/tdcall.h" #include "tdx/tdx.h" +#include "tdx/tdx_util.h" void handle_userspace_tdg_vp_vmcall_exit (struct kvm_vcpu *vcpu) { +struct kvm_vm *vm = vcpu->vm;struct kvm_tdx_vmcall *vmcall_info = &vcpu->run->tdx.u.vmcall;uint64_t vmcall_subfunction = vmcall_info->subfunction;@@ -20,6 +22,14 @@ void handle_userspace_tdg_vp_vmcall_exit(struct kvm_vcpu *vcpu) vcpu->run->system_event.data[2 ] = vmcall_info->in_r13; vmcall_info->status_code =0 ;break ; +case TDG_VP_VMCALL_MAP_GPA : +uint64_t gpa = vmcall_info->in_r12 & ~vm->arch.s_bit; +bool shared_to_private = !(vm->arch.s_bit & + vmcall_info->in_r12); +handle_memory_conversion (vm, gpa, vmcall_info->in_r13, + shared_to_private); + vmcall_info->status_code =0 ; +break ;default :TEST_FAIL ("TD VMCALL subfunction %lu is unsupported.\n" , vmcall_subfunction);@@ -210,3 +220,19 @@ uint64_t tdg_vp_info(uint64_t *rcx, uint64_t *rdx,return ret; } + +uint64_t tdg_vp_vmcall_map_gpa (uint64_t address,uint64_t size, +uint64_t *data_out) { +uint64_t ret; +struct tdx_hypercall_args args = { + .r11 =TDG_VP_VMCALL_MAP_GPA , + .r12 = address, + .r13 = size + }; + + ret =__tdx_hypercall (&args,TDX_HCALL_HAS_OUTPUT ); + +if (data_out) + *data_out = args.r11; +return ret; +}tools/testing/selftests/kvm/lib/x86_64/tdx/tdx_util.c +28
-0@@ -531,3 +531,28 @@ void td_vcpu_run(struct kvm_vcpu *vcpu)handle_userspace_tdg_vp_vmcall_exit (vcpu); } } + +/** +* Handle conversion of memory with @size beginning @gpa for @vm. Set +* @shared_to_private to true for shared to private conversions and +false +* otherwise. +* +* Since this is just for selftests, we will just keep both pieces of +backing +* memory allocated and not deallocate/allocate memory; we'll just do +the +* minimum of calling KVM_MEMORY_ENCRYPT_REG_REGION and +* KVM_MEMORY_ENCRYPT_UNREG_REGION. +*/ +void handle_memory_conversion (struct kvm_vm *vm,uint64_t gpa,uint64_t size, +bool shared_to_private) +{ +struct kvm_memory_attributes range; + + range.address = gpa; + range.size = size; + range.attributes = shared_to_private ?KVM_MEMORY_ATTRIBUTE_PRIVATE :0 ; + range.flags =0 ; + + printf("\t ... calling KVM_SET_MEMORY_ATTRIBUTES ioctl with gpa=%#lx, +size=%#lx, attributes=%#llx\n", gpa, size, range.attributes); + +vm_ioctl (vm,KVM_SET_MEMORY_ATTRIBUTES , &range); }tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +76
-0@@ -0,0 +1,135 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include <linux/kvm.h> +#include <stdint.h> + +#include "kvm_util_base.h" +#include "processor.h" +#include "tdx/tdcall.h" +#include "tdx/tdx.h" +#include "tdx/tdx_util.h" +#include "tdx/test_util.h" +#include "test_util.h" + +#define TDX_SHARED_MEM_TEST_PRIVATE_GVA (0x80000000) #define +TDX_SHARED_MEM_TEST_VADDR_SHARED_MASK BIT_ULL(30) +#define TDX_SHARED_MEM_TEST_SHARED_GVA \ + (TDX_SHARED_MEM_TEST_PRIVATE_GVA | \ + TDX_SHARED_MEM_TEST_VADDR_SHARED_MASK) + +#define TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE (0xcafecafe) #define +TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE (0xabcdabcd) + +#define TDX_SHARED_MEM_TEST_INFO_PORT 0x87 + +/* +* Shared variables between guest and host */ static uint64_t +test_mem_private_gpa;static uint64_t test_mem_shared_gpa; + +void guest_shared_mem (void ) +{ +uint32_t *test_mem_shared_gva = + (uint32_t *)TDX_SHARED_MEM_TEST_SHARED_GVA ; + +uint64_t placeholder; +uint64_t ret; + +/* Map gpa as shared */ + ret =tdg_vp_vmcall_map_gpa (test_mem_shared_gpa,PAGE_SIZE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + + *test_mem_shared_gva =TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ; + +/* Exit so host can read shared value */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + &placeholder); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); + +/* Read value written by host and send it back out for verification */ + ret =tdg_vp_vmcall_instruction_io (TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE , + (uint64_t *)test_mem_shared_gva); +if (ret) +tdx_test_fatal_with_data (ret, __LINE__); } + +int verify_shared_mem (void ) +{ +struct kvm_vm *vm; +struct kvm_vcpu *vcpu; + +vm_vaddr_t test_mem_private_gva; +uint32_t *test_mem_hva; + + vm =td_create (); +td_initialize (vm,VM_MEM_SRC_ANONYMOUS ,0 ); + vcpu =td_vcpu_add (vm,0 , guest_shared_mem); + +/* +* Set up shared memory page for testing by first allocating as private +* and then mapping the same GPA again as shared. This way, the TD does +* not have to remap its page tables at runtime. +*/ + test_mem_private_gva = vm_vaddr_alloc(vm, vm->page_size,
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c line 86
Quoted 10 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +10
-0+ TDX_SHARED_MEM_TEST_PRIVATE_GVA); +TEST_ASSERT_EQ (test_mem_private_gva,TDX_SHARED_MEM_TEST_PRIVATE_GVA ); + + test_mem_hva =addr_gva2hva (vm, test_mem_private_gva); +TEST_ASSERT (test_mem_hva !=NULL , +"Guest address not found in guest memory regions\n" ); + + test_mem_private_gpa =addr_gva2gpa (vm, test_mem_private_gva); +virt_pg_map_shared (vm,TDX_SHARED_MEM_TEST_SHARED_GVA , + test_mem_private_gpa);
As mentioned in the comments in [PATCH 22/29], how about replacing virt_pg_map_shared() with the following?
vm_phy_pages_conversion(); // new API to update protected_phy_pages virt_pg_map(); // set s_bit according to protected_phy_pages
Quoted 49 lines
tools/testing/selftests/kvm/x86_64/tdx_shared_mem_test.c new file +46
-1+ + test_mem_shared_gpa = test_mem_private_gpa |BIT_ULL (vm->pa_bits -1 ); +sync_global_to_guest (vm, test_mem_private_gpa); +sync_global_to_guest (vm, test_mem_shared_gpa); + +td_finalize (vm); + +printf ("Verifying shared memory accesses for TDX\n" ); + +/* Begin guest execution; guest writes to shared memory. */ +printf ("\t ... Starting guest execution\n" ); + +/* Handle map gpa as shared */ +td_vcpu_run (vcpu); +TDX_TEST_CHECK_GUEST_FAILURE (vcpu); + +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ (*test_mem_hva,TDX_SHARED_MEM_TEST_GUEST_WRITE_VALUE ); + + *test_mem_hva =TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ; +td_vcpu_run (vcpu); +TDX_TEST_ASSERT_IO (vcpu,TDX_SHARED_MEM_TEST_INFO_PORT ,4 , +TDG_VP_VMCALL_INSTRUCTION_IO_WRITE ); +TEST_ASSERT_EQ ( + *(uint32_t *)((void *)vcpu->run + vcpu->run->io.data_offset), +TDX_SHARED_MEM_TEST_HOST_WRITE_VALUE ); + +printf ("\t ... PASSED\n" ); + +kvm_vm_free (vm); + +return 0 ; +} + +int main (int argc,char **argv) +{ +if (!is_tdx_enabled ()) { +printf ("TDX is not supported by the KVM\n" +"Skipping the TDX tests.\n" ); +return 0 ; + } + +return verify_shared_mem (); +} --2.43.0.472.g3155946c3a-goog
RFC PATCH v5 24/29 KVM: selftests: Expose _vm_vaddr_alloc
In reply to Sagi ShaharFrom: Ackerley Tng <[email protected]>
vm_vaddr_alloc always allocates memory in memslot 0. This allows users of this function to choose which memslot to allocate virtual memory in.
--- tools/testing/selftests/kvm/include/kvm_util_base.h | 3 +++ tools/testing/selftests/kvm/lib/kvm_util.c | 6 +++--- 2 files changed, 6 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/include/kvm_util_base.h +3 -0
@@ -561,6 +561,9 @@ void vm_mem_region_delete(struct kvm_vm *vm, uint32_t slot);struct kvm_vcpu *__vm_vcpu_add (struct kvm_vm *vm,uint32_t vcpu_id);void vm_populate_vaddr_bitmap (struct kvm_vm *vm);vm_vaddr_t vm_vaddr_unused_gap (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min); +vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt);vm_vaddr_t vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min);vm_vaddr_t __vm_vaddr_alloc (struct kvm_vm *vm,size_t sz,vm_vaddr_t vaddr_min,enum kvm_mem_region_type type);
tools/testing/selftests/kvm/lib/kvm_util.c +3 -3
@@ -1410,9 +1410,9 @@ vm_vaddr_t vm_vaddr_unused_gap(struct kvm_vm *vm, size_t sz,* a unique set of pages, with the minimum real allocation being at least * a page. */ -static vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, -vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, -uint32_t data_memslot,bool encrypt) +vm_vaddr_t ____vm_vaddr_alloc (struct kvm_vm *vm,size_t sz, +vm_vaddr_t vaddr_min,vm_paddr_t paddr_min, +uint32_t data_memslot,bool encrypt) {uint64_t pages = (sz >> vm->page_shift) + ((sz % vm->page_size) !=0 );
Signature · 1 line
2.43.0.472.g3155946c3a-goog