mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@google.com>
To: linux-kernel@vger.kernel.org
Cc: acme@redhat.com, peterz@infradead.org, mingo@elte.hu,
	ak@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org,
	kan.liang@intel.com, dsahern@gmail.com, adrian.hunter@intel.com
Subject: [PATCH v1 0/4] perf: improve script and record for iregs and brstack
Date: Wed, 19 Aug 2015 10:38:22 +0200	[thread overview]
Message-ID: <1439973506-2166-1-git-send-email-eranian@google.com> (raw)

This short series of patches improves perf record and perf script support
for interrupted machine state and branch stack.

this makes it easier to postprocess the data and narrow down the volume
and limit the overhead of capturing interrupt machine state registers.
For some analysis, only a subset of the registers is useful.

Changes:
   - Make --intr-regs accept register names to limit volume of data collected
   - Make perf script print interrupted machine register values with -F iregs
   - Make perf script print branch stack content with -F brstack

   $ perf record --intr-regs=\?
   available registers: AX BX CX DX SI DI BP SP IP FLAGS CS SS R8 R9 R10 R11 R12 R13 R14 R15 
   ...

   $ perf record --intr-regs=ax,bx,cx,dx,si ....

   $ perf script -F ip,iregs
   40afc2   AX:0x6c5770    BX:0x1e    CX:0x5f4d80a    DX:0x101010101010101    SI:0x1

   $ perf script -F ip,brstack ....


Stephane Eranian (4):
  perf script: enable printing of interrupted machine state
  perf/x86: add list of register names
  perf record: add ability to name registers to record
  perf script: enable printing of branch stack

 tools/perf/Documentation/perf-record.txt |  6 ++-
 tools/perf/Documentation/perf-script.txt |  2 +-
 tools/perf/arch/x86/util/Build           |  1 +
 tools/perf/arch/x86/util/perf_regs.c     | 31 ++++++++++++++
 tools/perf/builtin-record.c              |  7 +++-
 tools/perf/builtin-script.c              | 52 ++++++++++++++++++++++-
 tools/perf/perf.h                        |  2 +-
 tools/perf/util/Build                    |  1 +
 tools/perf/util/evsel.c                  |  2 +-
 tools/perf/util/parse-regs-options.c     | 71 ++++++++++++++++++++++++++++++++
 tools/perf/util/parse-regs-options.h     |  5 +++
 tools/perf/util/perf_regs.h              |  7 ++++
 12 files changed, 180 insertions(+), 7 deletions(-)
 create mode 100644 tools/perf/arch/x86/util/perf_regs.c
 create mode 100644 tools/perf/util/parse-regs-options.c
 create mode 100644 tools/perf/util/parse-regs-options.h

-- 
1.9.1


             reply	other threads:[~2015-08-19  8:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  8:38 Stephane Eranian [this message]
2015-08-19  8:38 ` [PATCH v1 1/4] perf script: enable printing of interrupted machine state Stephane Eranian
2015-08-19  8:38 ` [PATCH v1 2/4] perf/x86: add list of register names Stephane Eranian
2015-08-19  8:38 ` [PATCH v1 3/4] perf record: add ability to name registers to record Stephane Eranian
2015-08-20 11:18   ` Jiri Olsa
2015-08-20 20:02     ` Stephane Eranian
2015-08-19  8:38 ` [PATCH v1 4/4] perf script: enable printing of branch stack Stephane Eranian
2015-08-19 22:11   ` Andi Kleen
2015-08-19 22:20     ` Stephane Eranian
2015-08-19 23:32       ` Andi Kleen

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=1439973506-2166-1-git-send-email-eranian@google.com \
    --to=eranian@google.com \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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

Powered by JetHome