From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: 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,
Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: [PATCH 2/3] target/arm: Always add pmu property
Date: Sat, 29 Jun 2024 21:50:33 +0900 [thread overview]
Message-ID: <20240629-pmu-v1-2-7269123b88a4@daynix.com> (raw)
In-Reply-To: <20240629-pmu-v1-0-7269123b88a4@daynix.com>
kvm-steal-time and sve properties are added for KVM even if the
corresponding features are not available. Always add pmu property too.
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
---
target/arm/cpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/arm/cpu.c b/target/arm/cpu.c
index 35fa281f1b98..0da72c12a5bd 100644
--- a/target/arm/cpu.c
+++ b/target/arm/cpu.c
@@ -1770,9 +1770,10 @@ void arm_cpu_post_init(Object *obj)
if (arm_feature(&cpu->env, ARM_FEATURE_PMU)) {
cpu->has_pmu = true;
- object_property_add_bool(obj, "pmu", arm_get_pmu, arm_set_pmu);
}
+ object_property_add_bool(obj, "pmu", arm_get_pmu, arm_set_pmu);
+
/*
* Allow user to turn off VFP and Neon support, but only for TCG --
* KVM does not currently allow us to lie to the guest about its
--
2.45.2
next prev parent reply other threads:[~2024-06-29 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 12:50 [PATCH 0/3] target/arm/kvm: Report PMU unavailability Akihiko Odaki
2024-06-29 12:50 ` [PATCH 1/3] tests/arm-cpu-features: Do not assume PMU availability Akihiko Odaki
2024-06-29 12:50 ` Akihiko Odaki [this message]
2024-07-01 11:54 ` [PATCH 2/3] target/arm: Always add pmu property Peter Maydell
2024-07-01 12:16 ` Akihiko Odaki
2024-07-01 13:32 ` Peter Maydell
2024-06-29 12:50 ` [PATCH 3/3] target/arm/kvm: Report PMU unavailability Akihiko Odaki
2024-06-29 17:27 ` [PATCH 0/3] " Richard Henderson
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=20240629-pmu-v1-2-7269123b88a4@daynix.com \
--to=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 \
/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).