From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>
Subject: RE: [PATCH 00/16] branch tracing support
Date: Fri, 11 May 2012 08:17:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23070F45CF@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CANFwon3r+r7BbsPf0krbbMuUL1jy92j=ZntpxzOTCLj+G1F_2Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
> -----Original Message-----
> From: Hui Zhu [mailto:teawater@gmail.com]
> Sent: Friday, May 11, 2012 2:24 AM
> To: Metzger, Markus T
> Cc: gdb-patches@sourceware.org; markus.t.metzger@gmail.com
> Subject: Re: [PATCH 00/16] branch tracing support
>
> Hi Markus,
>
> Thanks for your work. I think this function is very interesting.
>
> But I didn't find the patch for the doc in your patches list. I
> suggest you add it.
I expect some discussion on the commands and their exact spelling. I will add
documentation once the UI is clear, if that's OK.
I tried to summarize it in the cover letter. I hope it's sufficiently detailed
for
discussion. If it helps, I can send a documentation patch, as well, but I'm
afraid
I might end up redoing it completely.
> PS, do you have any data about how much speed decrease when btrace
> enable.
The speed decrease depends very heavily on the application. We measured
between 8.7x and 66x overhead.
Regards,
Markus.
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 417 bytes --]
--------------------------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
prev parent reply other threads:[~2012-05-11 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 15:15 markus.t.metzger
2012-05-10 15:16 ` [PATCH 05/16] cli, btrace: add btrace cli markus.t.metzger
2012-05-10 16:44 ` Eli Zaretskii
2012-05-11 8:17 ` Metzger, Markus T
2012-05-10 15:16 ` [PATCH 01/16] disas: add precise instructions flag markus.t.metzger
2012-05-10 15:17 ` [PATCH 07/16] configure: autoreconf markus.t.metzger
2012-05-10 15:17 ` [PATCH 02/16] source: add flags to print_source_lines () markus.t.metzger
2012-05-10 15:17 ` [PATCH 03/16] source, disasm: optionally prefix source lines with filename markus.t.metzger
2012-05-10 15:17 ` [PATCH 14/16] remote, btrace: add branch trace remote ops markus.t.metzger
2012-05-10 15:17 ` [PATCH 16/16] gdbserver, linux, btrace: add btrace support for linux-low markus.t.metzger
2012-05-10 15:17 ` [PATCH 10/16] btrace, config: enable btrace for 32bit and 64bit linux native markus.t.metzger
2012-05-10 15:17 ` [PATCH 04/16] thread, btrace: add generic branch trace support markus.t.metzger
2012-05-10 15:17 ` [PATCH 11/16] test, btrace: add branch trace tests markus.t.metzger
2012-05-10 15:17 ` [PATCH 08/16] linux, btrace: perf_event based branch tracing markus.t.metzger
2012-05-10 15:18 ` [PATCH 12/16] test, btrace: more branch tracing tests markus.t.metzger
2012-05-10 15:18 ` [PATCH 06/16] configure: add check for perf_event header markus.t.metzger
2012-05-10 15:18 ` [PATCH 15/16] gdbserver, btrace: add generic btrace support markus.t.metzger
2012-05-10 15:18 ` [PATCH 13/16] xml, btrace: define btrace xml document style markus.t.metzger
2012-05-10 15:18 ` [PATCH 09/16] btrace, linux: add linux native btrace target ops markus.t.metzger
2012-05-11 0:25 ` [PATCH 00/16] branch tracing support Hui Zhu
2012-05-11 8:17 ` 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=A78C989F6D9628469189715575E55B23070F45CF@IRSMSX103.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@gmail.com \
--cc=teawater@gmail.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