Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5 01/25] New target methods for memory tagging support
Date: Thu, 28 Jan 2021 07:02:45 -0300	[thread overview]
Message-ID: <89b73bed-694b-f61c-b377-a2dd0c944984@linaro.org> (raw)
In-Reply-To: <YBH2pWVtaY61IsFI@Plymouth>

On 1/27/21 8:26 PM, Lancelot SIX wrote:
> On Wed, Jan 27, 2021 at 05:20:48PM -0300, 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;
>> +
>>   public: /* Remote specific methods.  */
>>   
>>     void remote_download_command_source (int num, ULONGEST addr,
>> @@ -14472,6 +14480,32 @@ show_remote_timeout (struct ui_file *file, int from_tty,
>>   		    value);
>>   }
>>   
>> +/* Implement the "supports_memory_tagging" target_ops method.  */
>> +
>> +bool
>> +remote_target::supports_memory_tagging ()
>> +{
>> +  return false;
>> +}
>> +
>> +/* Implement the "fetch_memtags" target_ops method.  */
>> +
>> +bool
>> +remote_target::fetch_memtags (CORE_ADDR address, size_t len,
>> +			      gdb::byte_vector &tags, int type)
>> +{
>> +  return 0;
> 
> If you return a bool, you should probably return false.
> 
>> +}
>> +
>> +/* Implement the "store_memtags" target_ops method.  */
>> +
>> +bool
>> +remote_target::store_memtags (CORE_ADDR address, size_t len,
>> +			      const gdb::byte_vector &tags, int type)
>> +{
>> +  return 0;
> 
> Similarly, return false.
> 

Missed it, since this gets replaced by the full implementation later. 
I'll address it locally. Thanks for spotting that.

>> +}
>> +
>>   void _initialize_remote ();
>>   void
>>   _initialize_remote ()
>> diff --git a/gdb/target-debug.h b/gdb/target-debug.h
>> index 6910338865..5bc384a39a 100644
>> --- a/gdb/target-debug.h
>> +++ b/gdb/target-debug.h
>> @@ -212,4 +212,28 @@ target_debug_print_signals (gdb::array_view<const unsigned char> sigs)
>>     fputs_unfiltered (" }", gdb_stdlog);
>>   }
>>   
>> +static void
>> +target_debug_print_size_t (size_t size)
>> +{
>> +  fprintf_unfiltered (gdb_stdlog, "%s", pulongest (size));
>> +}
>> +
>> +static void
>> +target_debug_print_const_gdb_byte_vector_r (const gdb::byte_vector &vector)
>> +{
>> +  fputs_unfiltered ("{", gdb_stdlog);
>> +
>> +  for (size_t i = 0; i < vector.size (); i++)
>> +    {
>> +      fprintf_unfiltered (gdb_stdlog, " %s",
>> +			  phex_nz (vector[i], 1));
>> +    }
>> +  fputs_unfiltered (" }", gdb_stdlog);
>> +}
>> +
>> +static void
>> +target_debug_print_gdb_byte_vector_r (gdb::byte_vector &vector)
>> +{
>> +  target_debug_print_gdb_byte_vector_r (vector);
> 
> I think you meant target_debug_print_const_gdb_byte_vector_r here.
> 

That's correct. I'll fix this locally.

Thanks!

> Lancelot.
> 
>> +}
>>   #endif /* TARGET_DEBUG_H */
>> diff --git a/gdb/target-delegates.c b/gdb/target-delegates.c
>> index 437b19b858..e4563e4dac 100644
>> --- a/gdb/target-delegates.c
>> +++ b/gdb/target-delegates.c
>> @@ -173,6 +173,9 @@ struct dummy_target : public target_ops
>>     const struct frame_unwind *get_tailcall_unwinder () override;
>>     void prepare_to_generate_core () override;
>>     void done_generating_core () override;
>> +  bool supports_memory_tagging () override;
>> +  bool fetch_memtags (CORE_ADDR arg0, size_t arg1, gdb::byte_vector &arg2, int arg3) override;
>> +  bool store_memtags (CORE_ADDR arg0, size_t arg1, const gdb::byte_vector &arg2, int arg3) override;
>>   };
>>   
>>   struct debug_target : public target_ops
>> @@ -344,6 +347,9 @@ struct debug_target : public target_ops
>>     const struct frame_unwind *get_tailcall_unwinder () override;
>>     void prepare_to_generate_core () override;
>>     void done_generating_core () override;
>> +  bool supports_memory_tagging () override;
>> +  bool fetch_memtags (CORE_ADDR arg0, size_t arg1, gdb::byte_vector &arg2, int arg3) override;
>> +  bool store_memtags (CORE_ADDR arg0, size_t arg1, const gdb::byte_vector &arg2, int arg3) override;
>>   };
>>   
>>   void
>> @@ -4413,3 +4419,92 @@ debug_target::done_generating_core ()
>>     fputs_unfiltered (")\n", gdb_stdlog);
>>   }
>>   
>> +bool
>> +target_ops::supports_memory_tagging ()
>> +{
>> +  return this->beneath ()->supports_memory_tagging ();
>> +}
>> +
>> +bool
>> +dummy_target::supports_memory_tagging ()
>> +{
>> +  return false;
>> +}
>> +
>> +bool
>> +debug_target::supports_memory_tagging ()
>> +{
>> +  bool result;
>> +  fprintf_unfiltered (gdb_stdlog, "-> %s->supports_memory_tagging (...)\n", this->beneath ()->shortname ());
>> +  result = this->beneath ()->supports_memory_tagging ();
>> +  fprintf_unfiltered (gdb_stdlog, "<- %s->supports_memory_tagging (", this->beneath ()->shortname ());
>> +  fputs_unfiltered (") = ", gdb_stdlog);
>> +  target_debug_print_bool (result);
>> +  fputs_unfiltered ("\n", gdb_stdlog);
>> +  return result;
>> +}
>> +
>> +bool
>> +target_ops::fetch_memtags (CORE_ADDR arg0, size_t arg1, gdb::byte_vector &arg2, int arg3)
>> +{
>> +  return this->beneath ()->fetch_memtags (arg0, arg1, arg2, arg3);
>> +}
>> +
>> +bool
>> +dummy_target::fetch_memtags (CORE_ADDR arg0, size_t arg1, gdb::byte_vector &arg2, int arg3)
>> +{
>> +  tcomplain ();
>> +}
>> +
>> +bool
>> +debug_target::fetch_memtags (CORE_ADDR arg0, size_t arg1, gdb::byte_vector &arg2, int arg3)
>> +{
>> +  bool result;
>> +  fprintf_unfiltered (gdb_stdlog, "-> %s->fetch_memtags (...)\n", this->beneath ()->shortname ());
>> +  result = this->beneath ()->fetch_memtags (arg0, arg1, arg2, arg3);
>> +  fprintf_unfiltered (gdb_stdlog, "<- %s->fetch_memtags (", this->beneath ()->shortname ());
>> +  target_debug_print_CORE_ADDR (arg0);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_size_t (arg1);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_gdb_byte_vector_r (arg2);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_int (arg3);
>> +  fputs_unfiltered (") = ", gdb_stdlog);
>> +  target_debug_print_bool (result);
>> +  fputs_unfiltered ("\n", gdb_stdlog);
>> +  return result;
>> +}
>> +
>> +bool
>> +target_ops::store_memtags (CORE_ADDR arg0, size_t arg1, const gdb::byte_vector &arg2, int arg3)
>> +{
>> +  return this->beneath ()->store_memtags (arg0, arg1, arg2, arg3);
>> +}
>> +
>> +bool
>> +dummy_target::store_memtags (CORE_ADDR arg0, size_t arg1, const gdb::byte_vector &arg2, int arg3)
>> +{
>> +  tcomplain ();
>> +}
>> +
>> +bool
>> +debug_target::store_memtags (CORE_ADDR arg0, size_t arg1, const gdb::byte_vector &arg2, int arg3)
>> +{
>> +  bool result;
>> +  fprintf_unfiltered (gdb_stdlog, "-> %s->store_memtags (...)\n", this->beneath ()->shortname ());
>> +  result = this->beneath ()->store_memtags (arg0, arg1, arg2, arg3);
>> +  fprintf_unfiltered (gdb_stdlog, "<- %s->store_memtags (", this->beneath ()->shortname ());
>> +  target_debug_print_CORE_ADDR (arg0);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_size_t (arg1);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_const_gdb_byte_vector_r (arg2);
>> +  fputs_unfiltered (", ", gdb_stdlog);
>> +  target_debug_print_int (arg3);
>> +  fputs_unfiltered (") = ", gdb_stdlog);
>> +  target_debug_print_bool (result);
>> +  fputs_unfiltered ("\n", gdb_stdlog);
>> +  return result;
>> +}
>> +
>> diff --git a/gdb/target.h b/gdb/target.h
>> index 917476d16a..19395f1258 100644
>> --- a/gdb/target.h
>> +++ b/gdb/target.h
>> @@ -1260,6 +1260,38 @@ struct target_ops
>>       /* Cleanup after generating a core file.  */
>>       virtual void done_generating_core ()
>>         TARGET_DEFAULT_IGNORE ();
>> +
>> +    /* Returns true if the target supports memory tagging, false otherwise.  */
>> +    virtual bool supports_memory_tagging ()
>> +      TARGET_DEFAULT_RETURN (false);
>> +
>> +    /* Return the allocated memory tags of type TYPE associated with
>> +       [ADDRESS, ADDRESS + LEN) in TAGS.
>> +
>> +       LEN is the number of bytes in the memory range.  TAGS is a vector of
>> +       bytes containing the tags found in the above memory range.
>> +
>> +       It is up to the architecture/target to interpret the bytes in the TAGS
>> +       vector and read the tags appropriately.
>> +
>> +       Returns true if fetching the tags succeeded and false otherwise.  */
>> +    virtual bool fetch_memtags (CORE_ADDR address, size_t len,
>> +			       gdb::byte_vector &tags, int type)
>> +      TARGET_DEFAULT_NORETURN (tcomplain ());
>> +
>> +    /* Write the allocation tags of type TYPE contained in TAGS to the memory
>> +       range [ADDRESS, ADDRESS + LEN).
>> +
>> +       LEN is the number of bytes in the memory range.  TAGS is a vector of
>> +       bytes containing the tags to be stored to the memory range.
>> +
>> +       It is up to the architecture/target to interpret the bytes in the TAGS
>> +       vector and store them appropriately.
>> +
>> +       Returns true if storing the tags succeeded and false otherwise.  */
>> +    virtual bool store_memtags (CORE_ADDR address, size_t len,
>> +			       const gdb::byte_vector &tags, int type)
>> +      TARGET_DEFAULT_NORETURN (tcomplain ());
>>     };
>>   
>>   /* Deleter for std::unique_ptr.  See comments in
>> @@ -2312,6 +2344,15 @@ extern gdb::unique_xmalloc_ptr<char> target_fileio_read_stralloc
>>   #define target_augmented_libraries_svr4_read() \
>>     (current_top_target ()->augmented_libraries_svr4_read) ()
>>   
>> +#define target_supports_memory_tagging() \
>> +  ((current_top_target ()->supports_memory_tagging) ())
>> +
>> +#define target_fetch_memtags(address, len, tags, type) \
>> +  (current_top_target ()->fetch_memtags) ((address), (len), (tags), (type))
>> +
>> +#define target_store_memtags(address, len, tags, type) \
>> +  (current_top_target ()->store_memtags) ((address), (len), (tags), (type))
>> +
>>   /* Command logging facility.  */
>>   
>>   #define target_log_command(p)					\
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2021-01-28 10:02 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 via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 01/25] New target methods for memory tagging support Luis Machado via Gdb-patches
2021-01-27 23:26   ` Lancelot SIX via Gdb-patches
2021-01-28 10:02     ` Luis Machado via Gdb-patches [this message]
2021-02-05  2:31   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 02/25] New gdbarch memory tagging hooks Luis Machado via Gdb-patches
2021-02-05  2:38   ` Simon Marchi via Gdb-patches
2021-02-05  3:58   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 03/25] Add GDB-side remote target support for memory tagging Luis Machado via Gdb-patches
2021-02-05  2:48   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 04/25] Unit testing for GDB-side remote memory tagging handling Luis Machado via Gdb-patches
2021-02-05  2:50   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 05/25] GDBserver remote packet support for memory tagging Luis Machado via Gdb-patches
2021-02-05  2:56   ` Simon Marchi via Gdb-patches
2021-02-05 12:38     ` Luis Machado via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 06/25] Unit tests for gdbserver memory tagging remote packets Luis Machado via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 07/25] Documentation for " Luis Machado via Gdb-patches
2021-01-28  3:30   ` Eli Zaretskii via Gdb-patches
2021-01-28  9:58     ` Luis Machado via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 08/25] AArch64: Add MTE CPU feature check support Luis Machado via Gdb-patches
2021-02-05  3:05   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 09/25] AArch64: Add target description/feature for MTE registers Luis Machado via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 10/25] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 11/25] AArch64: Add MTE ptrace requests Luis Machado via Gdb-patches
2021-02-05  3:13   ` Simon Marchi via Gdb-patches
2021-01-27 20:20 ` [PATCH v5 12/25] AArch64: Implement memory tagging target methods for AArch64 Luis Machado via Gdb-patches
2021-02-05  3:30   ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 13/25] Convert char array to std::string in linux_find_memory_regions_full Luis Machado via Gdb-patches
2021-02-05  3:32   ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 14/25] Refactor parsing of /proc/<pid>/smaps Luis Machado via Gdb-patches
2021-02-05  3:38   ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 15/25] AArch64: Implement the memory tagging gdbarch hooks Luis Machado via Gdb-patches
2021-02-05  4:09   ` Simon Marchi via Gdb-patches
2021-02-05 14:05     ` Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 16/25] AArch64: Add unit testing for logical tag set/get operations Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 17/25] AArch64: Report tag violation error information Luis Machado via Gdb-patches
2021-02-05  4:22   ` Simon Marchi via Gdb-patches
2021-02-05 14:59     ` Luis Machado via Gdb-patches
2021-02-05 16:13       ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 18/25] AArch64: Add gdbserver MTE support Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 19/25] AArch64: Add MTE register set support for core files Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 20/25] New memory-tag commands Luis Machado via Gdb-patches
2021-02-05  4:49   ` Simon Marchi via Gdb-patches
2021-02-05  4:52     ` Simon Marchi via Gdb-patches
2021-02-08 18:59     ` Luis Machado via Gdb-patches
2021-03-23 21:46       ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 21/25] Documentation for the new mtag commands Luis Machado via Gdb-patches
2021-01-28  3:31   ` Eli Zaretskii via Gdb-patches
2021-02-05  4:50   ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 22/25] Extend "x" and "print" commands to support memory tagging Luis Machado via Gdb-patches
2021-02-05  5:02   ` Simon Marchi via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 23/25] Document new "x" and "print" memory tagging extensions Luis Machado via Gdb-patches
2021-01-28  3:31   ` Eli Zaretskii via Gdb-patches
2021-02-05  5:04   ` Simon Marchi via Gdb-patches
2021-02-08 20:44     ` Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 24/25] Add NEWS entry Luis Machado via Gdb-patches
2021-01-28  3:32   ` Eli Zaretskii via Gdb-patches
2021-02-05  5:06   ` Simon Marchi via Gdb-patches
2021-02-08 20:44     ` Luis Machado via Gdb-patches
2021-01-27 20:21 ` [PATCH v5 25/25] Add memory tagging testcases Luis Machado via Gdb-patches
2021-02-04 14:18 ` [PING] [PATCH v5 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado 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=89b73bed-694b-f61c-b377-a2dd0c944984@linaro.org \
    --to=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --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