Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Metzger <markus.t.metzger@intel.com>
To: palves@redhat.com
Cc: gdb-patches@sourceware.org
Subject: [PATCH 00/12] record btrace: prepare for a new trace format
Date: Mon, 14 Jul 2014 13:56:00 -0000	[thread overview]
Message-ID: <1405346196-1804-1-git-send-email-markus.t.metzger@intel.com> (raw)

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


In order to motivate some patches (e.g. identifying the cpu or changing the
btrace_compute_ftrace parameters), I also send a work-in-progress version of the
second part that adds support for the new trace format.  This patch is not part
of the series under review.


Markus Metzger (12):
  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
  btrace: use the new cpu identifier
  record-btrace: indicate gaps
  configure: check for libipt
  [wip] btrace: support Intel(R) Processor Trace

 gdb/Makefile.in                                  |  16 +-
 gdb/NEWS                                         |  37 +
 gdb/btrace.c                                     | 965 ++++++++++++++++++++---
 gdb/btrace.h                                     |  98 ++-
 gdb/common/btrace-common.c                       | 175 ++++
 gdb/common/btrace-common.h                       | 242 +++++-
 gdb/config.in                                    |   3 +
 gdb/configure                                    | 498 ++++++++++++
 gdb/configure.ac                                 |  20 +
 gdb/doc/gdb.texinfo                              | 189 ++++-
 gdb/features/btrace-conf.dtd                     |  17 +
 gdb/features/btrace.dtd                          |  18 +-
 gdb/gdbserver/Makefile.in                        |   8 +-
 gdb/gdbserver/linux-low.c                        | 181 ++++-
 gdb/gdbserver/server.c                           | 228 +++++-
 gdb/gdbserver/target.h                           |  27 +-
 gdb/nat/linux-btrace.c                           | 806 ++++++++++++++++---
 gdb/nat/linux-btrace.h                           |  79 +-
 gdb/record-btrace.c                              | 497 +++++++++++-
 gdb/remote.c                                     | 233 +++++-
 gdb/target-delegates.c                           |  32 +-
 gdb/target.c                                     |  22 +-
 gdb/target.h                                     |  37 +-
 gdb/testsuite/gdb.btrace/buffer-size.exp         |  57 ++
 gdb/testsuite/gdb.btrace/delta.exp               |  12 +-
 gdb/testsuite/gdb.btrace/enable.exp              |   4 +-
 gdb/testsuite/gdb.btrace/finish.exp              |   3 +-
 gdb/testsuite/gdb.btrace/instruction_history.exp |   2 +-
 gdb/testsuite/gdb.btrace/next.exp                |   6 +-
 gdb/testsuite/gdb.btrace/nexti.exp               |   6 +-
 gdb/testsuite/gdb.btrace/nohist.exp              |   3 +-
 gdb/testsuite/gdb.btrace/step.exp                |   6 +-
 gdb/testsuite/gdb.btrace/stepi.exp               |   6 +-
 gdb/x86-linux-nat.c                              |  18 +-
 34 files changed, 4143 insertions(+), 408 deletions(-)
 create mode 100644 gdb/common/btrace-common.c
 create mode 100644 gdb/features/btrace-conf.dtd
 create mode 100644 gdb/testsuite/gdb.btrace/buffer-size.exp

-- 
1.8.3.1


             reply	other threads:[~2014-07-14 13:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 13:56 Markus Metzger [this message]
2014-07-14 13:56 ` [PATCH 09/12] btrace: use the new cpu identifier 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           ` Metzger, Markus T
2014-11-14 13:50           ` Pedro Alves
2014-07-14 13:56 ` [PATCH 06/12] btrace: update btrace_compute_ftrace parameters 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:57 ` [PATCH 12/12] [wip] btrace: support Intel(R) Processor Trace Markus Metzger
2014-07-14 13:57 ` [PATCH 10/12] record-btrace: indicate gaps Markus Metzger
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 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
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 11/12] configure: check for libipt 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=1405346196-1804-1-git-send-email-markus.t.metzger@intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --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