Re: [PATCH v2] gdb, btrace: support libipt v2.2 events

[Eli Zaretskii <eliz@gnu.org>]

> From: Markus Metzger <markus.t.metzger@intel.com>
> Cc: Keith Seitz <keiths@redhat.com>
> Date: Mon,  4 May 2026 07:16:36 +0000
> 
> Add support for printing new events added in libipt v2.2 originating from
> Event Tracing in combination with Flexible Return and Event Delivery
> (FRED) and from Trigger Tracing.
> 
> Reviewed-By: Keith Seitz <keiths@redhat.com>
> ---
>  gdb/NEWS     |  3 +++
>  gdb/btrace.c | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 56 insertions(+)
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index e233906153a..4464135ef71 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -75,6 +75,9 @@
>  * The Windows native target now supports scheduler-locking.  E.g.,
>    "set scheduler-locking on" now works.  Previously it gave an error.
>  
> +* GDB now supports libipt v2.2 events originating from Event Tracing on a
> +  FRED-enabled system and from Trigger Tracing.

I think it would be good to mention the "maint btrace" command here,
since AFAIU that's where these events will appear.  Perhaps also
update the manual with what these events will look like in btrace?

Thanks

Reviewed-By: Eli Zaretskii <eliz@gnu.org>