Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kvmarm@lists.linux.dev, oliver.upton@linux.dev,
	catalin.marinas@arm.com, joey.gouly@arm.com,
	suzuki.poulose@arm.com, yuzenghui@huawei.com, will@kernel.org,
	christoffer.dall@arm.com
Subject: Re: [PATCH v1 3/4] KVM: arm64: Convert KVM_ARM_VCPU_* features into an enum
Date: Mon, 14 Oct 2024 18:13:31 +0100	[thread overview]
Message-ID: <867caa6210.wl-maz@kernel.org> (raw)
In-Reply-To: <20241014165809.984883-4-tabba@google.com>

On Mon, 14 Oct 2024 17:58:08 +0100,
Fuad Tabba <tabba@google.com> wrote:
> 
> Instead of using compile time defines, convert the KVM_ARM_VCPU_*
> features into an enum. Among other things, this reduces the
> chances of missing to update KVM_ARM_VCPU_MAX_FEATURES.
> 
> Also rename KVM_VCPU_MAX_FEATURES and KVM_ARM_VCPU_VALID_FEATURES
> to KVM_ARM_VCPU_MAX_FEATURES and KVM_ARM_VCPU_VALID_FEATURES in
> order to match the features they're counting.
> 
> No functional change intended.
> 
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
>  arch/arm64/include/asm/kvm_host.h |  2 +-
>  arch/arm64/include/uapi/asm/kvm.h | 25 ++++++++++++++-----------
>  arch/arm64/kvm/arm.c              | 10 +++++-----
>  3 files changed, 20 insertions(+), 17 deletions(-)
> 
> diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
> index 85901afeb332..9b7bf4ba07a3 100644
> --- a/arch/arm64/include/asm/kvm_host.h
> +++ b/arch/arm64/include/asm/kvm_host.h
> @@ -326,7 +326,7 @@ struct kvm_arch {
>  	unsigned long flags;
>  
>  	/* VM-wide vCPU feature set */
> -	DECLARE_BITMAP(vcpu_features, KVM_VCPU_MAX_FEATURES);
> +	DECLARE_BITMAP(vcpu_features, KVM_ARM_VCPU_MAX_FEATURES);
>  
>  	/* MPIDR to vcpu index mapping, optional */
>  	struct kvm_mpidr_data *mpidr_data;
> diff --git a/arch/arm64/include/uapi/asm/kvm.h b/arch/arm64/include/uapi/asm/kvm.h
> index 2d5fd0ed7dff..b6ebd79b8373 100644
> --- a/arch/arm64/include/uapi/asm/kvm.h
> +++ b/arch/arm64/include/uapi/asm/kvm.h
> @@ -100,17 +100,20 @@ struct kvm_regs {
>  #define KVM_VGIC_V3_REDIST_SIZE		(2 * SZ_64K)
>  #define KVM_VGIC_V3_ITS_SIZE		(2 * SZ_64K)
>  
> -#define KVM_ARM_VCPU_POWER_OFF		0 /* CPU is started in OFF state */
> -#define KVM_ARM_VCPU_EL1_32BIT		1 /* CPU running a 32bit VM */
> -#define KVM_ARM_VCPU_PSCI_0_2		2 /* CPU uses PSCI v0.2 */
> -#define KVM_ARM_VCPU_PMU_V3		3 /* Support guest PMUv3 */
> -#define KVM_ARM_VCPU_SVE		4 /* enable SVE for this CPU */
> -#define KVM_ARM_VCPU_PTRAUTH_ADDRESS	5 /* VCPU uses address authentication */
> -#define KVM_ARM_VCPU_PTRAUTH_GENERIC	6 /* VCPU uses generic authentication */
> -#define KVM_ARM_VCPU_HAS_EL2		7 /* Support nested virtualization */
> -
> -#define KVM_VCPU_MAX_FEATURES 8
> -#define KVM_VCPU_VALID_FEATURES	(BIT(KVM_VCPU_MAX_FEATURES) - 1)
> +enum kvm_arm_vcpu_features {
> +	KVM_ARM_VCPU_POWER_OFF = 0,	/* CPU is started in OFF state */
> +	KVM_ARM_VCPU_EL1_32BIT,		/* CPU running a 32bit VM */
> +	KVM_ARM_VCPU_PSCI_0_2,		/* CPU uses PSCI v0.2 */
> +	KVM_ARM_VCPU_PMU_V3,		/* Support guest PMUv3 */
> +	KVM_ARM_VCPU_SVE,		/* enable SVE for this CPU */
> +	KVM_ARM_VCPU_PTRAUTH_ADDRESS,	/* VCPU uses address authentication */
> +	KVM_ARM_VCPU_PTRAUTH_GENERIC,	/* VCPU uses generic authentication */
> +	KVM_ARM_VCPU_HAS_EL2,		/* Support nested virtualization */
> +
> +	KVM_ARM_VCPU_MAX_FEATURES,	/* Must be last */
> +};

This is going to break any userspace that has code shaped like this:

#ifdef KVM_ARM_VCPU_SVE
[...]
#endif

Not necessarily a good pattern, but nonetheless a valid one. So you
*must* preserve the #defines, even if you define them along the lines
of:

#define	KVM_ARM_VCPU_SVE	KVM_ARM_VCPU_SVE

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2024-10-14 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 16:58 [PATCH v1 0/4] KVM: arm64: Update KVM_VCPU_MAX_FEATURES and refactor to avoid same issue Fuad Tabba
2024-10-14 16:58 ` [PATCH v1 1/4] KVM: arm64: Update the value of KVM_VCPU_MAX_FEATURES Fuad Tabba
2024-10-14 16:58 ` [PATCH v1 2/4] KVM: arm64: Move KVM_VCPU_MAX_FEATURES to the features it is counting Fuad Tabba
2024-10-14 16:58 ` [PATCH v1 3/4] KVM: arm64: Convert KVM_ARM_VCPU_* features into an enum Fuad Tabba
2024-10-14 17:13   ` Marc Zyngier [this message]
2024-10-14 16:58 ` [PATCH v1 4/4] KVM: arm64: Convert KVM_ARCH_FLAG_* " Fuad Tabba
2024-10-14 17:17 ` [PATCH v1 0/4] KVM: arm64: Update KVM_VCPU_MAX_FEATURES and refactor to avoid same issue Marc Zyngier
2024-10-14 18:17   ` Fuad Tabba
2024-10-15 10:15     ` Marc Zyngier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867caa6210.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox