From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Shuuichirou Ishii" <ishii.shuuichir@fujitsu.com>,
"Itaru Kitayama" <itaru.kitayama@gmail.com>
Subject: Re: [PATCH] target/arm: Make number of counters in PMCR follow the CPU
Date: Fri, 13 May 2022 08:47:37 -0700 [thread overview]
Message-ID: <51639c5c-9092-c4a2-c215-2cbdf110d347@linaro.org> (raw)
In-Reply-To: <20220513122852.4063586-1-peter.maydell@linaro.org>
On 5/13/22 05:28, Peter Maydell wrote:
> Currently we give all the v7-and-up CPUs a PMU with 4 counters. This
> means that we don't provide the 6 counters that are required by the
> Arm BSA (Base System Architecture) specification if the CPU supports
> the Virtualization extensions.
>
> Instead of having a single PMCR_NUM_COUNTERS, make each CPU type
> specify the PMCR reset value (obtained from the appropriate TRM), and
> use the 'N' field of that value to define the number of counters
> provided.
>
> This means that we now supply 6 counters instead of 4 for:
> Cortex-A9, Cortex-A15, Cortex-A53, Cortex-A57, Cortex-A72,
> Cortex-A76, Neoverse-N1, '-cpu max'
> These CPUs remain with 4 counters:
> Cortex-A7, Cortex-A8
> This CPU goes down from 4 to 3 counters:
> Cortex-R5
>
> TODO: A64FX -- I don't know the correct PMCR_EL0 reset value.
>
> Note that because we now use the PMCR reset value of the specific
> implementation, we no longer set the LC bit out of reset. This has
> an UNKNOWN value out of reset for all cores with any AArch32 support,
> so guest software should be setting it anyway if it wants it.
>
> This change was originally landed in commit f7fb73b8cdd3f7 (during
> the 6.0 release cycle) but was then reverted by commit
> 21c2dd77a6aa517 before that release because it did not work with KVM.
> This version fixes that by creating the scratch vCPU in
> kvm_arm_get_host_cpu_features() with the KVM_ARM_VCPU_PMU_V3 feature
> if KVM supports it, and then only asking KVM for the PMCR_EL0 value
> if the vCPU has a PMU.
>
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
> I'd forgotten that we'd dropped this fix in the 6.0 timeframe
> and never picked it back up again until Alex reminded me of it...
>
> Changes since original attempt:
> -- rebased
> -- fix the code in kvm_arm_get_host_cpu_features() that reads PMCR_EL0
> -- set PMCR value for new CPUs cortex-a76, neoverse-n1
> -- set PMCR value for now-separated-out aarch32 -cpu max
> -- TODO comment for a64fx
>
> Shuuichirou, Itaru: this is another patch where we need to know
> an A64FX register value...
> ---
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-05-13 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 12:28 [PATCH] target/arm: Make number of counters in PMCR follow the CPU Peter Maydell
2022-05-13 15:47 ` Richard Henderson [this message]
2022-05-17 23:24 ` ishii.shuuichir
2022-05-18 10:30 ` Peter Maydell
2022-05-18 23:33 ` ishii.shuuichir
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 16:59 Peter Maydell
2021-03-19 10:39 ` Peter Maydell
2021-03-19 10:54 ` Marcin Juszkiewicz
2021-03-26 14:19 ` Richard Henderson
2021-03-31 8:59 ` Zenghui Yu
2021-03-31 9:43 ` Peter Maydell
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=51639c5c-9092-c4a2-c215-2cbdf110d347@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=ishii.shuuichir@fujitsu.com \
--cc=itaru.kitayama@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).