From: Eli Zaretskii <eliz@gnu.org>
To: Felix Willgerodt <felix.willgerodt@intel.com>
Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 01/12] btrace: Introduce auxiliary instructions.
Date: Mon, 14 Jun 2021 18:46:55 +0300 [thread overview]
Message-ID: <83sg1k5tzk.fsf@gnu.org> (raw)
In-Reply-To: <20210614145025.688566-2-felix.willgerodt@intel.com> (message from Felix Willgerodt via Gdb-patches on Mon, 14 Jun 2021 16:50:14 +0200)
> Date: Mon, 14 Jun 2021 16:50:14 +0200
> From: Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org>
>
> Auxiliary instructions are pseudo instructions pointing to auxiliary data.
> This auxiliary data can be printed in all commands displaying (record
> function-call-history, record instruction-history) or stepping through
> (stepi etc.) the execution history, which will be introduced in the next
> commits.
>
> This patch is in preparation for the new ptwrite feature, which is based on
> auxiliary instructions.
>
> gdb/ChangeLog:
> 2021-06-14 Felix Willgerodt <felix.willgerodt@intel.com>
>
> * btrace.c (btrace_clear_history): Clear aux_data.
> * btrace.h (btrace_insn_class): Add BTRACE_INSN_AUX.
> (btrace_insn): New union.
> (btrace_thread_info): New member aux_data.
>
> gdb/doc/ChangeLog:
> 2021-06-14 Felix Willgerodt <felix.willgerodt@intel.com>
>
> * gdb.texinfo (Process Record and Replay): Document printing of
> auxiliary information.
The documentation part is OK, thanks.
next prev parent reply other threads:[~2021-06-14 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 14:50 [PATCH v2 00/12] Extensions for PTWRITE Felix Willgerodt
2021-06-14 14:50 ` [PATCH v2 01/12] btrace: Introduce auxiliary instructions Felix Willgerodt
2021-06-14 15:46 ` Eli Zaretskii [this message]
2021-06-14 14:50 ` [PATCH v2 02/12] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2021-06-14 15:46 ` Eli Zaretskii
2021-06-14 14:50 ` [PATCH v2 03/12] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2021-06-14 15:50 ` Eli Zaretskii
2021-06-14 14:50 ` [PATCH v2 04/12] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
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=83sg1k5tzk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/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).