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 0/5] Support Intel(R) Processor Trace
Date: Tue, 23 Jun 2015 08:22:00 -0000	[thread overview]
Message-ID: <1435047418-21611-1-git-send-email-markus.t.metzger@intel.com> (raw)

Processor Trace (PT) is a new h/w tracing feature available with the 5th
generation Core processor.

It allows recording control-flow execution trace similar to Branch Trace Store
(BTS), which is already supported by GDB via the "record btrace" command.
PT is also integrated into GDB's record framework and enabled via the "record
btrace" or the "record btrace pt" command.  The former falls back to BTS, if
PT is not available.

Compared to BTS, PT is more compact and significantly less intrusive.  This
means longer traces and less recording overhead.

The PT driver has been merged into kernel 4.1.  This patch series adds GDB
support.  The actual decode is done in a separate library that is available
open source on github:

    https://github.com/01org/processor-trace

Markus Metzger (5):
  configure: check for libipt
  btrace: support Intel(R) Processor Trace
  btrace, linux: use data_size and data_offset
  btrace: store raw btrace data
  btrace: maintenance commands

 gdb/Makefile.in              |    5 +-
 gdb/NEWS                     |   27 +
 gdb/btrace.c                 | 1134 +++++++++++++++++++++++++++++++++++++++++-
 gdb/btrace.h                 |   85 ++++
 gdb/common/btrace-common.c   |   97 ++++
 gdb/common/btrace-common.h   |   48 +-
 gdb/config.in                |    3 +
 gdb/configure                |  498 +++++++++++++++++++
 gdb/configure.ac             |   20 +
 gdb/doc/gdb.texinfo          |  187 ++++++-
 gdb/features/btrace-conf.dtd |    7 +-
 gdb/features/btrace.dtd      |   16 +-
 gdb/gdbserver/linux-low.c    |   85 +++-
 gdb/gdbserver/server.c       |   51 +-
 gdb/nat/linux-btrace.c       |  398 ++++++++++++++-
 gdb/nat/linux-btrace.h       |   19 +
 gdb/record-btrace.c          |  139 +++++-
 gdb/remote.c                 |   65 ++-
 18 files changed, 2841 insertions(+), 43 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2015-06-23  8:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:22 Markus Metzger [this message]
2015-06-23  8:22 ` [PATCH 1/5] configure: check for libipt Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-30 14:54     ` Metzger, Markus T
2015-06-30 15:01       ` Pedro Alves
2015-06-23  8:22 ` [PATCH 5/5] btrace: maintenance commands Markus Metzger
2015-06-23 15:28   ` Eli Zaretskii
2015-06-24  7:05     ` Metzger, Markus T
2015-06-24 14:38       ` Eli Zaretskii
2015-06-30 12:57   ` Pedro Alves
2015-06-23  8:22 ` [PATCH 4/5] btrace: store raw btrace data Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-23  8:22 ` [PATCH 3/5] btrace, linux: use data_size and data_offset Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-23  8:23 ` [PATCH 2/5] btrace: support Intel(R) Processor Trace Markus Metzger
2015-06-23 15:32   ` Eli Zaretskii
2015-06-30 12:56   ` Pedro Alves
2015-06-30 14:54     ` Metzger, Markus T
2015-06-30 15:08       ` Pedro Alves
2015-07-01  8:39         ` Metzger, Markus T

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=1435047418-21611-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