From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 0/9] record btrace: prepare for a new trace format
Date: Thu, 05 Feb 2015 18:33:00 -0000 [thread overview]
Message-ID: <54D3B75D.3040203@redhat.com> (raw)
In-Reply-To: <1423150072-21229-1-git-send-email-markus.t.metzger@intel.com>
On 02/05/2015 04:27 PM, Markus Metzger wrote:
> I had to change a few strings so instead of sending another delta update,
> I send the entire series.
>
> Changes to v3:
>
> - changed a few strings around the term Branch Trace Store
> - fixed an overflow bug when enabling branch tracing
> - removed unrelated bug-fix patches that were not in the original series
>
> This is the first part of a patch series that adds support for a new trace
> format. The entire series consists of three parts:
>
> - preparation (this)
> - support live inferior tracing
> - support trace in core files
>
>
> Besides preparing for an additional trace format, this first part adds the
> following functionality:
>
> - allow the trace buffer size to be configured
> - indicate errors as gaps in the trace
Thanks, this version is OK, with the little nits pointed out
as replies to the patches fixed. No need to repost the series
for that.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-02-05 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:27 Markus Metzger
2015-02-05 15:28 ` [PATCH v4 5/9] record-btrace: add bts buffer size configuration option Markus Metzger
2015-02-05 16:25 ` Eli Zaretskii
2015-02-05 15:28 ` [PATCH v4 2/9] btrace: add format argument to supports_btrace Markus Metzger
2015-02-05 15:28 ` [PATCH v4 9/9] record-btrace: indicate gaps Markus Metzger
2015-02-05 15:28 ` [PATCH v4 6/9] btrace: update btrace_compute_ftrace parameters Markus Metzger
2015-02-05 15:28 ` [PATCH v4 4/9] record btrace: add configuration struct Markus Metzger
2015-02-05 16:27 ` Eli Zaretskii
2015-02-05 18:31 ` Pedro Alves
2015-02-05 15:28 ` [PATCH v4 1/9] btrace: add struct btrace_data Markus Metzger
2015-02-05 15:28 ` [PATCH v4 3/9] btrace, linux: add perf event buffer abstraction Markus Metzger
2015-02-05 15:28 ` [PATCH v4 8/9] btrace: identify cpu Markus Metzger
2015-02-05 18:31 ` Pedro Alves
2015-02-05 15:28 ` [PATCH v4 7/9] btrace: extend struct btrace_insn Markus Metzger
2015-02-05 18:33 ` Pedro Alves [this message]
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=54D3B75D.3040203@redhat.com \
--to=palves@redhat.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