Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: gdb-patches@sourceware.org, Alan.Hayward@arm.com
Cc: omair.javaid@linaro.org, david.spickett@linaro.org,
	jose.marchesi@oracle.com
Subject: Re: [PATCH 00/23] Memory Tagging Support + AArch64 Linux implementation
Date: Thu, 23 Jul 2020 11:59:37 -0300	[thread overview]
Message-ID: <e663463c-8a44-3839-e23d-9e64058b9b60@linaro.org> (raw)
In-Reply-To: <20200715194513.16641-1-luis.machado@linaro.org>

Ping?

On 7/15/20 4:44 PM, Luis Machado wrote:
> This patch series implements general memory tagging support for GDB, as well
> as an implementation for AArch64 Linux.
> 
> 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 (23):
>    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
>    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
>    New mtag 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                               |  32 ++
>   gdb/aarch64-linux-nat.c                | 121 ++++++-
>   gdb/aarch64-linux-tdep.c               | 330 ++++++++++++++++-
>   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           |  70 ++++
>   gdb/arch/aarch64-mte-linux.h           |  66 ++++
>   gdb/arch/aarch64.c                     |   7 +-
>   gdb/arch/aarch64.h                     |   7 +-
>   gdb/configure.nat                      |   3 +-
>   gdb/configure.tgt                      |   1 +
>   gdb/doc/gdb.texinfo                    | 174 ++++++++-
>   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                       | 356 ++++++++++++-------
>   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                           | 230 ++++++++++++
>   gdb/target-delegates.c                 |  84 +++++
>   gdb/target.h                           |  25 ++
>   gdb/testsuite/gdb.arch/aarch64-mte.c   | 107 ++++++
>   gdb/testsuite/gdb.arch/aarch64-mte.exp | 371 ++++++++++++++++++++
>   gdb/testsuite/gdb.base/memtag.c        |  22 ++
>   gdb/testsuite/gdb.base/memtag.exp      |  64 ++++
>   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         |  89 ++++-
>   gdbserver/linux-aarch64-tdesc.cc       |  10 +-
>   gdbserver/linux-aarch64-tdesc.h        |   3 +-
>   gdbserver/remote-utils.cc              |  40 +--
>   gdbserver/remote-utils.h               |   2 +
>   gdbserver/server.cc                    | 214 +++++++++++
>   gdbserver/server.h                     |   3 +
>   gdbserver/target.cc                    |  20 ++
>   gdbserver/target.h                     |  17 +
>   gdbsupport/rsp-low.cc                  |   2 +-
>   include/elf/common.h                   |   3 +
>   49 files changed, 3421 insertions(+), 182 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
> 


      parent reply	other threads:[~2020-07-23 14:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 19:44 Luis Machado
2020-07-15 19:44 ` [PATCH 01/23] New target methods for memory tagging support Luis Machado
2020-07-15 19:44 ` [PATCH 02/23] New gdbarch memory tagging hooks Luis Machado
2020-07-15 19:44 ` [PATCH 03/23] Add GDB-side remote target support for memory tagging Luis Machado
2020-07-15 19:44 ` [PATCH 04/23] Unit testing for GDB-side remote memory tagging handling Luis Machado
2020-07-15 19:44 ` [PATCH 05/23] GDBserver remote packet support for memory tagging Luis Machado
2020-07-15 19:44 ` [PATCH 06/23] Unit tests for gdbserver memory tagging remote packets Luis Machado
2020-07-15 19:44 ` [PATCH 07/23] Documentation for " Luis Machado
2020-07-17  5:54   ` Eli Zaretskii
2020-07-17 14:20     ` Luis Machado
2020-07-15 19:44 ` [PATCH 08/23] AArch64: Add MTE CPU feature check support Luis Machado
2020-07-15 19:44 ` [PATCH 09/23] AArch64: Add target description/feature for MTE registers Luis Machado
2020-07-15 19:45 ` [PATCH 10/23] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado
2020-07-15 19:45 ` [PATCH 11/23] AArch64: Add MTE ptrace requests Luis Machado
2020-07-15 19:45 ` [PATCH 12/23] AArch64: Implement memory tagging target methods for AArch64 Luis Machado
2020-07-15 19:45 ` [PATCH 13/23] Refactor parsing of /proc/<pid>/smaps Luis Machado
2020-07-15 19:45 ` [PATCH 14/23] AArch64: Implement the memory tagging gdbarch hooks Luis Machado
2020-07-15 19:45 ` [PATCH 15/23] AArch64: Add unit testing for logical tag set/get operations Luis Machado
2020-07-15 19:45 ` [PATCH 16/23] AArch64: Report tag violation error information Luis Machado
2020-07-15 19:45 ` [PATCH 17/23] AArch64: Add gdbserver MTE support Luis Machado
2020-07-15 19:45 ` [PATCH 18/23] New mtag commands Luis Machado
2020-07-15 19:45 ` [PATCH 19/23] Documentation for the new " Luis Machado
2020-07-17  6:11   ` Eli Zaretskii
2020-07-17 14:20     ` Luis Machado
2020-07-17 14:29       ` Eli Zaretskii
2020-07-17 15:08         ` Luis Machado
2020-07-15 19:45 ` [PATCH 20/23] Extend "x" and "print" commands to support memory tagging Luis Machado
2020-07-15 19:45 ` [PATCH 21/23] Document new "x" and "print" memory tagging extensions Luis Machado
2020-07-17  6:16   ` Eli Zaretskii
2020-07-17 14:20     ` Luis Machado
2020-07-17 14:31       ` Eli Zaretskii
2020-07-15 19:45 ` [PATCH 22/23] Add NEWS entry Luis Machado
2020-07-17  6:18   ` Eli Zaretskii
2020-07-17 14:20     ` Luis Machado
2020-07-15 19:45 ` [PATCH 23/23] Add memory tagging testcases Luis Machado
2020-07-16 16:49 ` [PATCH 00/23] Memory Tagging Support + AArch64 Linux implementation Alan Hayward
2020-07-17 12:33   ` Luis Machado
2020-07-17 22:02 ` John Baldwin
2020-07-23 13:59   ` Luis Machado
2020-07-23 16:48     ` John Baldwin
2020-07-24 16:10       ` David Spickett
2020-07-23 14:59 ` Luis Machado [this message]

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=e663463c-8a44-3839-e23d-9e64058b9b60@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=Alan.Hayward@arm.com \
    --cc=david.spickett@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=omair.javaid@linaro.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