From: Tom Tromey <tom@tromey.com>
To: Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org>
Cc: markus.t.metzger@intel.com, simark@simark.ca,
Felix Willgerodt <felix.willgerodt@intel.com>
Subject: Re: [PATCH v9 09/10] btrace, python: Enable ptwrite filter registration.
Date: Thu, 06 Jul 2023 10:31:26 -0600 [thread overview]
Message-ID: <87sfa1t31d.fsf@tromey.com> (raw)
In-Reply-To: <20230704123600.5944-10-felix.willgerodt@intel.com> (Felix Willgerodt via Gdb-patches's message of "Tue, 4 Jul 2023 14:35:59 +0200")
>>>>> Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org> writes:
> By default GDB will be printing the hex payload of the ptwrite package as
> auxiliary information. To customize this, the user can register a ptwrite
> filter function in python, that takes the payload and the PC as arguments and
> returns a string which will be printed instead. Registering the filter
> function is done using a factory pattern to make per-thread filtering easier.
Thank you for the patch.
> + /* Function pointer to the ptwrite callback. Returns the string returned
> + by the ptwrite filter function. */
> + gdb::optional<std::string> (*ptw_callback_fun) (const uint64_t payload,
> + const uint64_t ip,
> + const void *ptw_context)
> + = nullptr;
> +
> + /* Context for the ptw_callback_fun. */
> + void *ptw_context = nullptr;
I tend to think it's better to use std::function here, rather than the
C-style pointer-and-data approach.
> diff --git a/gdb/python/lib/gdb/ptwrite.py b/gdb/python/lib/gdb/ptwrite.py
I gather the new stuff is documented in the next patch.
> +# _ptwrite_filter contains the per thread copies of the filter function.
> +# The keys are tuples of inferior id and thread id.
> +# The filter functions are created for each thread by calling the
> +# _ptwrite_filter_factory.
> +_ptwrite_filter = {}
It seems like when an inferior or thread is destroyed, the entries
should be removed from this map.
> + gdbpy_ref<> py_payload (PyLong_FromUnsignedLongLong (payload));
> + gdbpy_ref<> py_ip (PyLong_FromUnsignedLongLong (ip));
Both of these calls require null checks.
> + gdbpy_ref<> py_result (PyObject_CallFunctionObjArgs ((PyObject *) ptw_filter,
> + py_payload.get (),
> + py_ip.get (),
> + nullptr));
> +
> + if (PyErr_Occurred ())
It's more idiomatic to check == nullptr than PyErr_Occurred.
> + result = gdbpy_obj_to_string (py_result.get ()).get ();
> +
> + if (PyErr_Occurred ())
Here too.
Tom
next prev parent reply other threads:[~2023-07-06 16:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:35 [PATCH v9 00/10] Extensions for PTWRITE Felix Willgerodt
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 [this message]
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=87sfa1t31d.fsf@tromey.com \
--to=tom@tromey.com \
--cc=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).