From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v4 1/8] target/arm: Move some system registers into a substructure
Date: Fri, 19 Oct 2018 08:28:53 -0700 [thread overview]
Message-ID: <cee4bb3c-e735-245c-9e5a-f78e13ef3a89@linaro.org> (raw)
In-Reply-To: <6e1ea3f2-24c9-58a7-2f13-0b835b4180cb@redhat.com>
On 10/19/18 5:04 AM, Philippe Mathieu-Daudé wrote:
> Hi Richard,
>
> On 17/10/2018 00:31, Richard Henderson wrote:
>> Create struct ARMISARegisters, to be accessed during translation.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> target/arm/cpu.h | 32 ++++----
>> hw/intc/armv7m_nvic.c | 12 +--
>> target/arm/cpu.c | 178 +++++++++++++++++++++---------------------
>> target/arm/cpu64.c | 70 ++++++++---------
>> target/arm/helper.c | 28 +++----
>> 5 files changed, 162 insertions(+), 158 deletions(-)
>>
>> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
>> index f00c0444c4..cff739b74d 100644
>> --- a/target/arm/cpu.h
>> +++ b/target/arm/cpu.h
>> @@ -788,13 +788,28 @@ struct ARMCPU {
>> * ARMv7AR ARM Architecture Reference Manual. A reset_ prefix
>> * is used for reset values of non-constant registers; no reset_
>> * prefix means a constant register.
>> + * Some of these registers are split out into a substructure that
>> + * is shared with the translators to control the ISA.
>> */
>> + 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 mvfr0;
>> + uint32_t mvfr1;
>> + uint32_t mvfr2;
>> + uint64_t id_aa64isar0;
>> + uint64_t id_aa64isar1;
>> + uint64_t id_aa64pfr0;
>> + uint64_t id_aa64pfr1;
>> + } isar;
>
> I understand and agree with the change, however I find the 'isar' name
> confusing. Sadly unnamed structure is not useful here.
I assume the naming of these registers has some history within ARM, but I find
the distribution of fields between "ISA Registers" and "Processor Feature
Registers" and "Media & VFP Feature Registers" confusing, since they all have
much the same function.
I struggled with the naming myself, but couldn't find anything better than "ISA
Registers" myself. Which they all are, really, despite the other two names.
r~
next prev parent reply other threads:[~2018-10-19 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 22:31 [Qemu-devel] [PATCH v4 0/8] target/arm: Rely on id regs instead of features Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 1/8] target/arm: Move some system registers into a substructure Richard Henderson
2018-10-19 12:04 ` Philippe Mathieu-Daudé
2018-10-19 15:28 ` Richard Henderson [this message]
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 2/8] target/arm: V8M should not imply V7VE Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 3/8] target/arm: Convert v8 extensions from feature bits to isar tests Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 4/8] target/arm: Convert division from feature bits to isar0 tests Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 5/8] target/arm: Convert jazelle from feature bit to isar1 test Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 6/8] target/arm: Convert t32ee from feature bit to isar3 test Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 7/8] target/arm: Convert sve from feature bit to aa64pfr0 test Richard Henderson
2018-10-16 22:31 ` [Qemu-devel] [PATCH v4 8/8] target/arm: Convert v8.2-fp16 " Richard Henderson
2018-10-19 10:38 ` [Qemu-devel] [PATCH v4 0/8] target/arm: Rely on id regs instead of features 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=cee4bb3c-e735-245c-9e5a-f78e13ef3a89@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).