[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163952881459.928111.11067384310708851429.b4-ty@ellerman.id.au>
Date: Wed, 15 Dec 2021 11:40:14 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Sean Christopherson <seanjc@...gle.com>,
Michael Ellerman <mpe@...erman.id.au>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Sachin Sant <sachinp@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Nicholas Piggin <npiggin@...il.com>
Subject: Re: [PATCH] KVM: PPC: Book3S HV P9: Use kvm_arch_vcpu_get_wait() to get rcuwait object
On Mon, 13 Dec 2021 17:45:56 +0000, Sean Christopherson wrote:
> 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.
>
> [...]
Applied to powerpc/next.
[1/1] KVM: PPC: Book3S HV P9: Use kvm_arch_vcpu_get_wait() to get rcuwait object
https://git.kernel.org/powerpc/c/63fa47ba886b86cbd58f03b3b01b04bd57a1f233
cheers
Powered by blists - more mailing lists