From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] target/arm: Fix Rt/Rt2 in ESR_ELx for copro traps from AArch32 to 64
Date: Wed, 5 Aug 2020 10:34:35 +0100 [thread overview]
Message-ID: <CAFEAcA_HPkO7w7LJH1GoqPGPy-7hLUcCmZpDBjLzDcKUCmpaVQ@mail.gmail.com> (raw)
In-Reply-To: <6b9b926a-0a46-1660-9a85-bae29cd56cf9@linaro.org>
On Tue, 4 Aug 2020 at 21:38, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 8/3/20 9:54 AM, Peter Maydell wrote:
> > + case 14:
> > + switch (mode) {
> > + case ARM_CPU_MODE_USR:
> > + case ARM_CPU_MODE_SYS:
> > + return 14;
> > + case ARM_CPU_MODE_HYP:
> > + return 16;
>
> Hyp uses LR_usr...
>
> > + case ARM_CPU_MODE_IRQ:
> > + return 18;
> > + case ARM_CPU_MODE_SVC:
> > + return 20;
> > + case ARM_CPU_MODE_ABT:
> > + return 22;
> > + case ARM_CPU_MODE_UND:
> > + return 24;
>
> ... making all of these off-by-2.
Yeah, this is the bug fixed in v2.
> > + case ARM_CPU_MODE_FIQ:
> > + return 30;
> > + default:
> > + g_assert_not_reached();
> > + }
> > + case 15:
> > + return 31;
>
> I don't see that R15 is mapped at all. Is this really reachable?
It is -- you can get Rt=0b1111 for MRC to APSR_nzcv (as well
as for various UNPREDICTABLE MCR etc cases that will get trapped
here that we have to do something sensible for). Rt=0b1111
is mapped to 0b11111 in the pseudocode (see
AArch64.AArch32SystemAccessTrapSyndrome()); it's just not
documented in the text (yet) that this is the required behaviour.
thanks
-- PMM
prev parent reply other threads:[~2020-08-05 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 16:54 [PATCH] target/arm: Fix Rt/Rt2 in ESR_ELx for copro traps from AArch32 to 64 Peter Maydell
2020-08-04 20:38 ` Richard Henderson
2020-08-05 9:34 ` 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=CAFEAcA_HPkO7w7LJH1GoqPGPy-7hLUcCmZpDBjLzDcKUCmpaVQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).