summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2021-12-13 18:45:56 +0100
committerMichael Ellerman <mpe@ellerman.id.au>2021-12-14 12:49:36 +0100
commit63fa47ba886b86cbd58f03b3b01b04bd57a1f233 (patch)
tree40c2f8e9343db36383c454ee3fc76d4c6330a20f /Documentation
parentKVM: PPC: Book3S: Suppress failed alloc warning in H_COPY_TOFROM_GUEST (diff)
downloadlinux-63fa47ba886b86cbd58f03b3b01b04bd57a1f233.tar.xz
linux-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 'Documentation')
0 files changed, 0 insertions, 0 deletions