From: Eric Auger <eric.auger@redhat.com>
To: Shameer Kolothum <shameerkolothum@gmail.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, cohuck@redhat.com, sebott@redhat.com,
berrange@redhat.com, maz@kernel.org, oliver.upton@linux.dev,
armbru@redhat.com, linuxarm@huawei.com, wangzhou1@hisilicon.com,
jiangkunkun@huawei.com, jonathan.cameron@huawei.com,
salil.mehta@huawei.com, yangjinqian1@huawei.com,
shameerali.kolothum.thodi@huawei.com
Subject: Re: [RFC PATCH RESEND 1/4] target/arm/kvm: Introduce helper to check target impl CPU support
Date: Sat, 9 Aug 2025 18:21:10 +0200 [thread overview]
Message-ID: <5c29e11f-eac1-40a0-aec0-a80131f7de56@redhat.com> (raw)
In-Reply-To: <20250801074730.28329-2-shameerkolothum@gmail.com>
Hi Shameer,
On 8/1/25 9:47 AM, Shameer Kolothum wrote:
> From: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
>
> The helper function will try to set the SMCCC filters for KVM vendor
> hypercalls related to target implementation CPU support. It also
> checks the kernel support for writable implementation ID registers
> (MIDR/REVIDR/AIDR) and enables it.
>
> Subsequent patches for Target Impl CPU support will make use of this
> helper.
>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> ---
> target/arm/kvm.c | 72 ++++++++++++++++++++++++++++++++++++++++++++
> target/arm/kvm_arm.h | 12 ++++++++
> 2 files changed, 84 insertions(+)
>
> diff --git a/target/arm/kvm.c b/target/arm/kvm.c
> index 3f41f99e23..eb04640b50 100644
> --- a/target/arm/kvm.c
> +++ b/target/arm/kvm.c
> @@ -2072,6 +2072,78 @@ bool kvm_arm_mte_supported(void)
> return kvm_check_extension(kvm_state, KVM_CAP_ARM_MTE);
> }
>
> +static bool kvm_arm_set_vm_attr(struct kvm_device_attr *attr, const char *name)
> +{
> + int err;
> +
> + err = kvm_vm_ioctl(kvm_state, KVM_HAS_DEVICE_ATTR, attr);
> + if (err != 0) {
> + error_report("%s: KVM_HAS_DEVICE_ATTR: %s", name, strerror(-err));
> + return false;
> + }
> +
> + err = kvm_vm_ioctl(kvm_state, KVM_SET_DEVICE_ATTR, attr);
> + if (err != 0) {
> + error_report("%s: KVM_SET_DEVICE_ATTR: %s", name, strerror(-err));
> + return false;
> + }
> +
> + return true;
> +}
> +
> +static bool kvm_arm_set_smccc_filter(uint64_t func, uint8_t faction)
nit: base is _u32 in the kernel
> +{
> + struct kvm_smccc_filter filter = {
> + .base = func,
> + .nr_functions = 1,
> + .action = faction,
> + };
> + struct kvm_device_attr attr = {
> + .group = KVM_ARM_VM_SMCCC_CTRL,
> + .attr = KVM_ARM_VM_SMCCC_FILTER,
> + .flags = 0,
> + .addr = (uintptr_t)&filter,
> + };
> +
> + if (!kvm_arm_set_vm_attr(&attr, "SMCCC Filter")) {
> + error_report("failed to set SMCCC filter in KVM Host");
maybe also output @func in the error msg
> + return false;
> + }
> +
> + return true;
> +}
> +
> +bool kvm_arm_target_impl_cpus_supported(void)
> +{
> + if (!kvm_arm_set_smccc_filter(
> + ARM_SMCCC_VENDOR_HYP_KVM_DISCOVER_IMPL_VER_FUNC_ID,
> + KVM_SMCCC_FILTER_FWD_TO_USER)) {
> + error_report("ARM_SMCCC_KVM_FUNC_DISCOVER_IMPL_VER fwd filter "
> + "install failed");
> + return false;
> + }
> +
> + if (!kvm_arm_set_smccc_filter(
> + ARM_SMCCC_VENDOR_HYP_KVM_DISCOVER_IMPL_CPUS_FUNC_ID,
> + KVM_SMCCC_FILTER_FWD_TO_USER)) {
> + error_report("ARM_SMCCC_KVM_FUNC_DISCOVER_IMPL_CPUS fwd filter "
> + "install failed");
> + return false;
> + }
> +
> + if (!kvm_check_extension(kvm_state, KVM_CAP_ARM_WRITABLE_IMP_ID_REGS)) {
> + error_report("KVM_CAP_ARM_WRITABLE_IMP_ID_REGS not supported");
> + return false;
> + }
> +
> + if (kvm_vm_enable_cap(kvm_state, KVM_CAP_ARM_WRITABLE_IMP_ID_REGS, 0)) {
> + error_report("Failed to enable KVM_CAP_ARM_WRITABLE_IMP_ID_REGS cap");
> + return false;
> + }
> +
> + return true;
> +}
> +
> QEMU_BUILD_BUG_ON(KVM_ARM64_SVE_VQ_MIN != 1);
>
> uint32_t kvm_arm_sve_get_vls(ARMCPU *cpu)
> diff --git a/target/arm/kvm_arm.h b/target/arm/kvm_arm.h
> index ba5de45f86..3cd6447901 100644
> --- a/target/arm/kvm_arm.h
> +++ b/target/arm/kvm_arm.h
> @@ -207,6 +207,13 @@ bool kvm_arm_sve_supported(void);
> */
> bool kvm_arm_mte_supported(void);
>
> +/**
> + * kvm_arm_target_impl_cpus_supported:
> + *
> + * Returns: true if KVM can enable target impl CPUs, and false otherwise.
> + */
> +bool kvm_arm_target_impl_cpus_supported(void);
> +
> /**
> * kvm_arm_get_max_vm_ipa_size:
> * @ms: Machine state handle
> @@ -263,6 +270,11 @@ static inline bool kvm_arm_mte_supported(void)
> return false;
> }
>
> +static inline bool kvm_arm_target_impl_cpus_supported(void)
> +{
> + return false;
> +}
> +
> static inline int kvm_arm_get_writable_id_regs(ARMCPU *cpu, IdRegMap *idregmap)
> {
> return -ENOSYS;
Otherwise looks good to me.
Thanks
Eric
next prev parent reply other threads:[~2025-08-09 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 7:47 [RFC PATCH RESEND 0/4] hw/arm/virt: Add support for Target Implementation CPUs Shameer Kolothum
2025-08-01 7:47 ` [RFC PATCH RESEND 1/4] target/arm/kvm: Introduce helper to check target impl CPU support Shameer Kolothum
2025-08-09 16:21 ` Eric Auger [this message]
2025-08-01 7:47 ` [RFC PATCH RESEND 2/4] target/arm/kvm: Add QAPI struct ArmTargetImplCPU Shameer Kolothum
2025-08-09 16:23 ` Eric Auger
2025-08-01 7:47 ` [RFC PATCH RESEND 3/4] target/arm/kvm: Handle KVM Target Imp CPU hypercalls Shameer Kolothum
2025-09-19 10:51 ` Sebastian Ott
2025-08-01 7:47 ` [RFC PATCH RESEND 4/4] hw/arm/virt: Add Target Implementation CPU support Shameer Kolothum
2025-08-09 16:21 ` Eric Auger
2025-08-01 8:31 ` [RFC PATCH RESEND 0/4] hw/arm/virt: Add support for Target Implementation CPUs Cornelia Huck
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=5c29e11f-eac1-40a0-aec0-a80131f7de56@redhat.com \
--to=eric.auger@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=jiangkunkun@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=salil.mehta@huawei.com \
--cc=sebott@redhat.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shameerkolothum@gmail.com \
--cc=wangzhou1@hisilicon.com \
--cc=yangjinqian1@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;
as well as URLs for NNTP newsgroup(s).