diff options
| author | Sean Christopherson <seanjc@google.com> | 2025-10-30 23:09:25 +0300 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2025-11-05 22:03:11 +0300 |
| commit | 50efc2340a598da4bafa40bc01e18f8cf73a4ae3 (patch) | |
| tree | dbac6ade99efb8fc181326f759ab2fca00afbcdb /scripts | |
| parent | 0a0da3f92118950862700497bc7917f0fbf6a6e8 (diff) | |
| download | linux-50efc2340a598da4bafa40bc01e18f8cf73a4ae3.tar.xz | |
KVM: Rename kvm_arch_vcpu_async_ioctl() to kvm_arch_vcpu_unlocked_ioctl()
Rename the "async" ioctl API to "unlocked" so that upcoming usage in x86's
TDX code doesn't result in a massive misnomer. To avoid having to retry
SEAMCALLs, TDX needs to acquire kvm->lock *and* all vcpu->mutex locks, and
acquiring all of those locks after/inside the current vCPU's mutex is a
non-starter. However, TDX also needs to acquire the vCPU's mutex and load
the vCPU, i.e. the handling is very much not async to the vCPU.
No functional change intended.
Acked-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Reviewed-by: Yan Zhao <yan.y.zhao@intel.com>
Tested-by: Yan Zhao <yan.y.zhao@intel.com>
Tested-by: Kai Huang <kai.huang@intel.com>
Link: https://patch.msgid.link/20251030200951.3402865-3-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
