qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: [Qemu-devel] [PATCH 1/6] target/arm: Implement ID_PFR2
Date: Fri, 22 Feb 2019 18:39:52 -0800	[thread overview]
Message-ID: <20190223023957.18865-2-richard.henderson@linaro.org> (raw)
In-Reply-To: <20190223023957.18865-1-richard.henderson@linaro.org>

This was defined at some point before ARMv8.4, and will
shortly be used by new processor descriptions.

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
---
 target/arm/cpu.h    | 1 +
 target/arm/helper.c | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 84ae6849c2..c57f8e9ba8 100644
--- a/target/arm/cpu.h
+++ b/target/arm/cpu.h
@@ -863,6 +863,7 @@ struct ARMCPU {
     uint32_t reset_sctlr;
     uint32_t id_pfr0;
     uint32_t id_pfr1;
+    uint32_t id_pfr2;
     uint32_t id_dfr0;
     uint64_t pmceid0;
     uint64_t pmceid1;
diff --git a/target/arm/helper.c b/target/arm/helper.c
index a018eb23fe..8903cc13d8 100644
--- a/target/arm/helper.c
+++ b/target/arm/helper.c
@@ -6092,10 +6092,10 @@ void register_cp_regs_for_features(ARMCPU *cpu)
               .opc0 = 3, .opc1 = 0, .crn = 0, .crm = 3, .opc2 = 3,
               .access = PL1_R, .type = ARM_CP_CONST,
               .resetvalue = 0 },
-            { .name = "MVFR4_EL1_RESERVED", .state = ARM_CP_STATE_AA64,
+            { .name = "ID_PFR2", .state = ARM_CP_STATE_BOTH,
               .opc0 = 3, .opc1 = 0, .crn = 0, .crm = 3, .opc2 = 4,
               .access = PL1_R, .type = ARM_CP_CONST,
-              .resetvalue = 0 },
+              .resetvalue = cpu->id_pfr2 },
             { .name = "MVFR5_EL1_RESERVED", .state = ARM_CP_STATE_AA64,
               .opc0 = 3, .opc1 = 0, .crn = 0, .crm = 3, .opc2 = 5,
               .access = PL1_R, .type = ARM_CP_CONST,
-- 
2.17.2

  reply	other threads:[~2019-02-23  2:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23  2:39 [Qemu-devel] [PATCH+RFC 0/6] target/arm: Define cortex-a{73, 75, 76} Richard Henderson
2019-02-23  2:39 ` Richard Henderson [this message]
2019-04-30 12:13   ` [Qemu-devel] [PATCH 1/6] target/arm: Implement ID_PFR2 Peter Maydell
2019-04-30 12:13     ` Peter Maydell
2019-02-23  2:39 ` [Qemu-devel] [PATCH 2/6] target/arm: Define cortex-a73 Richard Henderson
2019-04-30 12:23   ` Peter Maydell
2019-04-30 12:23     ` Peter Maydell
2019-02-23  2:39 ` [Qemu-devel] [PATCH 3/6] target/arm: Implement ID_AA64MMFR2 Richard Henderson
2019-04-30 12:25   ` Peter Maydell
2019-04-30 12:25     ` Peter Maydell
2019-02-23  2:39 ` [Qemu-devel] [RFC 4/6] target/arm: Define cortex-a75 Richard Henderson
2019-04-30 12:52   ` Peter Maydell
2019-04-30 12:52     ` Peter Maydell
2019-02-23  2:39 ` [Qemu-devel] [RFC 5/6] target/arm: Conditionalize DBGDIDR vs ID_AA64DFR0_EL1 assert Richard Henderson
2019-04-30 12:40   ` Peter Maydell
2019-04-30 12:40     ` Peter Maydell
2019-02-23  2:39 ` [Qemu-devel] [RFC 6/6] target/arm: Define cortex-a76 Richard Henderson
2019-04-30 12:57 ` [Qemu-devel] [PATCH+RFC 0/6] target/arm: Define cortex-a{73, 75, 76} Peter Maydell
2019-04-30 12:57   ` 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=20190223023957.18865-2-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.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).