diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-10-06 03:34:08 +0300 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2022-11-17 03:58:53 +0300 |
| commit | 28a65567acb51759079adf5c6e3fcd047cda8120 (patch) | |
| tree | 86f6d7389f4f4c15be3f6b15bc7e2abd04996bdd /tools/testing/selftests/kvm/lib/x86_64/ucall.c | |
| parent | 03b4750533fc6519845ac2ca0e1d88a81ac260a1 (diff) | |
| download | linux-28a65567acb51759079adf5c6e3fcd047cda8120.tar.xz | |
KVM: selftests: Drop now-unnecessary ucall_uninit()
Drop ucall_uninit() and ucall_arch_uninit() now that ARM doesn't modify
the host's copy of ucall_exit_mmio_addr, i.e. now that there's no need to
reset the pointer before potentially creating a new VM. The few calls to
ucall_uninit() are all immediately followed by kvm_vm_free(), and that is
likely always going to hold true, i.e. it's extremely unlikely a test
will want to effectively disable ucall in the middle of a test.
Reviewed-by: Andrew Jones <andrew.jones@linux.dev>
Tested-by: Peter Gonda <pgonda@google.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/r/20221006003409.649993-7-seanjc@google.com
Diffstat (limited to 'tools/testing/selftests/kvm/lib/x86_64/ucall.c')
| -rw-r--r-- | tools/testing/selftests/kvm/lib/x86_64/ucall.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/tools/testing/selftests/kvm/lib/x86_64/ucall.c b/tools/testing/selftests/kvm/lib/x86_64/ucall.c index 016a0487cf72..eb8bf55b359a 100644 --- a/tools/testing/selftests/kvm/lib/x86_64/ucall.c +++ b/tools/testing/selftests/kvm/lib/x86_64/ucall.c @@ -12,10 +12,6 @@ void ucall_arch_init(struct kvm_vm *vm, vm_paddr_t mmio_gpa) { } -void ucall_arch_uninit(struct kvm_vm *vm) -{ -} - void ucall_arch_do_ucall(vm_vaddr_t uc) { asm volatile("in %[port], %%al" |