From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: david.spickett@linaro.org
Subject: [PATCH v4 03/25] Add GDB-side remote target support for memory tagging
Date: Wed, 30 Dec 2020 12:38:54 -0300 [thread overview]
Message-ID: <20201230153916.1586725-4-luis.machado@linaro.org> (raw)
In-Reply-To: <20201230153916.1586725-1-luis.machado@linaro.org>
Updates for v4:
- Rename RSP helper functions.
- Fixup parameter and return types.
Updates for v2:
- Add type field to target hooks.
- Add type data to qMemTags and QMemTags. The packets now look like this:
qMemTags:<address>,<length>:<type>
QMemTags:<address>,<length>:<type>:<uninterpreted tag bytes>
--
This patch adds memory tagging support to GDB's remote side, with
packet string checks, new packet support and an implementation of
the two new tags methods fetch_atags and store_atags.
GDBserver needs to know how to read/write allocation tags, since that is
done via ptrace. It doesn't need to know about logical tags.
The new packets are:
qMemTags:<address>,<length>:<type>
--
Reads tags of the specified type from the address range
[<address>, <address + length>)
QMemTags:<address>,<length>:<type>:<uninterpreted tag bytes>
--
Writes the tags of specified type represented by the uninterpreted bytes to
the address range [<address>, <address + length>).
The interpretation of what to do with the tag bytes is up to the arch-specific
code.
Note that these new packets consider the case of packet size overflow as an
error, given the common use case is to read/write only a few memory tags at
a time. Having to use a couple new packets for multi-part transfers wouldn't
make sense for the little use it would have.
gdb/ChangeLog:
YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
* remote.c (PACKET_memory_tagging_feature): New enum.
(remote_memory_tagging_p): New function.
(remote_protocol_features): New "memory-tagging" entry.
(remote_target::remote_query_supported): Handle memory tagging
support.
(remote_target::supports_memory_tagging): Implement.
(create_fetch_memtags_request, parse_fetch_memtags_reply)
(create_store_memtags_request): New functions.
(remote_target::fetch_memtags): Implement.
(remote_target::store_memtags): Implement.
(_initialize_remote): Add new "memory-tagging-feature"
config command.
---
gdb/remote.c | 106 +++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 103 insertions(+), 3 deletions(-)
diff --git a/gdb/remote.c b/gdb/remote.c
index c7f09c4269..77e3ecca86 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -2102,6 +2102,10 @@ enum {
/* Support TARGET_WAITKIND_NO_RESUMED. */
PACKET_no_resumed,
+ /* Support for memory tagging, allocation tag fetch/store
+ packets and the tag violation stop replies. */
+ PACKET_memory_tagging_feature,
+
PACKET_MAX
};
@@ -2243,6 +2247,14 @@ remote_exec_event_p (struct remote_state *rs)
return packet_support (PACKET_exec_event_feature) == PACKET_ENABLE;
}
+/* Returns true if memory tagging is supported. */
+
+static bool
+remote_memory_tagging_p (void)
+{
+ return packet_support (PACKET_memory_tagging_feature) == PACKET_ENABLE;
+}
+
/* Insert fork catchpoint target routine. If fork events are enabled
then return success, nothing more to do. */
@@ -5245,6 +5257,8 @@ static const struct protocol_feature remote_protocol_features[] = {
{ "vContSupported", PACKET_DISABLE, remote_supported_packet, PACKET_vContSupported },
{ "QThreadEvents", PACKET_DISABLE, remote_supported_packet, PACKET_QThreadEvents },
{ "no-resumed", PACKET_DISABLE, remote_supported_packet, PACKET_no_resumed },
+ { "memory-tagging", PACKET_DISABLE, remote_supported_packet,
+ PACKET_memory_tagging_feature },
};
static char *remote_support_xml;
@@ -5339,6 +5353,10 @@ remote_target::remote_query_supported ()
if (packet_set_cmd_state (PACKET_no_resumed) != AUTO_BOOLEAN_FALSE)
remote_query_supported_append (&q, "no-resumed+");
+ if (packet_set_cmd_state (PACKET_memory_tagging_feature)
+ != AUTO_BOOLEAN_FALSE)
+ remote_query_supported_append (&q, "memory-tagging+");
+
/* Keep this one last to work around a gdbserver <= 7.10 bug in
the qSupported:xmlRegisters=i386 handling. */
if (remote_support_xml != NULL
@@ -14402,7 +14420,63 @@ set_range_stepping (const char *ignore_args, int from_tty,
bool
remote_target::supports_memory_tagging ()
{
- return false;
+ return remote_memory_tagging_p ();
+}
+
+/* Create the qMemTags packet given ADDRESS, LEN and TYPE. */
+
+static void
+create_fetch_memtags_request (gdb::char_vector &packet, CORE_ADDR address,
+ size_t len, int type)
+{
+ int addr_size = gdbarch_addr_bit (target_gdbarch ()) / 8;
+
+ std::string request = string_printf ("qMemTags:%s,%s:%s",
+ phex_nz (address, addr_size),
+ phex_nz (len, sizeof (len)),
+ phex_nz (type, sizeof (type)));
+
+ strcpy (packet.data (), request.c_str ());
+}
+
+/* Parse the qMemTags packet reply into TAGS.
+
+ Return true if successful, false otherwise. */
+
+static bool
+parse_fetch_memtags_reply (const gdb::char_vector &reply,
+ gdb::byte_vector &tags)
+{
+ if (reply.empty () || reply[0] == 'E' || reply[0] != 'm')
+ return false;
+
+ /* Copy the tag data. */
+ tags = hex2bin (reply.data () + 1);
+
+ return true;
+}
+
+/* Create the QMemTags packet given ADDRESS, LEN, TYPE and TAGS. */
+
+static void
+create_store_memtags_request (gdb::char_vector &packet, CORE_ADDR address,
+ size_t len, int type,
+ const gdb::byte_vector &tags)
+{
+ int addr_size = gdbarch_addr_bit (target_gdbarch ()) / 8;
+
+ /* Put together the main packet, address and length. */
+ std::string request = string_printf ("QMemTags:%s,%s:%s:",
+ phex_nz (address, addr_size),
+ phex_nz (len, sizeof (len)),
+ phex_nz (type, sizeof (type)));
+ request += bin2hex (tags.data (), tags.size ());
+
+ /* Check if we have exceeded the maximum packet size. */
+ if (packet.size () < request.length ())
+ error (_("Contents too big for packet QMemTags."));
+
+ strcpy (packet.data (), request.c_str ());
}
/* Implement the "fetch_memtags" target_ops method. */
@@ -14411,7 +14485,18 @@ bool
remote_target::fetch_memtags (CORE_ADDR address, size_t len,
gdb::byte_vector &tags, int type)
{
- return 0;
+ /* Make sure the qMemTags packet is supported. */
+ if (!remote_memory_tagging_p ())
+ gdb_assert_not_reached ("remote fetch_memtags called with packet disabled");
+
+ struct remote_state *rs = get_remote_state ();
+
+ create_fetch_memtags_request (rs->buf, address, len, type);
+
+ putpkt (rs->buf);
+ getpkt (&rs->buf, 0);
+
+ return parse_fetch_memtags_reply (rs->buf, tags);
}
/* Implement the "store_memtags" target_ops method. */
@@ -14420,7 +14505,19 @@ bool
remote_target::store_memtags (CORE_ADDR address, size_t len,
const gdb::byte_vector &tags, int type)
{
- return 0;
+ /* Make sure the QMemTags packet is supported. */
+ if (!remote_memory_tagging_p ())
+ gdb_assert_not_reached ("remote store_memtags called with packet disabled");
+
+ struct remote_state *rs = get_remote_state ();
+
+ create_store_memtags_request (rs->buf, address, len, type, tags);
+
+ putpkt (rs->buf);
+ getpkt (&rs->buf, 0);
+
+ /* Verify if the request was successful. */
+ return packet_check_result (rs->buf.data ()) == PACKET_OK;
}
void _initialize_remote ();
@@ -14822,6 +14919,9 @@ Show the maximum size of the address (in bits) in a memory packet."), NULL,
add_packet_config_cmd (&remote_protocol_packets[PACKET_no_resumed],
"N stop reply", "no-resumed-stop-reply", 0);
+ add_packet_config_cmd (&remote_protocol_packets[PACKET_memory_tagging_feature],
+ "memory-tagging-feature", "memory-tagging-feature", 0);
+
/* Assert that we've registered "set remote foo-packet" commands
for all packet configs. */
{
--
2.25.1
next prev parent reply other threads:[~2020-12-30 15:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:38 [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation 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 ` Luis Machado via Gdb-patches [this message]
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
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=20201230153916.1586725-4-luis.machado@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=david.spickett@linaro.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