aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2022-05-28 12:38:16 +0100
committerMarc Zyngier <maz@kernel.org>2022-06-09 12:02:12 +0100
commit690bacb83bc30d14821bd32cac1c5839b4a9ac6c (patch)
treefc26b966023be09f49b4eeaad79f415d3944f3f1
parentKVM: arm64: Add helpers to manipulate vcpu flags among a set (diff)
downloadlinux-dev-690bacb83bc30d14821bd32cac1c5839b4a9ac6c.tar.xz
linux-dev-690bacb83bc30d14821bd32cac1c5839b4a9ac6c.zip
KVM: arm64: Add three sets of flags to the vcpu state
It so appears that each of the vcpu flags is really belonging to one of three categories: - a configuration flag, set once and for all - an input flag generated by the kernel for the hypervisor to use - a state flag that is only for the kernel's own bookkeeping As we are going to split all the existing flags into these three sets, introduce all three in one go. No functional change other than a bit of bloat... Reviewed-by: Fuad Tabba <tabba@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org>
-rw-r--r--arch/arm64/include/asm/kvm_host.h9
1 files changed, 9 insertions, 0 deletions
diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
index 6d30ac7e3164..af45320f247f 100644
--- a/arch/arm64/include/asm/kvm_host.h
+++ b/arch/arm64/include/asm/kvm_host.h
@@ -335,6 +335,15 @@ struct kvm_vcpu_arch {
/* Miscellaneous vcpu state flags */
u64 flags;
+ /* Configuration flags, set once and for all before the vcpu can run */
+ u64 cflags;
+
+ /* Input flags to the hypervisor code, potentially cleared after use */
+ u64 iflags;
+
+ /* State flags for kernel bookkeeping, unused by the hypervisor code */
+ u64 sflags;
+
/*
* We maintain more than a single set of debug registers to support
* debugging the guest from the host and to maintain separate host and