From: Richard Earnshaw <rearnsha@arm.com>
To: libc-alpha@sourceware.org
Cc: Richard Earnshaw <rearnsha@arm.com>,
dj@redhat.com, szabolcs.nagy@arm.com
Subject: [PATCH v5 0/6] [committed] Memory tagging support
Date: Mon, 21 Dec 2020 15:33:39 +0000 [thread overview]
Message-ID: <20201221153345.3742-1-rearnsha@arm.com> (raw)
Final version, as committed to master.
The following minor tweaks were made:
- Move some preprocessor definitions from malloc/malloc.h to include/malloc.h
- Fix a comment in arena.c
- Fix non-GNU style in sysdeps/aarch64/libc-mtag.h
- updated one commit message to indicate version of linux that supports MTE.
- sprinkle some Reviewed-by where appropriate.
With thanks to Szabolcs and Siddhesh for prompt reviews.
R.
Richard Earnshaw (6):
config: Allow memory tagging to be enabled when configuring glibc
elf: Add a tunable to control use of tagged memory
malloc: Basic support for memory tagging in the malloc() family
linux: Add compatibility definitions to sys/prctl.h for MTE
aarch64: Add sysv specific enabling code for memory tagging
aarch64: Add aarch64-specific files for memory tagging support
INSTALL | 14 +
config.h.in | 3 +
config.make.in | 2 +
configure | 22 ++
configure.ac | 15 +
elf/dl-tunables.list | 9 +
include/malloc.h | 8 +
malloc/arena.c | 59 ++-
malloc/hooks.c | 79 ++--
malloc/malloc.c | 336 ++++++++++++++----
manual/install.texi | 13 +
manual/tunables.texi | 35 ++
sysdeps/aarch64/Makefile | 5 +
sysdeps/aarch64/__mtag_address_get_tag.S | 32 ++
sysdeps/aarch64/__mtag_memset_tag.S | 53 +++
sysdeps/aarch64/__mtag_new_tag.S | 37 ++
sysdeps/aarch64/__mtag_tag_region.S | 51 +++
sysdeps/aarch64/libc-mtag.h | 57 +++
sysdeps/generic/libc-mtag.h | 52 +++
sysdeps/unix/sysv/linux/aarch64/bits/hwcap.h | 1 +
sysdeps/unix/sysv/linux/aarch64/bits/mman.h | 1 +
.../unix/sysv/linux/aarch64/cpu-features.c | 30 ++
.../unix/sysv/linux/aarch64/cpu-features.h | 2 +
sysdeps/unix/sysv/linux/sys/prctl.h | 18 +
24 files changed, 837 insertions(+), 97 deletions(-)
create mode 100644 sysdeps/aarch64/__mtag_address_get_tag.S
create mode 100644 sysdeps/aarch64/__mtag_memset_tag.S
create mode 100644 sysdeps/aarch64/__mtag_new_tag.S
create mode 100644 sysdeps/aarch64/__mtag_tag_region.S
create mode 100644 sysdeps/aarch64/libc-mtag.h
create mode 100644 sysdeps/generic/libc-mtag.h
--
2.29.2
next reply other threads:[~2020-12-21 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 15:33 Richard Earnshaw [this message]
2020-12-21 15:33 ` [PATCH v5 1/6] config: Allow memory tagging to be enabled when configuring glibc Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 2/6] elf: Add a tunable to control use of tagged memory Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 3/6] malloc: Basic support for memory tagging in the malloc() family Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 4/6] linux: Add compatibility definitions to sys/prctl.h for MTE Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 5/6] aarch64: Add sysv specific enabling code for memory tagging Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 6/6] aarch64: Add aarch64-specific files for memory tagging support Richard Earnshaw
2020-12-22 12:49 ` [PATCH v5 0/6] [committed] Memory " Andreas Schwab
2020-12-22 12:58 ` Siddhesh Poyarekar
2020-12-22 13:21 ` Andreas Schwab
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=20201221153345.3742-1-rearnsha@arm.com \
--to=rearnsha@arm.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).