From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH v5 01/25] New target methods for memory tagging support
Date: Thu, 4 Feb 2021 21:31:39 -0500 [thread overview]
Message-ID: <c27fb316-bccc-6a20-d76a-5791dc718472@polymtl.ca> (raw)
In-Reply-To: <20210127202112.2485702-2-luis.machado@linaro.org>
On 2021-01-27 3:20 p.m., Luis Machado via Gdb-patches wrote:
> Updates on v5:
>
> - Remove the memory_tagging global (in favor of setting a specific print
> option) and related functions.
>
> Updates on v4:
>
> - Updated the return types of fetch/store member functions from int to bool.
> - Implemented target-debug type print helpers.
> - Renamed global memtag to memory_tagging.
>
> Updates on v3:
>
> - Updated the code documentation for the fetch_memtags and store_memtags
> methods.
>
> Updates on v2:
>
> - Added type parameter to fetch_memtags/store_memtags hooks.
>
> --
>
> This patch starts adding some of the generic pieces to accomodate memory
> tagging.
>
> We have three new target methods:
>
> - supports_memory_tagging: Checks if the target supports memory tagging. This
> defaults to false for targets that don't support memory tagging.
>
> - fetch_memtags: Fetches the allocation tags associated with a particular
> memory range [address, address + length).
>
> The default is to return 0 without returning any tags. This should only
> be called if memory tagging is supported.
>
> - store_memtags: Stores a set of allocation tags for a particular memory
> range [address, address + length).
>
> The default is to return 0. This should only
> be called if memory tagging is supported.
>
> gdb/ChangeLog:
>
> YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
>
> * remote.c (remote_target) <supports_memory_tagging>: New method
> override.
> <fetch_memtags>: New method override.
> <store_memtags>: New method override.
> (remote_target::supports_memory_tagging): New method.
> (remote_target::fetch_memtags): New method.
> (remote_target::store_memtags): New method.
> * target-delegates.c: Regenerate.
> * target.h (struct target_ops) <supports_memory_tagging>: New virtual
> method.
> <fetch_memtags>: New virtual method.
> <store_memtags>: New virtual method.
> (target_supports_memory_tagging): Define.
> (target_fetch_memtags): Define.
> (target_store_memtags): Define.
> * target-debug.h (target_debug_print_size_t)
> (target_debug_print_const_gdb_byte_vector_r)
> (target_debug_print_gdb_byte_vector_r): New functions.
> ---
> gdb/remote.c | 34 +++++++++++++++
> gdb/target-debug.h | 24 +++++++++++
> gdb/target-delegates.c | 95 ++++++++++++++++++++++++++++++++++++++++++
> gdb/target.h | 41 ++++++++++++++++++
> 4 files changed, 194 insertions(+)
>
> diff --git a/gdb/remote.c b/gdb/remote.c
> index bc995edc53..b130f1ddae 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -690,6 +690,14 @@ class remote_target : public process_stratum_target
> int remove_exec_catchpoint (int) override;
> enum exec_direction_kind execution_direction () override;
>
> + bool supports_memory_tagging () override;
> +
> + bool fetch_memtags (CORE_ADDR address, size_t len,
> + gdb::byte_vector &tags, int type) override;
> +
> + bool store_memtags (CORE_ADDR address, size_t len,
> + const gdb::byte_vector &tags, int type) override;
The indentation is a bit off here. Otherwise, LGTM.
Simon
next prev parent reply other threads:[~2021-02-05 2:31 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 20:20 [PATCH v5 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado
2021-01-27 20:20 ` [PATCH v5 01/25] New target methods for memory tagging support Luis Machado
2021-01-27 23:26 ` Lancelot SIX
2021-01-28 10:02 ` Luis Machado
2021-02-05 2:31 ` Simon Marchi [this message]
2021-01-27 20:20 ` [PATCH v5 02/25] New gdbarch memory tagging hooks Luis Machado
2021-02-05 2:38 ` Simon Marchi
2021-02-05 3:58 ` Simon Marchi
2021-01-27 20:20 ` [PATCH v5 03/25] Add GDB-side remote target support for memory tagging Luis Machado
2021-02-05 2:48 ` Simon Marchi
2021-01-27 20:20 ` [PATCH v5 04/25] Unit testing for GDB-side remote memory tagging handling Luis Machado
2021-02-05 2:50 ` Simon Marchi
2021-01-27 20:20 ` [PATCH v5 05/25] GDBserver remote packet support for memory tagging Luis Machado
2021-02-05 2:56 ` Simon Marchi
2021-02-05 12:38 ` Luis Machado
2021-01-27 20:20 ` [PATCH v5 06/25] Unit tests for gdbserver memory tagging remote packets Luis Machado
2021-01-27 20:20 ` [PATCH v5 07/25] Documentation for " Luis Machado
2021-01-28 3:30 ` Eli Zaretskii
2021-01-28 9:58 ` Luis Machado
2021-01-27 20:20 ` [PATCH v5 08/25] AArch64: Add MTE CPU feature check support Luis Machado
2021-02-05 3:05 ` Simon Marchi
2021-01-27 20:20 ` [PATCH v5 09/25] AArch64: Add target description/feature for MTE registers Luis Machado
2021-01-27 20:20 ` [PATCH v5 10/25] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado
2021-01-27 20:20 ` [PATCH v5 11/25] AArch64: Add MTE ptrace requests Luis Machado
2021-02-05 3:13 ` Simon Marchi
2021-01-27 20:20 ` [PATCH v5 12/25] AArch64: Implement memory tagging target methods for AArch64 Luis Machado
2021-02-05 3:30 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 13/25] Convert char array to std::string in linux_find_memory_regions_full Luis Machado
2021-02-05 3:32 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 14/25] Refactor parsing of /proc/<pid>/smaps Luis Machado
2021-02-05 3:38 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 15/25] AArch64: Implement the memory tagging gdbarch hooks Luis Machado
2021-02-05 4:09 ` Simon Marchi
2021-02-05 14:05 ` Luis Machado
2021-01-27 20:21 ` [PATCH v5 16/25] AArch64: Add unit testing for logical tag set/get operations Luis Machado
2021-01-27 20:21 ` [PATCH v5 17/25] AArch64: Report tag violation error information Luis Machado
2021-02-05 4:22 ` Simon Marchi
2021-02-05 14:59 ` Luis Machado
2021-02-05 16:13 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 18/25] AArch64: Add gdbserver MTE support Luis Machado
2021-01-27 20:21 ` [PATCH v5 19/25] AArch64: Add MTE register set support for core files Luis Machado
2021-01-27 20:21 ` [PATCH v5 20/25] New memory-tag commands Luis Machado
2021-02-05 4:49 ` Simon Marchi
2021-02-05 4:52 ` Simon Marchi
2021-02-08 18:59 ` Luis Machado
2021-03-23 21:46 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 21/25] Documentation for the new mtag commands Luis Machado
2021-01-28 3:31 ` Eli Zaretskii
2021-02-05 4:50 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 22/25] Extend "x" and "print" commands to support memory tagging Luis Machado
2021-02-05 5:02 ` Simon Marchi
2021-01-27 20:21 ` [PATCH v5 23/25] Document new "x" and "print" memory tagging extensions Luis Machado
2021-01-28 3:31 ` Eli Zaretskii
2021-02-05 5:04 ` Simon Marchi
2021-02-08 20:44 ` Luis Machado
2021-01-27 20:21 ` [PATCH v5 24/25] Add NEWS entry Luis Machado
2021-01-28 3:32 ` Eli Zaretskii
2021-02-05 5:06 ` Simon Marchi
2021-02-08 20:44 ` Luis Machado
2021-01-27 20:21 ` [PATCH v5 25/25] Add memory tagging testcases Luis Machado
2021-02-04 14:18 ` [PING] [PATCH v5 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado
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=c27fb316-bccc-6a20-d76a-5791dc718472@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).