From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 1/4] target-arm: Add missing MAIR_EL3 and TPIDR_EL3 registers
Date: Sun, 16 Aug 2015 23:54:02 +0200 [thread overview]
Message-ID: <20150816215402.GA16713@toto> (raw)
In-Reply-To: <1438281398-18746-2-git-send-email-peter.maydell@linaro.org>
On Thu, Jul 30, 2015 at 07:36:35PM +0100, Peter Maydell wrote:
> Add the AArch64 registers MAIR_EL3 and TPIDR_EL3, which are the only
> two which we had implemented the 32-bit Secure equivalents of but
> not the 64-bit Secure versions.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> target-arm/helper.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/target-arm/helper.c b/target-arm/helper.c
> index 01f0d0d..d59616e 100644
> --- a/target-arm/helper.c
> +++ b/target-arm/helper.c
> @@ -1022,6 +1022,10 @@ static const ARMCPRegInfo v7_cp_reginfo[] = {
> .opc0 = 3, .opc1 = 0, .crn = 10, .crm = 2, .opc2 = 0,
> .access = PL1_RW, .fieldoffset = offsetof(CPUARMState, cp15.mair_el[1]),
> .resetvalue = 0 },
> + { .name = "MAIR_EL3", .state = ARM_CP_STATE_AA64,
> + .opc0 = 3, .opc1 = 6, .crn = 10, .crm = 2, .opc2 = 0,
> + .access = PL3_RW, .fieldoffset = offsetof(CPUARMState, cp15.mair_el[3]),
> + .resetvalue = 0 },
> /* For non-long-descriptor page tables these are PRRR and NMRR;
> * regardless they still act as reads-as-written for QEMU.
> */
> @@ -2790,6 +2794,10 @@ static const ARMCPRegInfo el3_cp_reginfo[] = {
> .opc0 = 3, .opc1 = 6, .crn = 1, .crm = 1, .opc2 = 2,
> .access = PL3_RW, .accessfn = cptr_access, .resetvalue = 0,
> .fieldoffset = offsetof(CPUARMState, cp15.cptr_el[3]) },
> + { .name = "TPIDR_EL3", .state = ARM_CP_STATE_AA64,
> + .opc0 = 3, .opc1 = 6, .crn = 13, .crm = 0, .opc2 = 2,
> + .access = PL3_RW, .resetvalue = 0,
> + .fieldoffset = offsetof(CPUARMState, cp15.tpidr_el[3]) },
> REGINFO_SENTINEL
> };
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-08-16 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 18:36 [Qemu-devel] [PATCH 0/4] target-arm: Implement missing EL3 (and EL2) registers Peter Maydell
2015-07-30 18:36 ` [Qemu-devel] [PATCH 1/4] target-arm: Add missing MAIR_EL3 and TPIDR_EL3 registers Peter Maydell
2015-08-16 21:54 ` Edgar E. Iglesias [this message]
2015-07-30 18:36 ` [Qemu-devel] [PATCH 2/4] target-arm: Implement missing AMAIR registers Peter Maydell
2015-08-16 22:02 ` Edgar E. Iglesias
2015-07-30 18:36 ` [Qemu-devel] [PATCH 3/4] target-arm: Implement missing AFSR registers Peter Maydell
2015-08-16 22:05 ` Edgar E. Iglesias
2015-07-30 18:36 ` [Qemu-devel] [PATCH 4/4] target-arm: Implement missing ACTLR registers Peter Maydell
2015-08-16 22:09 ` Edgar E. Iglesias
2015-08-14 10:12 ` [Qemu-devel] [PATCH 0/4] target-arm: Implement missing EL3 (and EL2) registers Peter Maydell
2015-08-14 17:42 ` Edgar E. Iglesias
2015-08-14 17:48 ` Peter Maydell
2015-08-14 17:55 ` Edgar E. Iglesias
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=20150816215402.GA16713@toto \
--to=edgar.iglesias@gmail.com \
--cc=patches@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).