From: Felix Willgerodt <felix.willgerodt@intel.com>
To: gdb-patches@sourceware.org, markus.t.metzger@intel.com, simark@simark.ca
Cc: "Willgerodt, Felix" <felix.willgerodt@intel.com>
Subject: [PATCH v9 00/10] Extensions for PTWRITE
Date: Tue, 4 Jul 2023 14:35:50 +0200 [thread overview]
Message-ID: <20230704123600.5944-1-felix.willgerodt@intel.com> (raw)
From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
v8 can be found here:
https://sourceware.org/pipermail/gdb-patches/2023-March/198177.html
I changed the following commits, mainly based on comments from Simon (thanks!):
* Patch 4:
Changed error message for going to an aux instruction.
* Patch 5:
I fixed the possibility of dangling aux objects in python, by erroring out
earlier and some restructuring.
* Patch 8:
I added parsing the config bit from a file provided by Linux, instead of
hardcoding it.
* Patch 9:
This changed a bit. I restructured the ptwrite filtering book-keeping and
registration. Now we use a factory pattern for registration. I also removed
the handler for inferior exit events in favour of one for the newly added
thread_exit event. That simplified the python file.
* Patch 10:
This is now using an optional for the filter function return value and is
printing the payload directly, if we don't have a filter or no Python
support. The documentation changed a lot due to the new way to register filters.
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 | 72 ++-
gdb/btrace.h | 41 +-
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 | 166 ++++++
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 | 58 ++
gdb/python/lib/gdb/ptwrite.py | 77 +++
gdb/python/py-record-btrace.c | 185 +++++-
gdb/python/py-record-btrace.h | 6 +
gdb/python/py-record.c | 78 ++-
gdb/python/py-record.h | 7 +
gdb/python/python-internal.h | 3 +
gdb/python/python.c | 2 +
gdb/record-btrace.c | 105 +++-
gdb/record.c | 10 +
gdb/record.h | 5 +-
gdb/remote.c | 33 ++
gdb/testsuite/gdb.btrace/i386-ptwrite.S | 550 ++++++++++++++++++
gdb/testsuite/gdb.btrace/ptwrite.c | 39 ++
gdb/testsuite/gdb.btrace/ptwrite.exp | 202 +++++++
gdb/testsuite/gdb.btrace/x86_64-ptwrite.S | 544 +++++++++++++++++
gdb/testsuite/gdb.python/py-record-btrace.exp | 4 +
gdb/testsuite/lib/gdb.exp | 72 +++
gdbserver/linux-low.cc | 3 +
gdbserver/server.cc | 18 +
gdbsupport/btrace-common.h | 6 +
gdbsupport/common.m4 | 2 +
gdbsupport/config.in | 3 +
gdbsupport/configure | 11 +
38 files changed, 2345 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.1
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 reply other threads:[~2023-07-04 12:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:35 Felix Willgerodt [this message]
2023-07-04 12:35 ` [PATCH v9 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2023-07-04 12:44 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2023-07-04 12:45 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2023-07-04 12:47 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2023-07-04 12:35 ` [PATCH v9 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2023-07-04 12:52 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-05 11:37 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2023-07-04 12:46 ` Eli Zaretskii
2023-07-05 10:03 ` Willgerodt, Felix
2023-07-05 11:35 ` Eli Zaretskii
2023-07-06 16:11 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-13 16:45 ` Tom Tromey
2023-07-14 11:07 ` Willgerodt, Felix
2023-07-04 12:35 ` [PATCH v9 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2023-07-04 12:49 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-04 12:35 ` [PATCH v9 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2023-07-04 12:35 ` [PATCH v9 09/10] btrace, python: Enable ptwrite filter registration Felix Willgerodt
2023-07-06 16:31 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-04 12:36 ` [PATCH v9 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2023-07-04 12:56 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-06 16:46 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-06 16:37 ` [PATCH v9 00/10] Extensions for PTWRITE Tom Tromey
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=20230704123600.5944-1-felix.willgerodt@intel.com \
--to=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=simark@simark.ca \
/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).