From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "palves@redhat.com" <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Jan Kratochvil (jan.kratochvil@redhat.com)"
<jan.kratochvil@redhat.com>
Subject: RE: [PATCH v3 00/15] record btrace: prepare for a new trace format
Date: Wed, 04 Feb 2015 08:25:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B231E6CA1E0@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1422548899-9789-1-git-send-email-markus.t.metzger@intel.com>
> -----Original Message-----
> From: Metzger, Markus T
> Sent: Thursday, January 29, 2015 5:28 PM
> To: palves@redhat.com
Hello Pedro,
> btrace: add struct btrace_data
> btrace: add format argument to supports_btrace
> btrace, linux: add perf event buffer abstraction
> record btrace: add configuration struct
> record-btrace: add bts buffer size configuration option
> btrace: update btrace_compute_ftrace parameters
> btrace: extend struct btrace_insn
> btrace: identify cpu
> record-btrace: indicate gaps
I don't think it was a very good idea from me to extend the patch series
while under review. Let's focus on the above patches from the original
series...
> btrace: less debug output
> btrace: work around _dl_runtime_resolve returning to resolved function
> btrace: support 32-bit inferior on 64-bit host
> btrace: increase buffer size for exception test
... and ignore the new bug-fix patches. I'll send them in a new, separate
review request. I found another bug I see on some targets and I'm working
on simplifying the test suite. If I keep adding (those) patches to this series,
we will never get anywhere with it.
Makes sense?
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
prev parent reply other threads:[~2015-02-04 8:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:28 Markus Metzger
2015-01-29 16:29 ` [PATCH v3 08/15] btrace: identify cpu Markus Metzger
2015-01-29 16:29 ` [PATCH v3 05/15] record-btrace: add bts buffer size configuration option Markus Metzger
2015-01-29 16:29 ` [PATCH v3 12/15] btrace: support 32-bit inferior on 64-bit host Markus Metzger
2015-01-29 16:29 ` [PATCH v3 02/15] btrace: add format argument to supports_btrace Markus Metzger
2015-01-29 16:29 ` [PATCH v3 13/15] btrace: increase buffer size for exception test Markus Metzger
2015-01-29 16:29 ` [PATCH v3 07/15] btrace: extend struct btrace_insn Markus Metzger
2015-01-29 16:30 ` [PATCH v3 14/15] configure: check for libipt Markus Metzger
2015-01-29 16:30 ` [PATCH v3 06/15] btrace: update btrace_compute_ftrace parameters Markus Metzger
2015-01-29 16:30 ` [PATCH v3 09/15] record-btrace: indicate gaps Markus Metzger
2015-01-29 16:30 ` [PATCH v3 01/15] btrace: add struct btrace_data Markus Metzger
2015-01-29 16:33 ` [PATCH v3 11/15] btrace: work around _dl_runtime_resolve returning to resolved function Markus Metzger
2015-01-29 17:11 ` [PATCH v3 10/15] btrace: less debug output Markus Metzger
2015-01-29 17:11 ` [PATCH v3 03/15] btrace, linux: add perf event buffer abstraction Markus Metzger
2015-01-29 18:35 ` [PATCH v3 04/15] record btrace: add configuration struct Markus Metzger
2015-01-29 19:29 ` Eli Zaretskii
2015-01-29 19:28 ` [PATCH v3 15/15] [wip] btrace: support Intel(R) Processor Trace Markus Metzger
2015-01-29 19:28 ` Eli Zaretskii
2015-01-30 18:57 ` Metzger, Markus T
2015-02-04 8:25 ` Metzger, Markus T [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=A78C989F6D9628469189715575E55B231E6CA1E0@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.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