From: Eli Zaretskii <eliz@gnu.org>
To: Zied Guermazi <zied.guermazi@trande.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/7] add btrace coresight related commands
Date: Wed, 31 Mar 2021 09:32:02 +0300 [thread overview]
Message-ID: <83v997j0kd.fsf@gnu.org> (raw)
In-Reply-To: <20210331025234.518688-3-zied.guermazi@trande.de> (message from Zied Guermazi on Wed, 31 Mar 2021 04:52:29 +0200)
> From: Zied Guermazi <zied.guermazi@trande.de>
> Date: Wed, 31 Mar 2021 04:52:29 +0200
> Cc: Zied Guermazi <zied.guermazi@trande.de>
>
> gdb/ChangeLog
>
> * NEWS: list new commands for extending btrace
> to support using ARM CoreSight Traces.
> * record-btrace.c (record_btrace_print_etm_conf): New.
> (record_btrace_print_conf): handle BTRACE_FORMAT_ETM.
> (cmd_record_btrace_etm_start): New.
> (cmd_record_btrace_start): handle starting ETM tracing.
> (cmd_show_record_btrace_cpu): extend for ARM cpus.
> (show_record_etm_buffer_size_value): New.
> (_initialize_record_btrace): add commands for ETM traces.
> (record_start): add starting ETM traces.
>
> gdb/doc/ChangeLog
>
> * gdb.texinfo (Process Record and Replay): Document extending
> GDB btrace commands to support using ARM CoreSight traces.
>
> gdbsupport/ChangeLog
>
> * btrace-common.h (btrace_format): add BTRACE_FORMAT_ETM
> to the enum.
> (btrace_config_etm): new struct.
> (btrace_config): add btrace_config_etm etm.
> * btrace-common.cc (btrace_format_string): add BTRACE_FORMAT_ETM.
> (btrace_format_short_string): add BTRACE_FORMAT_ETM.
OK for the documentation parts, with two nit:
> +@item set record btrace etm sink @var{sink}
> +Set ARM CoreSight ETM sink to collect traces.
> +On @sc{gnu}/Linux systems, possible values for @var{sink} are the name of the
> +files in the directory ^^^^^^^^
"the names", in plural.
> +Bigger buffers mean longer traces. On the other hand, @value{GDBN} will
> +also need longer to process the branch trace data before it can be used.
^^^^^^^^^^^^^^^^^^^^^^
"need longer time to process" is more clear, I think.
Thanks.
next prev parent reply other threads:[~2021-03-31 6:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 2:52 [PATCH v3 0/7] extend branch tracing to use ARM CoreSight traces Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 1/7] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 2/7] add btrace coresight related commands Zied Guermazi
2021-03-31 6:32 ` Eli Zaretskii [this message]
2021-03-31 18:30 ` Luis Machado
2021-03-31 20:24 ` Zied Guermazi
2021-04-01 16:11 ` Luis Machado
2021-03-31 2:52 ` [PATCH v3 3/7] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-03-31 20:23 ` Luis Machado
[not found] ` <a78174f9-177f-3757-6b33-d09f38f1fec8@trande.de>
2021-04-01 21:04 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 4/7] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-04-01 12:16 ` Luis Machado
2021-04-01 21:57 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 5/7] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-04-01 12:18 ` Luis Machado
2021-03-31 2:52 ` [PATCH v3 6/7] add support for coresight btrace via remote protocol Zied Guermazi
2021-03-31 6:33 ` Eli Zaretskii
2021-04-01 12:45 ` Luis Machado
2021-04-01 22:58 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 7/7] adapt btrace testcases for arm target Zied Guermazi
2021-04-01 13:34 ` Luis Machado
2021-04-04 19:30 ` Zied Guermazi
2021-04-06 13:09 ` Luis Machado
2021-04-09 19:34 ` Zied Guermazi
2021-04-12 17:11 ` Luis Machado
2021-04-02 16:02 ` [PATCH v3 0/7] extend branch tracing to use ARM CoreSight traces Simon Marchi
2021-04-02 16:05 ` Zied Guermazi
2021-04-05 0:09 ` Simon Marchi
2021-04-05 7:38 ` Zied Guermazi
2021-04-06 16:25 ` Simon Marchi
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=83v997j0kd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=zied.guermazi@trande.de \
/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).