From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4 0/6] Memory tagging support
Date: Fri, 18 Dec 2020 12:18:26 -0800 [thread overview]
Message-ID: <CAMe9rOq4uTuYQJe4DBuwjoBVQOHt7K4923-8Zqw729iDv7CVaw@mail.gmail.com> (raw)
In-Reply-To: <20201218192957.11035-1-rearnsha@arm.com>
On Fri, Dec 18, 2020 at 11:31 AM Richard Earnshaw via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Main changes in this version:
>
> - collapse the changes to the malloc code to a single patch.
> - change _LIBC_MTAG to USE_MTAG.
Should we use ENABLE_MTAG instead of USE_MTAG? The same
glibc binary should work with and without memory tag
> - comments around definition of PROT_MTE.
> - tunable renamed to glibc.mem.tagging.
> - cleanups to assembler files for aarch64 support.
>
> I'll push a copy of this patch set to rearnsha/mte-v4.0 shortly.
>
> 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 +
> malloc/arena.c | 59 ++-
> malloc/hooks.c | 79 ++--
> malloc/malloc.c | 336 ++++++++++++++----
> malloc/malloc.h | 7 +
> 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, 836 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
>
--
H.J.
next prev parent reply other threads:[~2020-12-18 20:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 19:29 Richard Earnshaw
2020-12-18 19:29 ` [PATCH v4 1/6] config: Allow memory tagging to be enabled when configuring glibc Richard Earnshaw
2020-12-21 12:40 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 2/6] elf: Add a tunable to control use of tagged memory Richard Earnshaw
2020-12-21 12:42 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 3/6] malloc: Basic support for memory tagging in the malloc() family Richard Earnshaw
2020-12-21 13:27 ` Siddhesh Poyarekar
2020-12-21 13:46 ` Florian Weimer
2020-12-21 14:31 ` Richard Earnshaw
2020-12-21 14:31 ` Szabolcs Nagy
2020-12-18 19:29 ` [PATCH v4 4/6] linux: Add compatibility definitions to sys/prctl.h for MTE Richard Earnshaw
2020-12-21 13:32 ` Siddhesh Poyarekar
2020-12-21 13:34 ` Richard Earnshaw
2020-12-21 13:38 ` Siddhesh Poyarekar
2020-12-21 13:39 ` Florian Weimer
2020-12-21 13:41 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 5/6] aarch64: Add sysv specific enabling code for memory tagging Richard Earnshaw
2020-12-21 12:27 ` Szabolcs Nagy
2020-12-21 13:36 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 6/6] aarch64: Add aarch64-specific files for memory tagging support Richard Earnshaw
2020-12-21 12:44 ` Szabolcs Nagy
2020-12-21 12:50 ` Richard Earnshaw
2020-12-18 20:18 ` H.J. Lu [this message]
2020-12-21 12:28 ` [PATCH v4 0/6] Memory " Siddhesh Poyarekar
2020-12-21 13:44 ` Siddhesh Poyarekar
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=CAMe9rOq4uTuYQJe4DBuwjoBVQOHt7K4923-8Zqw729iDv7CVaw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=rearnsha@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).