From: Luis Machado <luis.machado@arm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/aarch64] Add new debug architecture version
Date: Wed, 26 Apr 2023 07:01:29 +0100 [thread overview]
Message-ID: <63dabc36-6d32-abdf-bd74-09e4126dcdca@arm.com> (raw)
In-Reply-To: <20230425142252.754998-1-luis.machado@arm.com>
On 4/25/23 15:22, Luis Machado via Gdb-patches wrote:
> Teach gdb about a new debug architecture version for AArch64 (0x11).
>
> No user-visible changes.
>
> Regression-tested on aarch64-linux Ubuntu 20.04/22.04.
>
> Signed-off-by: Luis Machado <luis.machado@arm.com>
> ---
> gdb/nat/aarch64-hw-point.h | 2 ++
> gdb/nat/aarch64-linux-hw-point.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/gdb/nat/aarch64-hw-point.h b/gdb/nat/aarch64-hw-point.h
> index f4662f7c782..c19681422da 100644
> --- a/gdb/nat/aarch64-hw-point.h
> +++ b/gdb/nat/aarch64-hw-point.h
> @@ -59,6 +59,8 @@
> #define AARCH64_DEBUG_ARCH_V8_2 0x8
> #define AARCH64_DEBUG_ARCH_V8_4 0x9
> #define AARCH64_DEBUG_ARCH_V8_8 0x10
> +/* Armv8.9 debug architecture. */
> +#define AARCH64_DEBUG_ARCH_V8_9 0x11
>
> /* ptrace expects control registers to be formatted as follows:
>
> diff --git a/gdb/nat/aarch64-linux-hw-point.c b/gdb/nat/aarch64-linux-hw-point.c
> index ccb47cd5aa2..8cf8b31530c 100644
> --- a/gdb/nat/aarch64-linux-hw-point.c
> +++ b/gdb/nat/aarch64-linux-hw-point.c
> @@ -234,6 +234,8 @@ compatible_debug_arch (unsigned int debug_arch)
> return true;
> if (debug_arch == AARCH64_DEBUG_ARCH_V8_8)
> return true;
> + if (debug_arch == AARCH64_DEBUG_ARCH_V8_9)
> + return true;
>
> return false;
> }
Pushed now.
prev parent reply other threads:[~2023-04-26 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 14:22 Luis Machado
2023-04-26 6:01 ` Luis Machado [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=63dabc36-6d32-abdf-bd74-09e4126dcdca@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.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).