From: Cornelia Huck <cohuck@redhat.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
kvmarm@lists.linux.dev, maz@kernel.org, oliver.upton@linux.dev
Cc: catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
eric.auger@redhat.com, sebott@redhat.com, yuzenghui@huawei.com,
wangzhou1@hisilicon.com, jiangkunkun@huawei.com,
jonathan.cameron@huawei.com, anthony.jebson@huawei.com,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com
Subject: Re: [PATCH v5 3/4] KVM: arm64: Report all the KVM/arm64-specific hypercalls
Date: Mon, 27 Jan 2025 13:47:23 +0100 [thread overview]
Message-ID: <8734h48lus.fsf@redhat.com> (raw)
In-Reply-To: <20250124151732.6072-4-shameerali.kolothum.thodi@huawei.com>
On Fri, Jan 24 2025, Shameer Kolothum <shameerali.kolothum.thodi@huawei.com> wrote:
> Currently ARM_SMCCC_VENDOR_HYP_KVM_FEATURES_FUNC_ID returns the
> bitmap corresponding to KVM_REG_ARM_VENDOR_HYP_BMAP and it only
> returns _KVM_FEATURES_FUNC_ID and _KVM_PTP_FUNC_ID. Change that
> to return all the KVM/arm64-specific hypercalls exposed by
> KVM/arm64 to guest operating systems.
>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> ---
> arch/arm64/kvm/hypercalls.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/hypercalls.c b/arch/arm64/kvm/hypercalls.c
> index 27ce4cb44904..6132cb542200 100644
> --- a/arch/arm64/kvm/hypercalls.c
> +++ b/arch/arm64/kvm/hypercalls.c
> @@ -359,7 +359,11 @@ int kvm_smccc_call_handler(struct kvm_vcpu *vcpu)
> val[3] = ARM_SMCCC_VENDOR_HYP_UID_KVM_REG_3;
> break;
> case ARM_SMCCC_VENDOR_HYP_KVM_FEATURES_FUNC_ID:
> - val[0] = smccc_feat->vendor_hyp_bmap;
> + val[0] = GENMASK(ARM_SMCCC_KVM_FUNC_MMIO_GUARD,
> + ARM_SMCCC_KVM_FUNC_FEATURES);
Don't you need to exclude the reserved ids 5 and 6?
> + /* Function numbers 8-63 are reserved for pKVM for now */
> + val[2] = GENMASK((ARM_SMCCC_KVM_FUNC_DISCOVER_IMPL_CPUS - 64),
> + (ARM_SMCCC_KVM_FUNC_DISCOVER_IMPL_VER - 64));
> break;
> case ARM_SMCCC_VENDOR_HYP_KVM_PTP_FUNC_ID:
> kvm_ptp_get_time(vcpu, val);
next prev parent reply other threads:[~2025-01-27 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 15:17 [PATCH v5 0/4] KVM: arm64: Errata management for VM Live migration Shameer Kolothum
2025-01-24 15:17 ` [PATCH v5 1/4] arm64: Modify _midr_range() functions to read MIDR/REVIDR internally Shameer Kolothum
2025-01-24 15:17 ` [PATCH v5 2/4] KVM: arm64: Introduce hypercall support for retrieving target implementations Shameer Kolothum
2025-01-27 12:50 ` Cornelia Huck
2025-01-27 17:26 ` Oliver Upton
2025-01-28 14:16 ` Shameerali Kolothum Thodi
2025-01-24 15:17 ` [PATCH v5 3/4] KVM: arm64: Report all the KVM/arm64-specific hypercalls Shameer Kolothum
2025-01-27 12:47 ` Cornelia Huck [this message]
2025-01-27 13:35 ` Shameerali Kolothum Thodi
2025-01-27 17:05 ` Oliver Upton
2025-01-27 17:24 ` Shameerali Kolothum Thodi
2025-01-24 15:17 ` [PATCH v5 4/4] arm64: paravirt: Enable errata based on implementation CPUs Shameer Kolothum
2025-01-27 12:53 ` Cornelia Huck
2025-01-27 17:37 ` Oliver Upton
2025-02-04 16:45 ` [PATCH v5 0/4] KVM: arm64: Errata management for VM Live migration Sebastian Ott
2025-02-04 17:11 ` Marc Zyngier
2025-02-04 17:42 ` Sebastian Ott
2025-02-04 18: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=8734h48lus.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=anthony.jebson@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=eric.auger@redhat.com \
--cc=jiangkunkun@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=sebott@redhat.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=wangzhou1@hisilicon.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;
as well as URLs for NNTP newsgroup(s).