From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, qemu-arm@nongnu.org, Dave.Martin@arm.com
Subject: [Qemu-devel] [PATCH v6 0/6] linux-user/aarch64: Support PROT_BTI
Date: Wed, 5 Jun 2019 15:57:00 -0500 [thread overview]
Message-ID: <20190605205706.569-1-richard.henderson@linaro.org> (raw)
Dave Martin has recently posted a kernel patch set for
supporting ARMv8.5 Branch Target Identification in userland.
http://lists.infradead.org/pipermail/linux-arm-kernel/2019-May/654654.html
While that support is not yet in the upstream kernel, it looks
to be close to its final form. Note that the patch set spells
this PROT_BTI_GUARDED, but review suggested to rename to PROT_BTI.
Changes since v5:
* New function to validate the target PROT parameter for mmap/mprotect.
* Require BTI in the cpu for PROT_BTI set.
* Set PSTATE.BTYPE=2 for the signal handler.
Adjust the smoke test to match.
* Tidy up the note parsing.
r~
Richard Henderson (6):
linux-user/aarch64: Reset btype for syscalls and signals
linux-user: Validate mmap/mprotect prot value
linux-user: Set PAGE_TARGET_1 for TARGET_PROT_BTI
include/elf: Add defines related to notes for GNU systems
linux-user: Parse NT_GNU_PROPERTY_TYPE_0 notes
tests/tcg/aarch64: Add bti smoke test
include/elf.h | 48 ++++++++++++
include/exec/cpu-all.h | 2 +
linux-user/syscall_defs.h | 4 +
linux-user/aarch64/cpu_loop.c | 7 ++
linux-user/aarch64/signal.c | 10 ++-
linux-user/elfload.c | 83 ++++++++++++++++++--
linux-user/mmap.c | 122 ++++++++++++++++++++++--------
target/arm/translate-a64.c | 6 +-
tests/tcg/aarch64/bti-1.c | 77 +++++++++++++++++++
tests/tcg/aarch64/bti-crt.inc.c | 69 +++++++++++++++++
tests/tcg/aarch64/Makefile.target | 3 +
11 files changed, 387 insertions(+), 44 deletions(-)
create mode 100644 tests/tcg/aarch64/bti-1.c
create mode 100644 tests/tcg/aarch64/bti-crt.inc.c
--
2.17.1
next reply other threads:[~2019-06-05 21:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:57 Richard Henderson [this message]
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 1/6] linux-user/aarch64: Reset btype for syscalls and signals Richard Henderson
2019-06-06 9:53 ` [Qemu-devel] [PATCH v6 1/6] linux-user/aarch64: Reset btype for syscalls and signalsy Dave Martin
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 2/6] linux-user: Validate mmap/mprotect prot value Richard Henderson
2019-06-06 11:24 ` Aleksandar Markovic
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 3/6] linux-user: Set PAGE_TARGET_1 for TARGET_PROT_BTI Richard Henderson
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 4/6] include/elf: Add defines related to notes for GNU systems Richard Henderson
2019-06-05 21:17 ` Aleksandar Markovic
2019-06-06 5:45 ` Aleksandar Markovic
2019-06-06 8:42 ` Markus Armbruster
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 5/6] linux-user: Parse NT_GNU_PROPERTY_TYPE_0 notes Richard Henderson
2019-06-06 10:12 ` Dave Martin
2019-06-05 20:57 ` [Qemu-devel] [PATCH v6 6/6] tests/tcg/aarch64: Add bti smoke test Richard Henderson
2019-06-06 10:21 ` Dave Martin
2019-06-06 14:24 ` Richard Henderson
2019-06-05 22:15 ` [Qemu-devel] [PATCH v6 0/6] linux-user/aarch64: Support PROT_BTI no-reply
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=20190605205706.569-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Dave.Martin@arm.com \
--cc=peter.maydell@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).