From: Peter Maydell <peter.maydell@linaro.org>
To: Zhuojia Shen <chaosdefinition@hotmail.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH] target/arm: align exposed ID registers with Linux
Date: Tue, 22 Nov 2022 18:26:48 +0000 [thread overview]
Message-ID: <CAFEAcA85sSz3bvAvz6XLqa4TxBSgYWRG-oXTCr7Q4tNYRk+GEw@mail.gmail.com> (raw)
In-Reply-To: <DS7PR12MB6309CF26249A273C1E2A6AAAAC0D9@DS7PR12MB6309.namprd12.prod.outlook.com>
On Tue, 22 Nov 2022 at 03:05, Zhuojia Shen <chaosdefinition@hotmail.com> wrote:
>
> In CPUID registers exposed to userspace, some registers were missing
> and some fields were not exposed. This patch aligns exposed ID
> registers and their fields with what Linux exposes currently.
>
> Specifically, the following new ID registers/fields are exposed to
> userspace:
These changes don't quite seem to line up with what the kernel
documents that it exposes:
https://www.kernel.org/doc/Documentation/arm64/cpu-feature-registers.rst
> ID_AA64PFR1_EL1.BT: bits 3-0
> ID_AA64PFR1_EL1.MTE: bits 11-8
> ID_AA64PFR1_EL1.SME: bits 27-24
.SME not listed as exposed.
> ID_AA64SMFR0_EL1.F32F32: bit 32
> ID_AA64SMFR0_EL1.B16F32: bit 34
> ID_AA64SMFR0_EL1.F16F32: bit 35
> ID_AA64SMFR0_EL1.I8I32: bits 39-36
> ID_AA64SMFR0_EL1.F64F64: bit 48
> ID_AA64SMFR0_EL1.I16I64: bits 55-52
> ID_AA64SMFR0_EL1.FA64: bit 63
This register not listed as exposed.
> ID_AA64ISAR2_EL1.WFxT: bits 3-0
> ID_AA64ISAR2_EL1.RPRES: bits 7-4
> ID_AA64ISAR2_EL1.GPA3: bits 11-8
> ID_AA64ISAR2_EL1.APA3: bits 15-12
GPA3 and APA3 not listed as exposed.
thanks
-- PMM
next prev parent reply other threads:[~2022-11-22 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 2:48 [PATCH] target/arm: align exposed ID registers with Linux Zhuojia Shen
2022-11-22 18:12 ` Richard Henderson
2022-11-22 18:53 ` Zhuojia Shen
2022-11-22 18:26 ` Peter Maydell [this message]
2022-11-22 18:46 ` Zhuojia Shen
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=CAFEAcA85sSz3bvAvz6XLqa4TxBSgYWRG-oXTCr7Q4tNYRk+GEw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=chaosdefinition@hotmail.com \
--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).