From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PING] [PATCH v7 00/10] Extensions for PTWRITE
Date: Wed, 9 Nov 2022 13:16:23 +0000 [thread overview]
Message-ID: <MN2PR11MB45664CC9E61FA737284FBCE68E3E9@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221021115947.359223-1-felix.willgerodt@intel.com>
*Ping*
Thanks,
Felix
> -----Original Message-----
> From: Willgerodt, Felix <felix.willgerodt@intel.com>
> Sent: Freitag, 21. Oktober 2022 14:00
> To: gdb-patches@sourceware.org; Metzger, Markus T
> <markus.t.metzger@intel.com>
> Cc: Willgerodt, Felix <felix.willgerodt@intel.com>
> Subject: [PATCH v7 00/10] Extensions for PTWRITE
>
> Eli already approved the documentation parts.
> Markus reviewed every patch and approved the btrace bits.
> The only thing that is missing is a global maintainers approval for
> the Python bits.
>
> Compared to v6 I only addressed the nits that Eli and Markus pointed out.
>
> The older revisions can be found here:
> V1: https://sourceware.org/pipermail/gdb-patches/2019-May/157933.html
> V2: https://sourceware.org/pipermail/gdb-patches/2021-June/179908.html
> V3: https://sourceware.org/pipermail/gdb-patches/2021-June/180035.html
> v4: https://sourceware.org/pipermail/gdb-patches/2022-May/188772.html
> v5: https://sourceware.org/pipermail/gdb-patches/2022-June/190236.html
> v6: https://sourceware.org/pipermail/gdb-patches/2022-
> September/191866.html
>
> Thanks,
> Felix
>
> Felix Willgerodt (10):
> btrace: Introduce auxiliary instructions.
> btrace: Enable auxiliary instructions in record instruction-history.
> btrace: Enable auxiliary instructions in record function-call-history.
> btrace: Handle stepping and goto for auxiliary instructions.
> python: Introduce gdb.RecordAuxiliary class.
> python: Add clear() to gdb.Record.
> btrace, gdbserver: Add ptwrite to btrace_config_pt.
> btrace, linux: Enable ptwrite packets.
> btrace, python: Enable ptwrite filter registration.
> btrace: Extend ptwrite event decoding.
>
> gdb/NEWS | 7 +
> gdb/btrace.c | 68 ++-
> gdb/btrace.h | 38 +-
> gdb/config.in | 3 +
> gdb/configure | 11 +
> gdb/data-directory/Makefile.in | 1 +
> gdb/disasm-flags.h | 1 +
> gdb/doc/gdb.texinfo | 32 +-
> gdb/doc/python.texi | 168 ++++++
> gdb/extension-priv.h | 5 +
> gdb/extension.c | 13 +
> gdb/extension.h | 3 +
> gdb/features/btrace-conf.dtd | 1 +
> gdb/guile/guile.c | 1 +
> gdb/nat/linux-btrace.c | 29 +
> gdb/python/lib/gdb/ptwrite.py | 80 +++
> gdb/python/py-record-btrace.c | 136 ++++-
> gdb/python/py-record-btrace.h | 11 +
> gdb/python/py-record.c | 89 ++-
> gdb/python/py-record.h | 3 +
> gdb/python/python-internal.h | 3 +
> gdb/python/python.c | 2 +
> gdb/record-btrace.c | 107 +++-
> gdb/record.c | 10 +
> gdb/record.h | 5 +-
> gdb/remote.c | 30 +
> gdb/testsuite/gdb.btrace/i386-ptwrite.S | 550 ++++++++++++++++++
> gdb/testsuite/gdb.btrace/ptwrite.c | 39 ++
> gdb/testsuite/gdb.btrace/ptwrite.exp | 209 +++++++
> gdb/testsuite/gdb.btrace/x86_64-ptwrite.S | 544 +++++++++++++++++
> gdb/testsuite/gdb.python/py-record-btrace.exp | 6 +-
> gdb/testsuite/lib/gdb.exp | 74 +++
> gdbserver/linux-low.cc | 2 +
> gdbserver/server.cc | 18 +
> gdbsupport/btrace-common.h | 6 +
> gdbsupport/common.m4 | 2 +
> gdbsupport/config.in | 3 +
> gdbsupport/configure | 11 +
> 38 files changed, 2286 insertions(+), 35 deletions(-)
> create mode 100644 gdb/python/lib/gdb/ptwrite.py
> create mode 100644 gdb/testsuite/gdb.btrace/i386-ptwrite.S
> create mode 100644 gdb/testsuite/gdb.btrace/ptwrite.c
> create mode 100644 gdb/testsuite/gdb.btrace/ptwrite.exp
> create mode 100644 gdb/testsuite/gdb.btrace/x86_64-ptwrite.S
>
> --
> 2.34.3
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-11-09 13:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:59 Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 13:19 ` Eli Zaretskii
2022-10-21 11:59 ` [PATCH v7 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-10-21 11:59 ` [PATCH v7 09/10] btrace, python: Enable ptwrite filter registration Felix Willgerodt
2022-10-21 11:59 ` Felix Willgerodt
2022-11-09 13:16 ` Willgerodt, Felix [this message]
2022-11-17 9:18 [PING] [PATCH v7 00/10] Extensions for PTWRITE Willgerodt, Felix
2022-11-30 8:40 ` Willgerodt, Felix
2022-12-07 8:45 ` Willgerodt, Felix
2022-12-14 13:23 ` Willgerodt, Felix
2023-01-09 12:21 ` Willgerodt, Felix
2023-01-16 9:30 ` Willgerodt, Felix
2023-01-23 10:47 ` Willgerodt, Felix
2023-01-30 13:07 ` Willgerodt, Felix
2023-02-07 12:22 ` Willgerodt, Felix
2023-02-20 12:51 ` Willgerodt, Felix
2023-03-06 9:02 ` Willgerodt, Felix
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=MN2PR11MB45664CC9E61FA737284FBCE68E3E9@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.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).