From: Richard Henderson <richard.henderson@linaro.org>
To: Rebecca Cran <rebecca@nuviainc.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v4 2/4] target/arm: Support AA32 DIT by moving PSTATE_SS from cpsr into env->pstate
Date: Wed, 3 Feb 2021 10:36:26 -1000 [thread overview]
Message-ID: <8c5b4424-f8d2-faf5-414a-4b752135bd5d@linaro.org> (raw)
In-Reply-To: <67c1c588-1210-da0e-24c2-49bb77c1d217@nuviainc.com>
On 2/3/21 10:28 AM, Rebecca Cran wrote:
> On 2/3/21 10:17 AM, Richard Henderson wrote:
>> On 2/2/21 6:58 PM, Rebecca Cran wrote:
>>> if (!arm_singlestep_active(env)) {
>>> - env->uncached_cpsr &= ~PSTATE_SS;
>>> + env->pstate &= ~PSTATE_SS;
>>> + } else {
>>> + env->pstate |= PSTATE_SS;
>>> }
>>
>> Where did this addition come from?
>
> I thought this was needed given your comment:
>
> "This is missing the restore of PSTATE_SS for when singlestep *is* active."
No, that was this:
> + /* Save SPSR_ELx.SS into PSTATE. */
> + env->pstate = (env->pstate & ~PSTATE_SS) | (val & PSTATE_SS);
> + val &= ~PSTATE_SS;
which is a restore, not an unconditional enable as you do above.
r~
next prev parent reply other threads:[~2021-02-03 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 4:58 [PATCH v4 0/4] target/arm: Add support for FEAT_DIT, Data Independent Timing Rebecca Cran
2021-02-03 4:58 ` [PATCH v4 1/4] " Rebecca Cran
2021-02-03 4:58 ` [PATCH v4 2/4] target/arm: Support AA32 DIT by moving PSTATE_SS from cpsr into env->pstate Rebecca Cran
2021-02-03 17:17 ` Richard Henderson
2021-02-03 20:28 ` Rebecca Cran
2021-02-03 20:36 ` Richard Henderson [this message]
2021-02-03 17:19 ` Richard Henderson
2021-02-08 6:50 ` Rebecca Cran
2021-02-03 4:58 ` [PATCH v4 3/4] target/arm: Set ID_AA64PFR0.DIT and ID_PFR0.DIT to 1 for "max" AA64 CPU Rebecca Cran
2021-02-03 4:58 ` [PATCH v4 4/4] target/arm: Set ID_PFR0.DIT to 1 for "max" 32-bit CPU Rebecca Cran
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=8c5b4424-f8d2-faf5-414a-4b752135bd5d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rebecca@nuviainc.com \
/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).