From: Fuad Tabba <tabba@google.com>
To: kvmarm@lists.linux.dev
Cc: maz@kernel.org, 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,
tabba@google.com
Subject: [PATCH v1 0/4] KVM: arm64: Update KVM_VCPU_MAX_FEATURES and refactor to avoid same issue
Date: Mon, 14 Oct 2024 17:58:05 +0100 [thread overview]
Message-ID: <20241014165809.984883-1-tabba@google.com> (raw)
The value of KVM_VCPU_MAX_FEATURES has not been updated since
adding new features in commit 89b0e7de3451 ("KVM: arm64: nv:
Introduce nested virtualization VCPU feature").
This patch series updates its value and refactors VCPU feature
values as well as KVM arch flags to reduce the chances of this
happening again.
Based on Linux 6.12-rc3 (8e929cb546ee).
Cheers,
/fuad
Fuad Tabba (4):
KVM: arm64: Update the value of KVM_VCPU_MAX_FEATURES
KVM: arm64: Move KVM_VCPU_MAX_FEATURES to the features it is counting
KVM: arm64: Convert KVM_ARM_VCPU_* features into an enum
KVM: arm64: Convert KVM_ARCH_FLAG_* into an enum
arch/arm64/include/asm/kvm_host.h | 58 +++++++++++++++++--------------
arch/arm64/include/uapi/asm/kvm.h | 22 +++++++-----
arch/arm64/kvm/arm.c | 12 ++++---
3 files changed, 52 insertions(+), 40 deletions(-)
base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354
--
2.47.0.rc1.288.g06298d1525-goog
next reply other threads:[~2024-10-14 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:58 Fuad Tabba [this message]
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
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=20241014165809.984883-1-tabba@google.com \
--to=tabba@google.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.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