From: Peter Maydell <peter.maydell@linaro.org>
To: Chen Baozi <chenbaozi@phytium.com.cn>
Cc: qemu-devel@nongnu.org,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v2] target/arm: Add Neoverse-N1 registers
Date: Mon, 6 Mar 2023 15:43:27 +0000 [thread overview]
Message-ID: <CAFEAcA8saKA2zHXpPLHVSB3ya=HFG2ayPZCvD3BUut76NAmQCw@mail.gmail.com> (raw)
In-Reply-To: <20230306151243.3877250-1-chenbaozi@phytium.com.cn>
On Mon, 6 Mar 2023 at 15:12, Chen Baozi <chenbaozi@phytium.com.cn> wrote:
>
> Add implementation defined registers for neoverse-n1 which
> would be accessed by TF-A. Since there is no DSU in Qemu,
> CPUCFR_EL1.SCU bit is set to 1 to avoid DSU registers definition.
>
> Signed-off-by: Chen Baozi <chenbaozi@phytium.com.cn>
> Tested-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
> ---
> target/arm/cpu64.c | 2 ++
> target/arm/cpu_tcg.c | 62 ++++++++++++++++++++++++++++++++++++++++++
> target/arm/internals.h | 2 ++
> 3 files changed, 66 insertions(+)
We should add a comment here:
/*
* Report CPUCFR_EL1.SCU as 1, as we do not implement the DSU
* (and in particular its system registers).
*/
If that's the only issue with this version of the patch
I'll fix it up when I add this into target-arm.next.
> + { .name = "CPUCFR_EL1", .state = ARM_CP_STATE_AA64,
> + .opc0 = 3, .opc1 = 0, .crn = 15, .crm = 0, .opc2 = 0,
> + .access = PL1_R, .type = ARM_CP_CONST, .resetvalue = 4 },
thanks
-- PMM
prev parent reply other threads:[~2023-03-06 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:12 [PATCH v2] target/arm: Add Neoverse-N1 registers Chen Baozi
2023-03-06 15:37 ` Peter Maydell
2023-03-06 17:13 ` Marcin Juszkiewicz
2023-03-06 17:29 ` Marcin Juszkiewicz
2023-03-06 15:43 ` Peter Maydell [this message]
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='CAFEAcA8saKA2zHXpPLHVSB3ya=HFG2ayPZCvD3BUut76NAmQCw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=chenbaozi@phytium.com.cn \
--cc=marcin.juszkiewicz@linaro.org \
--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).