Thread (23 messages) 23 messages, 3 authors, 2021-11-30

Re: [RFC PATCH v2 02/11] KVM: Introduce kvm_vcpu_has_run_once

From: Raghavendra Rao Ananta <hidden>
Date: 2021-11-23 18:32:07
Also in: kvm, kvmarm, lkml

Hello Marc,

On Mon, Nov 22, 2021 at 8:27 AM Marc Zyngier [off-list ref] wrote:
On Sat, 13 Nov 2021 01:22:25 +0000,
Raghavendra Rao Ananta [off-list ref] wrote:
quoted
Architectures such as arm64 and riscv uses vcpu variables
such as has_run_once and ran_atleast_once, respectively,
to mark if the vCPU has started running. Since these are
architecture agnostic variables, introduce
kvm_vcpu_has_run_once() as a core kvm functionality and
use this instead of the architecture defined variables.

No functional change intended.

Signed-off-by: Raghavendra Rao Ananta <redacted>
arm64 is moving away from this, see [1]. You also don't need any new
state, as vcpu->pid gives you exactly what you need.
Thanks for the pointer. I can directly use this!
Happy to queue additional patches on top if you want to deal with
riscv.
Just to clarify, you mean get the kvm support for riscv on kvmarm-next?
If yes, then sure, I can make changes in riscv to use
vcpu_has_run_once() from your series.

Regards,
Raghavendra

Thanks,

        M.

[1] https://lore.kernel.org/all/20211018211158.3050779-1-maz@kernel.org/ (local)

--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help