From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
Wei Huang <wei@redhat.com>,
Andrew Jones <ajones@ventanamicro.com>
Subject: Re: [PATCH v2 5/5] target/arm/kvm: Report PMU unavailability
Date: Tue, 16 Jul 2024 11:22:06 +0200 [thread overview]
Message-ID: <3ef05b2b-06da-40ca-9344-2d5a8cdd6dba@linaro.org> (raw)
In-Reply-To: <20240716-pmu-v2-5-f3e3e4b2d3d5@daynix.com>
On 16/7/24 10:28, Akihiko Odaki wrote:
> target/arm/kvm.c checked PMU availability but claimed PMU is
> available even if it is not. In fact, Asahi Linux supports KVM but lacks
> PMU support. Only advertise PMU availability only when it is really
> available.
>
> Fixes: dc40d45ebd8e ("target/arm/kvm: Move kvm_arm_get_host_cpu_features and unexport")
Commit dc40d45ebd8e only moves the code around. I suppose you meant:
Fixes: 929e754d5a ("arm: Add an option to turn on/off vPMU support")
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> target/arm/kvm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/arm/kvm.c b/target/arm/kvm.c
> index 70f79eda33cd..b20a35052f41 100644
> --- a/target/arm/kvm.c
> +++ b/target/arm/kvm.c
> @@ -280,6 +280,7 @@ static bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)
> if (kvm_arm_pmu_supported()) {
> init.features[0] |= 1 << KVM_ARM_VCPU_PMU_V3;
> pmu_supported = true;
> + features |= 1ULL << ARM_FEATURE_PMU;
> }
>
> if (!kvm_arm_create_scratch_host_vcpu(cpus_to_try, fdarray, &init)) {
> @@ -448,7 +449,6 @@ static bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)
> features |= 1ULL << ARM_FEATURE_V8;
> features |= 1ULL << ARM_FEATURE_NEON;
> features |= 1ULL << ARM_FEATURE_AARCH64;
> - features |= 1ULL << ARM_FEATURE_PMU;
> features |= 1ULL << ARM_FEATURE_GENERIC_TIMER;
>
> ahcf->features = features;
>
prev parent reply other threads:[~2024-07-16 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 8:28 [PATCH v2 0/5] target/arm/kvm: Report PMU unavailability Akihiko Odaki
2024-07-16 8:28 ` [PATCH v2 1/5] tests/arm-cpu-features: Do not assume PMU availability Akihiko Odaki
2024-07-16 9:16 ` Philippe Mathieu-Daudé
2024-07-16 8:28 ` [PATCH v2 2/5] target/arm: Allow setting 'pmu' only for host and max Akihiko Odaki
2024-07-16 9:36 ` Peter Maydell
2024-07-16 8:28 ` [PATCH v2 3/5] target/arm: Do not allow setting 'pmu' for hvf Akihiko Odaki
2024-07-16 11:28 ` Peter Maydell
2024-07-16 8:28 ` [PATCH v2 4/5] target/arm: Always add pmu property Akihiko Odaki
2024-07-16 9:19 ` Philippe Mathieu-Daudé
2024-07-16 11:32 ` Peter Maydell
2024-07-16 11:36 ` Akihiko Odaki
2024-07-16 12:53 ` Peter Maydell
2024-07-16 8:28 ` [PATCH v2 5/5] target/arm/kvm: Report PMU unavailability Akihiko Odaki
2024-07-16 9:22 ` Philippe Mathieu-Daudé [this message]
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=3ef05b2b-06da-40ca-9344-2d5a8cdd6dba@linaro.org \
--to=philmd@linaro.org \
--cc=ajones@ventanamicro.com \
--cc=akihiko.odaki@daynix.com \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wei@redhat.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).