From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH v5 21/25] Documentation for the new mtag commands
Date: Thu, 4 Feb 2021 23:50:26 -0500 [thread overview]
Message-ID: <04ccafae-af53-d45d-2d44-d242b6eb9c19@polymtl.ca> (raw)
In-Reply-To: <20210127202112.2485702-22-luis.machado@linaro.org>
Maybe just update the subject to match the command name?
Simon
On 2021-01-27 3:21 p.m., Luis Machado via Gdb-patches wrote:
> Updates on v4:
>
> - Update the command names.
>
> --
>
> Document the new "memory-tag" command prefix and all of its subcommands.
>
> gdb/doc/ChangeLog:
>
> YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
>
> * gdb.texinfo (Memory Tagging): New subsection and node.
> (AArch64 Memory Tagging Extension): New subsection.
> ---
> gdb/doc/gdb.texinfo | 97 ++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 96 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index a10a74d0c3..f751bdf4d3 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -10848,6 +10848,66 @@ target supports computing the CRC checksum of a block of memory
> (@pxref{qCRC packet}).
> @end table
>
> +@node Memory Tagging
> +@subsection Memory Tagging
> +
> +Memory tagging is a memory protection technology that uses a pair of tags to
> +validate memory accesses through pointers. The tags are integer values
> +usually comprised of a few bits, depending on the architecture.
> +
> +There are two types of tags that are used in this setup: logical and
> +allocation. A logical tag is stored in the pointers themselves, usually at the
> +higher bits of the pointers. An allocation tag is the tag associated
> +with particular ranges of memory in the physical address space, against which
> +the logical tags from pointers are compared.
> +
> +The pointer tag (logical tag) must match the memory tag (allocation tag)
> +for the memory access to be valid. If the logical tag does not match the
> +allocation tag, that will raise a memory violation.
> +
> +Allocation tags cover multiple contiguous bytes of physical memory. This
> +range of bytes is called a memory tag granule and is architecture-specific.
> +For example, AArch64 has a tag granule of 16 bytes, meaning each allocation
> +tag spans 16 bytes of memory.
> +
> +If the underlying architecture supports memory tagging, like AArch64 MTE
> +or SPARC ADI do, @value{GDBN} can make use of it to validate addresses and
> +pointers against memory allocation tags.
> +
> +A command prefix of @code{memory-tag} gives access to the various memory tagging
> +commands.
> +
> +The @code{memory-tag} commands are the following:
> +
> +@table @code
> +@kindex memory-tag print-logical-tag
> +@item memory-tag print-logical-tag @var{address_expression}
> +Print the logical tag stored at the address given by @var{address_expression}.
> +@kindex memory-tag with-logical-tag
> +@item memory-tag with-logical-tag @var{address_expression} @var{tag_bytes}
> +Print the address given by @var{address_expression}, augmented with a logical
> +tag of @var{tag_bytes}.
> +@kindex memory-tag print-allocation-tag
> +@item memory-tag print-allocation-tag @var{address_expression}
> +Print the allocation tag associated with the memory address given by
> +@var{address_expression}.
> +@kindex memory-tag setatag
> +@item memory-tag setatag @var{starting_address} @var{length} @var{tag_bytes}
> +Set the allocation tag(s) for memory range @r{[}@var{starting_address},
> +@var{starting_address} + @var{length}@r{)} to @var{tag_bytes}.
> +@kindex memory-tag check
> +@item memory-tag check @var{address_expression}
> +Check that the logical tag stored at the address given by
> +@var{address_expression} matches the allocation tag for the same address.
> +
> +This essentially emulates the hardware validation that is done when tagged
> +memory is accessed through a pointer, but does not cause a memory fault as
> +it would during hardware validation.
> +
> +It can be used to inspect potential memory tagging violations in the running
> +process, before any faults get triggered.
> +@end table
> +
> @node Auto Display
> @section Automatic Display
> @cindex automatic display
> @@ -24966,6 +25026,41 @@ When GDB prints a backtrace, any addresses that required unmasking will be
> postfixed with the marker [PAC]. When using the MI, this is printed as part
> of the @code{addr_flags} field.
>
> +@subsubsection AArch64 Memory Tagging Extension.
> +@cindex AArch64 Memory Tagging Extension.
> +
> +When @value{GDBN} is debugging the AArch64 architecture, the program is
> +using the v8.5-A feature Memory Tagging Extension (MTE) and there is support
> +in the kernel for MTE, @value{GDBN} will make memory tagging functionality
> +available for inspection and editing of logical and allocation tags.
> +@xref{Memory Tagging}.
> +
> +To aid debugging, @value{GDBN} will output additional information when SIGSEGV
> +signals are generated as a result of memory tag failures.
> +
> +If the tag violation is synchronous, the following will be shown:
> +
> +@smallexample
> +Program received signal SIGSEGV, Segmentation fault
> +Memory tag violation while accessing address 0x0000fffff7ff8000
> +Allocation tag 0x0000000000000001.
> +@end smallexample
> +
> +If the tag violation is asynchronous, the fault address is not available.
> +In this case @value{GDBN} will show the following:
> +
> +@smallexample
> +Program received signal SIGSEGV, Segmentation fault
> +Memory tag violation
> +Fault address unavailable.
> +@end smallexample
> +
> +A special register, @code{tag_ctl}, is made available through the
> +@code{org.gnu.gdb.aarch64.mte} feature. This register exposes some
> +options that can be controlled at runtime and emulates the @code{prctl}
> +option @code{PR_SET_TAGGED_ADDR_CTRL}. For further information, see the
> +documentation in the Linux kernel.
> +
> @node i386
> @subsection x86 Architecture-specific Issues
>
> @@ -41023,7 +41118,7 @@ does not have any restriction on alignment or size.
>
> @var{length} is the length, in bytes, of the memory range.
>
> -@var{type} is the type of tag the request wants to fetch. The typeis a signed
> +@var{type} is the type of tag the request wants to fetch. The type is a signed
> integer.
>
> @var{tag bytes} is a sequence of hex encoded uninterpreted bytes which will be
>
next prev parent reply other threads:[~2021-02-05 4:50 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
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 [this message]
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=04ccafae-af53-d45d-2d44-d242b6eb9c19@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).