From: Alan Hayward <Alan.Hayward@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [RFC] AArch64 Memory tagging support
Date: Mon, 14 Oct 2019 13:12:00 -0000 [thread overview]
Message-ID: <24AA901B-D2DB-4DC6-923F-21581A4E3CB8@arm.com> (raw)
In-Reply-To: <87sgnz2lki.fsf@tromey.com>
> On 11 Oct 2019, at 19:17, Tom Tromey <tom@tromey.com> wrote:
>
>>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:
>
> Alan> This is a rough design for implementing ARMv8.5 MTE support in GDB,
> Alan> detailing the UI changes and sketching out the internals.
>
>
> Alan> Memory accesses inside GDB
>
> Alan> It should be enough for AArch64 to override target_xfer_partial.
> Alan> If the process is using memory tags, and the address contains a LT, then
> Alan> call PEEKDATATAG for the memory range being accessed and check if the access
> Alan> would succeed. If it doesn't then print just the first failure to the screen.
> Alan> If it does succeed then call the overridden function to access the memory.
>
> Another thing to consider is that you will probably want remote protocol
> support for this.
>
> Tom
Thanks,
I’ll make sure that gets added onto the design.
Alan.
next prev parent reply other threads:[~2019-10-14 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 10:39 Alan Hayward
2019-10-11 18:17 ` Tom Tromey
2019-10-14 13:12 ` Alan Hayward [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-21 10:39 Alan Hayward
2019-08-21 16:34 ` John Baldwin
2019-08-22 10:31 ` Alan Hayward
2020-04-13 14:57 ` Luis Machado
2020-06-05 12:55 ` Luis Machado
2020-06-16 16:34 ` 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=24AA901B-D2DB-4DC6-923F-21581A4E3CB8@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=tom@tromey.com \
/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).