From: Markus Metzger <markus.t.metzger@intel.com>
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org
Subject: [PATCH 0/2] btrace: perf improvements
Date: Fri, 07 Mar 2014 08:57:00 -0000 [thread overview]
Message-ID: <1394182665-14164-1-git-send-email-markus.t.metzger@intel.com> (raw)
The subsequent patches improve the performance of processing branch trace by
reducing the number of symbol table lookups.
For the currently hard-coded buffer size the impact should only be noticeable
for big programs. When tracing GDB itself, for example, there is no noticeable
delay.
Subsequent patches will allow the buffer size to be configurable. Bigger
buffers will require faster processing.
Markus Metzger (2):
btrace: only search for lines in current symtab
btrace: avoid symbol lookup
gdb/btrace.c | 128 +++++++++++++-------------
gdb/btrace.h | 3 +
gdb/record-btrace.c | 8 +-
gdb/testsuite/gdb.btrace/exception.exp | 4 +-
gdb/testsuite/gdb.btrace/static_functions.exp | 62 +++++++++++++
5 files changed, 135 insertions(+), 70 deletions(-)
create mode 100644 gdb/testsuite/gdb.btrace/static_functions.exp
--
1.8.3.1
next reply other threads:[~2014-03-07 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 8:57 Markus Metzger [this message]
2014-03-07 8:57 ` [PATCH 2/2] btrace: avoid symbol lookup Markus Metzger
2014-03-07 15:55 ` Pedro Alves
2014-03-10 8:05 ` Metzger, Markus T
2014-03-07 15:56 ` Pedro Alves
2014-03-10 21:43 ` Jan Kratochvil
2014-03-11 10:08 ` Metzger, Markus T
2014-03-21 17:22 ` Jan Kratochvil
2014-03-24 7:57 ` Metzger, Markus T
2014-03-24 8:37 ` Jan Kratochvil
2014-03-24 9:21 ` Metzger, Markus T
2014-03-07 8:57 ` [PATCH 1/2] btrace: only search for lines in current symtab Markus Metzger
2014-03-21 17:43 ` Jan Kratochvil
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=1394182665-14164-1-git-send-email-markus.t.metzger@intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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