On Thu, 02 May 2024 16:40:30 +0100, Marc Zyngier wrote:
> The per-CPU host context structure contains a __hyp_running_vcpu that
> serves as a replacement for kvm_get_current_vcpu() in contexts where
> we cannot make direct use of it (such as in the nVHE hypervisor).
> Since there is a lot of common code between nVHE and VHE, the latter
> also populates this field even if kvm_get_running_vcpu() always works.
>
> We currently pretty inconsistent when populating __hyp_running_vcpu
> to point to the currently running vcpu:
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Move management of __hyp_running_vcpu to load/put on VHE
commit: 9a39359903fea9c354d89dce81ffd952859c90dc
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
