From: Gavin Shan <gshan@redhat.com>
To: qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, richard.henderson@linaro.org,
qemu-devel@nongnu.org, marcin.juszkiewicz@linaro.org,
shan.gavin@gmail.com, pbonzini@redhat.com
Subject: [PATCH 2/2] target/arm: Initlaize PMU feature for scratch vcpu
Date: Wed, 7 Apr 2021 12:01:00 +0800 [thread overview]
Message-ID: <20210407040100.9933-2-gshan@redhat.com> (raw)
In-Reply-To: <20210407040100.9933-1-gshan@redhat.com>
If the scratch vCPU is initialized without PMU feature, we receive
error on reading PMCR_EL0 as it's invisible in this case. It leads
to host probing failure.
This fixes the issue by initializing the scratch vcpu with the PMU
feature enabled and reading PMCR_EL0 from host. Otherwise, its value
is set according to the detected target.
Fixes: f7fb73b8cdd3 ("target/arm: Make number of counters in PMCR follow the CPU")
Signed-off-by: Gavin Shan <gshan@redhat.com>
---
target/arm/kvm64.c | 32 +++++++++++++++++++++++++++-----
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/target/arm/kvm64.c b/target/arm/kvm64.c
index 79800f00a7..7311e86d1d 100644
--- a/target/arm/kvm64.c
+++ b/target/arm/kvm64.c
@@ -516,11 +516,14 @@ bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)
QEMU_KVM_ARM_TARGET_NONE
};
struct kvm_vcpu_init init = {
- .features[0] = 0;
+ .features[0] = (1 << KVM_ARM_VCPU_PMU_V3),
};
- if (!kvm_arm_create_scratch_host_vcpu(cpus_to_try, fdarray, &init)) {
- return false;
+ if (!kvm_arm_create_scratch_host_vcpu(NULL, fdarray, &init)) {
+ init.features[0] = 0;
+ if (!kvm_arm_create_scratch_host_vcpu(cpus_to_try, fdarray, &init)) {
+ return false;
+ }
}
ahcf->target = init.target;
@@ -564,8 +567,27 @@ bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)
ARM64_SYS_REG(3, 0, 0, 7, 1));
err |= read_sys_reg64(fdarray[2], &ahcf->isar.id_aa64mmfr2,
ARM64_SYS_REG(3, 0, 0, 7, 2));
- err |= read_sys_reg64(fdarray[2], &ahcf->isar.reset_pmcr_el0,
- ARM64_SYS_REG(3, 3, 9, 12, 0));
+
+ /*
+ * Read PMCR_EL0 from host if PMU feature has been enabled
+ * successfully. Otherwise, the value is set according to
+ * the detected target.
+ */
+ if (init.features[0] & (1 << KVM_ARM_VCPU_PMU_V3)) {
+ err |= read_sys_reg64(fdarray[2], &ahcf->isar.reset_pmcr_el0,
+ ARM64_SYS_REG(3, 3, 9, 12, 0));
+ } else {
+ switch (init.target) {
+ case KVM_ARM_TARGET_CORTEX_A53:
+ ahcf->isar.reset_pmcr_el0 = 0x41033000;
+ break;
+ case KVM_ARM_TARGET_CORTEX_A57:
+ ahcf->isar.reset_pmcr_el0 = 0x41013000;
+ break;
+ default:
+ ahcf->isar.reset_pmcr_el0 = 0x41023000;
+ }
+ }
/*
* Note that if AArch32 support is not present in the host,
--
2.23.0
next prev parent reply other threads:[~2021-04-07 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 4:00 [PATCH 1/2] target/arm: Needn't validate the target in scratch host Gavin Shan
2021-04-07 4:01 ` Gavin Shan [this message]
2021-04-07 7:38 ` [PATCH 2/2] target/arm: Initlaize PMU feature for scratch vcpu Peter Maydell
2021-04-12 4:11 ` Gavin Shan
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=20210407040100.9933-2-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@gmail.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).