From: Zied Guermazi <zied.guermazi@trande.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com
Subject: Re: [PATCH v6 2/7] add btrace coresight related commands
Date: Tue, 1 Jun 2021 17:47:34 +0200 [thread overview]
Message-ID: <dea6073d-bd25-ce24-73ce-91f09796711e@trande.de> (raw)
In-Reply-To: <83czt523g6.fsf@gnu.org>
Hi Eli,
there is no change in documentation part. so we can consider this part
as approved.
Kind Regards
Zied Guermazi
On 01.06.21 14:07, Eli Zaretskii wrote:
>> From: Zied Guermazi <zied.guermazi@trande.de>
>> Date: Mon, 31 May 2021 23:33:02 +0200
>> Cc: Zied Guermazi <zied.guermazi@trande.de>
>>
>> This patch extends the commands needed for using branch tracing
>> with ARM CoreSight traces.
>> Those commands are:
>> set record btrace etm sink
>> set record btrace etm buffer-size
>> record btrace etm
>>
>> 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.
> Are there any changes in the documentation parts since the last time?
> If not, I think I already approved the doc parts.
>
> Thanks.
next prev parent reply other threads:[~2021-06-01 15:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 21:33 [PATCH v6 0/7] extend branch tracing to use ARM CoreSight traces Zied Guermazi
2021-05-31 21:33 ` [PATCH v6 1/7] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-06-30 12:17 ` Luis Machado
2021-05-31 21:33 ` [PATCH v6 2/7] add btrace coresight related commands Zied Guermazi
2021-06-01 12:07 ` Eli Zaretskii
2021-06-01 15:47 ` Zied Guermazi [this message]
2021-06-30 12:26 ` Luis Machado
2021-05-31 21:33 ` [PATCH v6 3/7] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-06-22 14:59 ` Metzger, Markus T
2022-04-07 16:33 ` Zied Guermazi
2022-04-13 7:00 ` Metzger, Markus T
2022-05-10 12:58 ` Zied Guermazi
2022-05-10 13:21 ` Metzger, Markus T
2021-06-30 12:54 ` Luis Machado
2021-05-31 21:33 ` [PATCH v6 4/7] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-06-23 8:00 ` Metzger, Markus T
2022-05-12 22:52 ` Zied Guermazi
2022-05-13 5:31 ` Metzger, Markus T
2022-06-12 21:02 ` Zied Guermazi
2022-06-20 12:52 ` Metzger, Markus T
2022-07-18 19:06 ` Zied Guermazi
2022-07-19 5:04 ` Metzger, Markus T
2022-07-21 22:20 ` Zied Guermazi
2022-07-25 14:33 ` Metzger, Markus T
2021-06-30 13:24 ` Luis Machado
2021-05-31 21:33 ` [PATCH v6 5/7] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-06-23 8:08 ` Metzger, Markus T
2021-05-31 21:33 ` [PATCH v6 6/7] add support for coresight btrace via remote protocol Zied Guermazi
2021-06-01 12:08 ` Eli Zaretskii
2021-06-23 10:59 ` Metzger, Markus T
2021-05-31 21:33 ` [PATCH v6 7/7] adapt btrace testcases for arm target Zied Guermazi
2021-06-22 21:28 ` Lancelot SIX
2021-06-23 14:16 ` Metzger, Markus T
2022-05-13 11:08 ` Richard Earnshaw
2022-05-17 9:44 ` Zied Guermazi
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=dea6073d-bd25-ce24-73ce-91f09796711e@trande.de \
--to=zied.guermazi@trande.de \
--cc=eliz@gnu.org \
--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).