[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zgpwcg0s.wl-maz@kernel.org>
Date: Mon, 22 Nov 2021 16:27:15 +0000
From: Marc Zyngier <maz@...nel.org>
To: Raghavendra Rao Ananta <rananta@...gle.com>
Cc: Andrew Jones <drjones@...hat.com>,
James Morse <james.morse@....com>,
Alexandru Elisei <alexandru.elisei@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Paolo Bonzini <pbonzini@...hat.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Peter Shier <pshier@...gle.com>,
Ricardo Koller <ricarkol@...gle.com>,
Oliver Upton <oupton@...gle.com>,
Reiji Watanabe <reijiw@...gle.com>,
Jing Zhang <jingzhangos@...gle.com>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC PATCH v2 02/11] KVM: Introduce kvm_vcpu_has_run_once
On Sat, 13 Nov 2021 01:22:25 +0000,
Raghavendra Rao Ananta <rananta@...gle.com> wrote:
>
> 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 <rananta@...gle.com>
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.
Happy to queue additional patches on top if you want to deal with
riscv.
Thanks,
M.
[1] https://lore.kernel.org/all/20211018211158.3050779-1-maz@kernel.org/
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists