Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gustavo Romero <gustavo.romero@linaro.org>
To: Luis Machado <luis.machado@arm.com>, gdb-patches@sourceware.org
Cc: thiago.bauermann@linaro.org
Subject: Re: [PATCH 0/4] Add another way to check for MTE-tagged addresses on remote targets
Date: Thu, 28 Mar 2024 19:59:08 -0300	[thread overview]
Message-ID: <e002b8f8-532f-5b03-9223-a49c4f2f5e0b@linaro.org> (raw)
In-Reply-To: <905a394c-c6d3-4721-bc60-dfe31dcc4a64@arm.com>

Hi Luis,

On 3/28/24 10:00 AM, Luis Machado wrote:
> Hi Gustavo,
> 
> On 3/28/24 07:00, Gustavo Romero wrote:
>> This series introduces a new method to check for MTE-tagged addresses on
>> remote targets.
>>
>> A new remote packet, qMemTagAddrCheck, is introduced, along with a new
>> remote feature associated with it, 'memory-tagging-check-add+'. Only
>> when 'memory-tagging-check-add+' feature is advertised GDB will use the
>> new packet to query if an address is tagged.
>>
>> This new mechanism allows for checking MTE addresses in an OS-agnostic
>> way, which is necessary when debugging targets that do not support
>> '/proc/<PID>/smaps', as the current method of reading smaps contents
>> fails in such cases.
>>
>> Cheers,
>> Gustavo
>>
>> Gustavo Romero (4):
>>    gdb: aarch64: Remove MTE address checking from get_memtag
>>    gdb: aarch64: Move MTE address check out of set_memtag
>>    gdb: aarch64: Remove MTE address checking from memtag_matches_p
>>    gdb: Add new remote packet to check if address is tagged
>>
>>   gdb/aarch64-linux-nat.c   |  8 +++++
>>   gdb/aarch64-linux-tdep.c  | 22 +++-----------
>>   gdb/arch-utils.c          |  2 +-
>>   gdb/arch-utils.h          |  2 +-
>>   gdb/corelow.c             |  8 +++++
>>   gdb/gdbarch-gen.h         |  4 +--
>>   gdb/gdbarch.c             |  2 +-
>>   gdb/gdbarch_components.py |  2 +-
>>   gdb/printcmd.c            | 29 +++++++++++-------
>>   gdb/remote.c              | 62 +++++++++++++++++++++++++++++++++++++++
>>   gdb/target-delegates.c    | 28 ++++++++++++++++++
>>   gdb/target.c              |  6 ++++
>>   gdb/target.h              |  6 ++++
>>   13 files changed, 147 insertions(+), 34 deletions(-)
>>
> 
> Thanks for the series. Please bear with me while I go through it and try it on my end.

Thanks a lot! I've sent a v2 [0] that fixes a build error and also has
instructions on how to build a QEMU gdbstub that supports the new packet
so it's possible to test the remote target with this series.


Cheers,
Gustavo

[0] https://sourceware.org/pipermail/gdb-patches/2024-March/207650.html

      reply	other threads:[~2024-03-28 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  7:00 Gustavo Romero
2024-03-28  7:00 ` [PATCH 1/4] gdb: aarch64: Remove MTE address checking from get_memtag Gustavo Romero
2024-03-28  7:00 ` [PATCH 2/4] gdb: aarch64: Move MTE address check out of set_memtag Gustavo Romero
2024-03-28  7:00 ` [PATCH 3/4] gdb: aarch64: Remove MTE address checking from memtag_matches_p Gustavo Romero
2024-03-28  7:00 ` [PATCH 4/4] gdb: Add new remote packet to check if address is tagged Gustavo Romero
2024-03-28 13:00 ` [PATCH 0/4] Add another way to check for MTE-tagged addresses on remote targets Luis Machado
2024-03-28 22:59   ` Gustavo Romero [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=e002b8f8-532f-5b03-9223-a49c4f2f5e0b@linaro.org \
    --to=gustavo.romero@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=thiago.bauermann@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