From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peng Liang <liangpeng10@huawei.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, drjones@redhat.com,
zhang.zhanghailiang@huawei.com, mst@redhat.com,
cohuck@redhat.com, xiexiangyou@huawei.com, pbonzini@redhat.com
Subject: Re: [RFC 1/9] target/arm: convert isar regs to array
Date: Thu, 13 Aug 2020 12:42:24 +0200 [thread overview]
Message-ID: <6151cd0a-b3ff-ae68-e843-c6b294b846a8@redhat.com> (raw)
In-Reply-To: <20200813102657.2588720-2-liangpeng10@huawei.com>
On 8/13/20 12:26 PM, Peng Liang wrote:
> The isar in ARMCPU is a struct, each field of which represents an ID
> register. It's not convenient for us to support CPU feature in AArch64.
> So let's change it to an array first and add an enum as the index of the
> array for convenience. Since we will never access high 32-bits of ID
> registers in AArch32, it's harmless to change the ID registers in
> AArch32 to 64-bits.
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> Signed-off-by: Peng Liang <liangpeng10@huawei.com>
> ---
> hw/intc/armv7m_nvic.c | 48 ++++----
> target/arm/cpu.c | 232 +++++++++++++++++++-------------------
> target/arm/cpu.h | 226 +++++++++++++++++++------------------
> target/arm/cpu64.c | 170 ++++++++++++++--------------
> target/arm/cpu_tcg.c | 250 +++++++++++++++++++++--------------------
> target/arm/helper.c | 54 ++++-----
> target/arm/internals.h | 15 +--
> target/arm/kvm64.c | 72 ++++++------
> 8 files changed, 541 insertions(+), 526 deletions(-)
Please consider using scripts/git.orderfile.
[...]
> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
> index 9e8ed423ea..5d8074d03b 100644
> --- a/target/arm/cpu.h
> +++ b/target/arm/cpu.h
> @@ -67,6 +67,37 @@
> #define ARMV7M_EXCP_PENDSV 14
> #define ARMV7M_EXCP_SYSTICK 15
>
> +typedef enum CPUIDReg {
> + MIDR_EL1,
> + ID_ISAR0,
> + ID_ISAR1,
> + ID_ISAR2,
> + ID_ISAR3,
> + ID_ISAR4,
> + ID_ISAR5,
> + ID_ISAR6,
> + ID_MMFR0,
> + ID_MMFR1,
> + ID_MMFR2,
> + ID_MMFR3,
> + ID_MMFR4,
> + ID_AA64ISAR0,
> + ID_AA64ISAR1,
> + ID_AA64PFR0,
> + ID_AA64PFR1,
> + ID_AA64MMFR0,
> + ID_AA64MMFR1,
> + ID_AA64MMFR2,
> + ID_AA64DFR0,
> + ID_AA64DFR1,
> + ID_DFR0,
> + MVFR0,
> + MVFR1,
> + MVFR2,
> + DBGDIDR,
> + ID_MAX,
(nitpicking, drop the last comma).
> +} CPUIDReg;
> +
> /* For M profile, some registers are banked secure vs non-secure;
> * these are represented as a 2-element array where the first element
> * is the non-secure copy and the second is the secure copy.
> @@ -890,32 +921,7 @@ struct ARMCPU {
> * field by reading the value from the KVM vCPU.
> */
> struct ARMISARegisters {
> - uint32_t id_isar0;
> - uint32_t id_isar1;
> - uint32_t id_isar2;
> - uint32_t id_isar3;
> - uint32_t id_isar4;
> - uint32_t id_isar5;
> - uint32_t id_isar6;
> - uint32_t id_mmfr0;
> - uint32_t id_mmfr1;
> - uint32_t id_mmfr2;
> - uint32_t id_mmfr3;
> - uint32_t id_mmfr4;
> - uint32_t mvfr0;
> - uint32_t mvfr1;
> - uint32_t mvfr2;
> - uint32_t id_dfr0;
> - uint32_t dbgdidr;
> - uint64_t id_aa64isar0;
> - uint64_t id_aa64isar1;
> - uint64_t id_aa64pfr0;
> - uint64_t id_aa64pfr1;
> - uint64_t id_aa64mmfr0;
> - uint64_t id_aa64mmfr1;
> - uint64_t id_aa64mmfr2;
> - uint64_t id_aa64dfr0;
> - uint64_t id_aa64dfr1;
> + uint64_t regs[ID_MAX];
> } isar;
Why not simply this?
uint64_t isar[ID_MAX];
> uint64_t midr;
> uint32_t revidr;
[...]
next prev parent reply other threads:[~2020-08-13 10:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 10:26 [RFC 0/9] Support disable/enable CPU features for AArch64 Peng Liang
2020-08-13 10:26 ` [RFC 1/9] target/arm: convert isar regs to array Peng Liang
2020-08-13 10:42 ` Philippe Mathieu-Daudé [this message]
2020-08-13 16:11 ` Richard Henderson
2020-08-13 10:26 ` [RFC 2/9] target/arm: parse cpu feature related options Peng Liang
2020-08-13 12:21 ` Andrew Jones
2020-08-15 2:19 ` Peng Liang
2020-08-15 6:51 ` Andrew Jones
2020-08-13 10:26 ` [RFC 3/9] target/arm: register CPU features for property Peng Liang
2020-08-13 12:34 ` Andrew Jones
2020-08-13 10:26 ` [RFC 4/9] target/arm: Allow ID registers to synchronize to KVM Peng Liang
2020-08-13 10:26 ` [RFC 5/9] target/arm: introduce CPU feature dependency mechanism Peng Liang
2020-08-13 12:48 ` Andrew Jones
2020-08-15 2:19 ` Peng Liang
2020-08-15 6:59 ` Andrew Jones
2020-08-13 10:26 ` [RFC 6/9] target/arm: introduce KVM_CAP_ARM_CPU_FEATURE Peng Liang
2020-08-13 11:00 ` Cornelia Huck
2020-08-15 2:19 ` Peng Liang
2020-08-13 10:26 ` [RFC 7/9] target/arm: Add CPU features to query-cpu-model-expansion Peng Liang
2020-08-13 12:56 ` Andrew Jones
2020-08-15 2:19 ` Peng Liang
2020-08-15 7:02 ` Andrew Jones
2020-08-13 10:26 ` [RFC 8/9] target/arm: Update ID fields Peng Liang
2020-08-13 10:26 ` [RFC 9/9] target/arm: Add more CPU features Peng Liang
2020-08-13 14:10 ` [RFC 0/9] Support disable/enable CPU features for AArch64 Andrew Jones
2020-08-13 16:30 ` no-reply
2020-08-13 16:34 ` no-reply
2020-08-13 16:38 ` no-reply
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=6151cd0a-b3ff-ae68-e843-c6b294b846a8@redhat.com \
--to=philmd@redhat.com \
--cc=cohuck@redhat.com \
--cc=drjones@redhat.com \
--cc=liangpeng10@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.com \
--cc=zhang.zhanghailiang@huawei.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).