diff options
| author | Sean Christopherson <seanjc@google.com> | 2021-12-13 17:45:56 +0000 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2021-12-14 22:49:36 +1100 |
| commit | 63fa47ba886b86cbd58f03b3b01b04bd57a1f233 (patch) | |
| tree | 40c2f8e9343db36383c454ee3fc76d4c6330a20f /arch/powerpc/kvm/book3s_hv_nested.c | |
| parent | 792020907b11c6f9246c21977cab3bad985ae4b6 (diff) | |
| download | linux-stable-63fa47ba886b86cbd58f03b3b01b04bd57a1f233.tar.gz linux-stable-63fa47ba886b86cbd58f03b3b01b04bd57a1f233.tar.bz2 linux-stable-63fa47ba886b86cbd58f03b3b01b04bd57a1f233.zip | |
KVM: PPC: Book3S HV P9: Use kvm_arch_vcpu_get_wait() to get rcuwait object
Use kvm_arch_vcpu_get_wait() to get a vCPU's rcuwait object instead of
using vcpu->wait directly in kvmhv_run_single_vcpu(). Functionally, this
is a nop as vcpu->arch.waitp is guaranteed to point at vcpu->wait. But
that is not obvious at first glance, and a future change coming in via
the KVM tree, commit 510958e99721 ("KVM: Force PPC to define its own
rcuwait object"), will hide vcpu->wait from architectures that define
__KVM_HAVE_ARCH_WQP to prevent generic KVM from attepting to wake a vCPU
with the wrong rcuwait object.
Reported-by: Sachin Sant <sachinp@linux.vnet.ibm.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Tested-by: Sachin Sant <sachinp@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20211213174556.3871157-1-seanjc@google.com
Diffstat (limited to 'arch/powerpc/kvm/book3s_hv_nested.c')
0 files changed, 0 insertions, 0 deletions