From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>,
Amanieu d'Antras <amanieu@gmail.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v2] target/arm: Allow user-mode code to write CPSR.E via MSR
Date: Tue, 19 May 2020 08:01:21 -0700 [thread overview]
Message-ID: <dd4cbf09-8f6d-8034-661b-ffa4195e56d7@linaro.org> (raw)
In-Reply-To: <20200518142801.20503-1-peter.maydell@linaro.org>
On 5/18/20 7:28 AM, Peter Maydell wrote:
> Using the MSR instruction to write to CPSR.E is deprecated, but it is
> required to work from any mode including unprivileged code. We were
> incorrectly forbidding usermode code from writing it because
> CPSR_USER did not include the CPSR_E bit.
>
> We use CPSR_USER in only three places:
> * as the mask of what to allow userspace MSR to write to CPSR
> * when deciding what bits a linux-user signal-return should be
> able to write from the sigcontext structure
> * in target_user_copy_regs() when we set up the initial
> registers for the linux-user process
>
> In the first two cases not being able to update CPSR.E is a bug, and
> in the third case it doesn't matter because CPSR.E is always 0 there.
> So we can fix both bugs by adding CPSR_E to CPSR_USER.
>
> Because the cpsr_write() in restore_sigcontext() is now changing
> a CPSR bit which is cached in hflags, we need to add an
> arm_rebuild_hflags() call there; the callsite in
> target_user_copy_regs() was already rebuilding hflags for other
> reasons.
>
> (The recommended way to change CPSR.E is to use the 'SETEND'
> instruction, which we do correctly allow from usermode code.)
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> v2 changes:
> * fixed wrong variable name in commit message
> * added arm_rebuild_hflags() call in restore_sigcontext()
> ---
> target/arm/cpu.h | 2 +-
> linux-user/arm/signal.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2020-05-19 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 14:28 [PATCH v2] target/arm: Allow user-mode code to write CPSR.E via MSR Peter Maydell
2020-05-19 15:01 ` Richard Henderson [this message]
2020-05-21 17:04 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-10-12 15:33 [PATCH 00/10] target/arm: Various v8.1M minor features Peter Maydell
2020-10-12 15:33 ` [PATCH v2] target/arm: Allow user-mode code to write CPSR.E via MSR 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=dd4cbf09-8f6d-8034-661b-ffa4195e56d7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=amanieu@gmail.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).