From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
kvmarm@lists.linux.dev, catalin.marinas@arm.com, will@kernel.org,
mark.rutland@arm.com, cohuck@redhat.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 v4 3/3] arm64: paravirt: Enable errata based on implementation CPUs
Date: Thu, 19 Dec 2024 09:40:55 -0800 [thread overview]
Message-ID: <Z2RapzikZQGgeE_6@linux.dev> (raw)
In-Reply-To: <86bjx8q995.wl-maz@kernel.org>
On Thu, Dec 19, 2024 at 10:04:22AM +0000, Marc Zyngier wrote:
> > +void __init pv_target_impl_cpu_init(void)
> > +{
> > + struct arm_smccc_res res;
> > + int index = 0, max_idx = -1;
> > +
> > + /* Check we have already set targets */
> > + if (target_impl_cpu_num)
> > + return;
> > +
> > + do {
> > + arm_smccc_1_1_invoke(ARM_SMCCC_VENDOR_HYP_KVM_DISCOVER_IMPL_CPUS_FUNC_ID,
> > + index, &res);
> > + if (res.a0 == SMCCC_RET_NOT_SUPPORTED)
> > + return;
>
> Can't you probe for this as part of the KVM guest services?
+1, this needs to be predicated on actually detecting the hypervisor as
KVM.
> > +
> > + if (max_idx < 0) {
> > + /* res.a0 should have a valid maximum CPU implementation index */
> > + if (res.a0 >= MAX_TARGET_IMPL_CPUS)
> > + return;
> > + max_idx = res.a0;
> > + }
> > +
> > + target_impl_cpus[index].midr = res.a1;
> > + target_impl_cpus[index].revidr = res.a2;
> > + index++;
> > + } while (index <= max_idx);
> > +
> > + target_impl_cpu_num = index;
> > + pr_info("Number of target implementation CPUs is %d\n", target_impl_cpu_num);
> > +}
> > +
> > int __init pv_time_init(void)
> > {
> > int ret;
>
> Independent of this, I wonder what we should output in sysfs
> (/sys/devices/system/cpu/cpu*/regs/identification/*).
It's a bit crap, but maybe implementation index 0 gets reported through
the 'main' midr/revidr files, otherwise have a directory per
implementation index of midr/revidr.
--
Thanks,
Oliver
next prev parent reply other threads:[~2024-12-19 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 10:53 [PATCH v4 0/3] KVM: arm64: Errata management for VM Live migration Shameer Kolothum
2024-12-18 10:53 ` [PATCH v4 1/3] arm64: Modify _midr_range() functions to read MIDR/REVIDR internally Shameer Kolothum
2024-12-19 7:05 ` Cornelia Huck
2024-12-18 10:53 ` [PATCH v4 2/3] KVM: arm64: Introduce hypercall support for retrieving target implementations Shameer Kolothum
2024-12-19 7:07 ` Cornelia Huck
2024-12-19 9:51 ` Marc Zyngier
2024-12-18 10:53 ` [PATCH v4 3/3] arm64: paravirt: Enable errata based on implementation CPUs Shameer Kolothum
2024-12-19 7:09 ` Cornelia Huck
2024-12-19 10:04 ` Marc Zyngier
2024-12-19 17:40 ` Oliver Upton [this message]
2024-12-20 11:17 ` Marc Zyngier
2024-12-20 15:00 ` Cornelia Huck
2024-12-19 10:07 ` [PATCH v4 0/3] KVM: arm64: Errata management for VM Live migration Marc Zyngier
2024-12-19 17:36 ` Oliver Upton
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=Z2RapzikZQGgeE_6@linux.dev \
--to=oliver.upton@linux.dev \
--cc=anthony.jebson@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=cohuck@redhat.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.