From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Cc: david.spickett@linaro.org
Subject: Re: [PING] [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation
Date: Tue, 26 Jan 2021 11:26:24 -0500 [thread overview]
Message-ID: <a1986b81-da71-cab8-53af-cfe542f1b176@polymtl.ca> (raw)
In-Reply-To: <d0bcd01a-f140-b6cf-0e06-8abd73c878fd@linaro.org>
Just wondering, do you intend to update the settings as suggested here?
https://sourceware.org/pipermail/gdb-patches/2021-January/175198.html
Simon
On 2021-01-26 8:03 a.m., Luis Machado via Gdb-patches wrote:
>
> On 1/15/21 1:02 PM, Luis Machado wrote:
>> Ping?
>>
>> On 12/30/20 12:38 PM, Luis Machado wrote:
>>> Memory tagging improves memory safety by tagging various parts of memory and
>>> raising exceptions when the allocation tag (the one associated with a range of
>>> memory addresses) does not match the logical tag contained in a pointer that is
>>> used to access the memory area.
>>>
>>> We already have an implementation of such a mechanism for sparc64 (ADI), but
>>> it is target-specific and not exposed to the rest of GDB. This series aims to
>>> make the infrastructure available to other targets that may wish to support
>>> their specific memory tagging approaches. For AArch64 Linux this is called
>>> MTE (Memory Tagging Extensions).
>>>
>>> The series is split into a set that deals with generic changes to GDB's
>>> infrastructure (target methods, gdbarch hooks and remote packets), a set that
>>> implements support for AArch64 Linux and one last set that implements new
>>> commands, updates the documentation and adds tests.
>>>
>>> The goal is to make it so the architecture independent parts of GDB don't
>>> need to interpret tag formats, given the formats are likely different
>>> for each architecture. For this reason, GDB will handle tags as a sequence of
>>> bytes and will not assume a particular format.
>>>
>>> The architecture-specific code can handle the sequence of bytes appropriately.
>>>
>>> Luis Machado (25):
>>> New target methods for memory tagging support
>>> New gdbarch memory tagging hooks
>>> Add GDB-side remote target support for memory tagging
>>> Unit testing for GDB-side remote memory tagging handling
>>> GDBserver remote packet support for memory tagging
>>> Unit tests for gdbserver memory tagging remote packets
>>> Documentation for memory tagging remote packets
>>> AArch64: Add MTE CPU feature check support
>>> AArch64: Add target description/feature for MTE registers
>>> AArch64: Add MTE register set support for GDB and gdbserver
>>> AArch64: Add MTE ptrace requests
>>> AArch64: Implement memory tagging target methods for AArch64
>>> Convert char array to std::string in linux_find_memory_regions_full
>>> Refactor parsing of /proc/<pid>/smaps
>>> AArch64: Implement the memory tagging gdbarch hooks
>>> AArch64: Add unit testing for logical tag set/get operations
>>> AArch64: Report tag violation error information
>>> AArch64: Add gdbserver MTE support
>>> AArch64: Add MTE register set support for core files
>>> New memory-tag commands
>>> Documentation for the new mtag commands
>>> Extend "x" and "print" commands to support memory tagging
>>> Document new "x" and "print" memory tagging extensions
>>> Add NEWS entry.
>>> Add memory tagging testcases
>>>
>>> gdb/Makefile.in | 3 +
>>> gdb/NEWS | 36 +-
>>> gdb/aarch64-linux-nat.c | 127 ++++++-
>>> gdb/aarch64-linux-tdep.c | 336 +++++++++++++++++-
>>> gdb/aarch64-linux-tdep.h | 3 +
>>> gdb/aarch64-tdep.c | 40 ++-
>>> gdb/aarch64-tdep.h | 12 +-
>>> gdb/arch-utils.c | 50 +++
>>> gdb/arch-utils.h | 23 ++
>>> gdb/arch/aarch64-mte-linux.c | 73 ++++
>>> gdb/arch/aarch64-mte-linux.h | 75 ++++
>>> gdb/arch/aarch64.c | 7 +-
>>> gdb/arch/aarch64.h | 7 +-
>>> gdb/configure.nat | 3 +-
>>> gdb/configure.tgt | 1 +
>>> gdb/doc/gdb.texinfo | 233 +++++++++++-
>>> gdb/features/Makefile | 1 +
>>> gdb/features/aarch64-mte.c | 14 +
>>> gdb/features/aarch64-mte.xml | 11 +
>>> gdb/gdbarch.c | 137 ++++++++
>>> gdb/gdbarch.h | 53 +++
>>> gdb/gdbarch.sh | 36 ++
>>> gdb/linux-tdep.c | 378 +++++++++++++-------
>>> gdb/linux-tdep.h | 4 +
>>> gdb/nat/aarch64-mte-linux-ptrace.c | 200 +++++++++++
>>> gdb/nat/aarch64-mte-linux-ptrace.h | 50 +++
>>> gdb/printcmd.c | 468 ++++++++++++++++++++++++-
>>> gdb/remote.c | 227 ++++++++++++
>>> gdb/target-debug.h | 24 ++
>>> gdb/target-delegates.c | 95 +++++
>>> gdb/target.h | 41 +++
>>> gdb/testsuite/gdb.arch/aarch64-mte.c | 107 ++++++
>>> gdb/testsuite/gdb.arch/aarch64-mte.exp | 369 +++++++++++++++++++
>>> gdb/testsuite/gdb.base/memtag.c | 22 ++
>>> gdb/testsuite/gdb.base/memtag.exp | 66 ++++
>>> gdb/testsuite/lib/gdb.exp | 16 +
>>> gdb/valprint.h | 1 +
>>> gdbserver/Makefile.in | 1 +
>>> gdbserver/configure.srv | 2 +
>>> gdbserver/linux-aarch64-ipa.cc | 8 +-
>>> gdbserver/linux-aarch64-low.cc | 97 ++++-
>>> gdbserver/linux-aarch64-tdesc.cc | 10 +-
>>> gdbserver/linux-aarch64-tdesc.h | 3 +-
>>> gdbserver/remote-utils.cc | 43 ++-
>>> gdbserver/remote-utils.h | 7 +-
>>> gdbserver/server.cc | 219 ++++++++++++
>>> gdbserver/server.h | 3 +
>>> gdbserver/target.cc | 20 ++
>>> gdbserver/target.h | 21 ++
>>> gdbsupport/common-utils.cc | 49 +++
>>> gdbsupport/common-utils.h | 15 +
>>> gdbsupport/rsp-low.cc | 49 ---
>>> gdbsupport/rsp-low.h | 19 -
>>> include/elf/common.h | 3 +
>>> 54 files changed, 3654 insertions(+), 264 deletions(-)
>>> create mode 100644 gdb/arch/aarch64-mte-linux.c
>>> create mode 100644 gdb/arch/aarch64-mte-linux.h
>>> create mode 100644 gdb/features/aarch64-mte.c
>>> create mode 100644 gdb/features/aarch64-mte.xml
>>> create mode 100644 gdb/nat/aarch64-mte-linux-ptrace.c
>>> create mode 100644 gdb/nat/aarch64-mte-linux-ptrace.h
>>> create mode 100644 gdb/testsuite/gdb.arch/aarch64-mte.c
>>> create mode 100644 gdb/testsuite/gdb.arch/aarch64-mte.exp
>>> create mode 100644 gdb/testsuite/gdb.base/memtag.c
>>> create mode 100644 gdb/testsuite/gdb.base/memtag.exp
>>>
next prev parent reply other threads:[~2021-01-26 16:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:38 Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 01/25] New target methods for memory tagging support Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 02/25] New gdbarch memory tagging hooks Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 03/25] Add GDB-side remote target support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 04/25] Unit testing for GDB-side remote memory tagging handling Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 05/25] GDBserver remote packet support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 06/25] Unit tests for gdbserver memory tagging remote packets Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 07/25] Documentation for " Luis Machado via Gdb-patches
2020-12-30 20:41 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 08/25] AArch64: Add MTE CPU feature check support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 09/25] AArch64: Add target description/feature for MTE registers Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 10/25] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 11/25] AArch64: Add MTE ptrace requests Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 12/25] AArch64: Implement memory tagging target methods for AArch64 Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 13/25] Convert char array to std::string in linux_find_memory_regions_full Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 14/25] Refactor parsing of /proc/<pid>/smaps Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 15/25] AArch64: Implement the memory tagging gdbarch hooks Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 16/25] AArch64: Add unit testing for logical tag set/get operations Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 17/25] AArch64: Report tag violation error information Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 18/25] AArch64: Add gdbserver MTE support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 19/25] AArch64: Add MTE register set support for core files Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 20/25] New memory-tag commands Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 21/25] Documentation for the new mtag commands Luis Machado via Gdb-patches
2020-12-30 20:43 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 22/25] Extend "x" and "print" commands to support memory tagging Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 23/25] Document new "x" and "print" memory tagging extensions Luis Machado via Gdb-patches
2020-12-30 20:44 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 24/25] Add NEWS entry Luis Machado via Gdb-patches
2020-12-30 20:45 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 25/25] Add memory tagging testcases Luis Machado via Gdb-patches
2021-01-15 16:02 ` [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado via Gdb-patches
2021-01-26 13:03 ` [PING] " Luis Machado via Gdb-patches
2021-01-26 16:26 ` Simon Marchi via Gdb-patches [this message]
2021-01-26 16:36 ` Luis Machado via Gdb-patches
2021-01-26 16:49 ` Simon Marchi via Gdb-patches
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=a1986b81-da71-cab8-53af-cfe542f1b176@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=david.spickett@linaro.org \
--cc=luis.machado@linaro.org \
--cc=simon.marchi@polymtl.ca \
/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