[PATCH v1 0/4] perf: improve script and record for iregs and brstack

From: Stephane Eranian
Date: Wed Aug 19 2015 - 04:39:23 EST


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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/