From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 05/12] record-btrace: add bts buffer size configuration option
Date: Wed, 05 Nov 2014 20:46:00 -0000 [thread overview]
Message-ID: <545A8C89.1090901@redhat.com> (raw)
In-Reply-To: <1405346196-1804-6-git-send-email-markus.t.metzger@intel.com>
On 07/14/2014 02:56 PM, Markus Metzger wrote:
> --- a/gdb/features/btrace-conf.dtd
> +++ b/gdb/features/btrace-conf.dtd
> @@ -5,6 +5,7 @@
> notice and this notice are preserved. -->
>
> <!ELEMENT btrace-conf (bts?)>
> -<!ATTLIST btrace-conf version CDATA #FIXED "1.0">
> +<!ATTLIST btrace-conf version CDATA #FIXED "1.1">
I don't see why we need to bump the version. GDB that know
about attribute cope with it being missing. And GDBs that aren't
expecting the attribute just ignore it.
>
> <!ELEMENT bts EMPTY>
> +<!ATTLIST bts size CDATA #IMPLIED>
> supported_btrace_packets (char *buf)
> {
> if (target_supports_btrace (BTRACE_FORMAT_BTS))
> - strcat (buf, ";Qbtrace:bts+");
> + {
> + strcat (buf, ";Qbtrace:bts+");
> + strcat (own_buf, ";Qbtrace-conf:bts:size+");
> + }
'buf' or 'own_buf' ?
> + if (pages == 0) {
Misplaced {
> + errno = EINVAL;
> + goto err;
> + }
> +
> +/* Adjusts the size and returns a human readable size suffix. */
> +
> +static const char *
> +record_btrace_adjust_size (unsigned int *size)
> +{
> + unsigned int sz;
> +
> + sz = *size;
> +
> + if ((sz & ((1u << 30) - 1)) == 0)
> + {
> + *size = sz >> 30;
> + return "GB";
> + }
> + else if ((sz & ((1u << 20) - 1)) == 0)
> + {
> + *size = sz >> 20;
> + return "MB";
> + }
> + else if ((sz & ((1u << 10) - 1)) == 0)
> + {
> + *size = sz >> 10;
> + return "KB";
Pedantically, this should be "kB".
> + add_setshow_uinteger_cmd ("buffer-size", no_class,
> + &record_btrace_conf.bts.size,
> + _("Set the record/replay bts buffer size."),
> + _("Show the record/replay bts buffer size."), _("\
> +Bigger buffers allow longer recording but also take more time to process \
> +the recorded execution.\n\
> +The actual buffer size may differ from the requested size. Use \"info record\" \
> +to see the actual buffer size."), NULL, NULL,
> + &set_record_btrace_bts_cmdlist,
> + &show_record_btrace_bts_cmdlist);
I think the documentation of these knobs should mention that
the setting takes effect the next time btrace is enabled, not
immediately.
> +gdb_test_no_output "set record btrace bts buffer-size 1"
> +gdb_test "show record btrace bts buffer-size" "The record/replay bts buffer size is 1\.\r"
> +
> +gdb_test_no_output "record btrace bts"
> +gdb_test "show record btrace bts buffer-size" "The record/replay bts buffer size is 1\.\r"
See:
https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Make_sure_test_messages_are_unique
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-11-05 20:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 13:56 [PATCH 00/12] record btrace: prepare for a new trace format Markus Metzger
2014-07-14 13:56 ` [PATCH 08/12] btrace: identify cpu Markus Metzger
2014-11-05 20:47 ` Pedro Alves
2014-07-14 13:56 ` [PATCH 06/12] btrace: update btrace_compute_ftrace parameters Markus Metzger
2014-07-14 13:56 ` [PATCH 02/12] btrace: add format argument to supports_btrace Markus Metzger
2014-11-05 20:45 ` Pedro Alves
2014-11-14 12:36 ` Metzger, Markus T
2014-11-14 13:36 ` Pedro Alves
2014-11-14 13:47 ` Metzger, Markus T
2014-11-14 13:50 ` Pedro Alves
2014-11-14 13:50 ` Metzger, Markus T
2014-07-14 13:56 ` [PATCH 09/12] btrace: use the new cpu identifier Markus Metzger
2014-07-14 13:57 ` [PATCH 11/12] configure: check for libipt Markus Metzger
2014-07-14 13:57 ` [PATCH 04/12] record btrace: add configuration struct Markus Metzger
2014-07-14 15:06 ` Eli Zaretskii
2014-11-05 20:45 ` Pedro Alves
2014-07-14 13:57 ` [PATCH 05/12] record-btrace: add bts buffer size configuration option Markus Metzger
2014-07-14 15:44 ` Eli Zaretskii
2014-11-05 20:46 ` Pedro Alves [this message]
2014-07-14 13:57 ` [PATCH 03/12] btrace, linux: add perf event buffer abstraction Markus Metzger
2014-07-14 13:57 ` [PATCH 07/12] btrace: extend struct btrace_insn Markus Metzger
2014-11-05 20:46 ` Pedro Alves
2014-07-14 13:57 ` [PATCH 10/12] record-btrace: indicate gaps Markus Metzger
2014-07-14 13:57 ` [PATCH 12/12] [wip] btrace: support Intel(R) Processor Trace Markus Metzger
2014-07-14 14:48 ` [PATCH 01/12] btrace: add struct btrace_data Markus Metzger
2014-11-05 20:44 ` Pedro Alves
2014-10-28 14:35 ` [PATCH 00/12] record btrace: prepare for a new trace format Metzger, Markus T
2014-11-05 20:50 ` Pedro Alves
2014-11-06 9:04 ` Metzger, Markus T
2014-11-07 11:27 ` Pedro Alves
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=545A8C89.1090901@redhat.com \
--to=palves@redhat.com \
--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