From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v5 02/10] btrace: Enable auxiliary instructions in record instruction-history.
Date: Tue, 28 Jun 2022 09:10:24 +0000 [thread overview]
Message-ID: <DM8PR11MB574934A33E1FCFFA0E1F7F7CDEB89@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220622114340.55830-3-felix.willgerodt@intel.com>
Hello Felix,
>Print the auxiliary data when a btrace_insn of type BTRACE_INSN_AUX
>is encountered in the instruction-history. Printing is active by default,
>it can be silenced with the /a modifier.
I find it a bit strange that /a disables some output instead of enabling it.
Should we change the default? I'd probably always use it, but then, I
also always supply /cli to 'record function-call-history'.
>This patch is in preparation for the new ptwrite feature, which is based on
>auxiliary instructions.
>---
> gdb/disasm-flags.h | 1 +
> gdb/doc/gdb.texinfo | 3 +++
> gdb/record-btrace.c | 14 ++++++++++++++
> gdb/record.c | 5 +++++
> 4 files changed, 23 insertions(+)
>+ else if (insn->iclass == BTRACE_INSN_AUX)
>+ {
>+ if ((flags & DISASSEMBLY_OMIT_AUX_INSN) != 0)
>+ continue;
>+
>+ uiout->field_fmt ("insn-number", "%u", btrace_insn_number (&it));
>+ uiout->text ("\t");
>+ uiout->spaces (3);
>+ uiout->text ("[");
>+ uiout->field_fmt (
>+ "aux-data", "%s",
>+ it.btinfo->aux_data.at (insn->aux_data_index).c_str ());
The formatting is a bit unusual.
regards,
markus.
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-06-28 9:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 11:43 [PATCH v5 00/10] Extensions for PTWRITE Felix Willgerodt
2022-06-22 11:43 ` [PATCH v5 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T [this message]
2022-06-28 11:28 ` Willgerodt, Felix
2022-06-29 10:43 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T
2022-09-19 8:59 ` Willgerodt, Felix
2022-06-22 11:43 ` [PATCH v5 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-07-11 12:48 ` Willgerodt, Felix
2022-06-22 11:43 ` [PATCH v5 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2022-06-28 9:12 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 09/10] btrace, python: Enable ptwrite filter registration Felix Willgerodt
2022-06-28 13:59 ` Metzger, Markus T
2022-07-11 12:48 ` Willgerodt, Felix
2022-07-12 12:23 ` Metzger, Markus T
2022-07-13 8:49 ` Willgerodt, Felix
2022-07-13 15:20 ` Metzger, Markus T
2022-07-26 14:08 ` Willgerodt, Felix
2022-09-14 8:37 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2022-06-29 13:35 ` Metzger, Markus T
2022-09-19 8:59 ` 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=DM8PR11MB574934A33E1FCFFA0E1F7F7CDEB89@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=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).