From: Michael Ellerman <mpe@ellerman.id.au>
To: Anju T <anju@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org
Cc: maddy@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
acme@redhat.com, hemant@linux.vnet.ibm.com,
anju@linux.vnet.ibm.com, dsahern@gmail.com,
naveen.n.rao@linux.vnet.ibm.com, sukadev@linux.vnet.ibm.com,
jolsa@redhat.com
Subject: Re: [V11,3/4] tools/perf: Map the ID values with register names
Date: Thu, 21 Apr 2016 23:39:11 +1000 (AEST) [thread overview]
Message-ID: <3qrKbh2Ft4z9t3q@ozlabs.org> (raw)
In-Reply-To: <1455944568-7231-4-git-send-email-anju@linux.vnet.ibm.com>
On Sat, 2016-20-02 at 05:02:47 UTC, Anju T wrote:
> Map ID values with corresponding register names. These names are then
> displayed when user issues perf record with the -I option
> followed by perf report/script with -D option.
>
> To test this patchset,
> Eg:
> $ perf record -I ls # record machine state at interrupt
> $ perf script -D # read the perf.data file
>
> Sample output obtained for this patch / output looks like as follows:
>
> 496768515470 0x1988 [0x188]: PERF_RECORD_SAMPLE(IP, 0x1): 4522/4522: 0xc0000000001e538c period: 1 addr: 0
> ... intr regs: mask 0x7ffffffffff ABI 64-bit
> .... r0 0xc0000000001e5e34
> .... r1 0xc000000fe733f9a0
> .... r2 0xc000000001523100
> .... r3 0xc000000ffaadeb60
> .... r4 0xc000000003456800
> .... r5 0x73a9b5e000
> .... r6 0x1e000000
> .... r7 0x0
> .... r8 0x0
> .... r9 0x0
> .... r10 0x1
> .... r11 0x0
> .... r12 0x24022822
> .... r13 0xc00000000feec180
> .... r14 0x0
> .... r15 0xc000001e4be18800
> .... r16 0x0
> .... r17 0xc000000ffaac5000
> .... r18 0xc000000fe733f8a0
> .... r19 0xc000000001523100
> .... r20 0xc00000000009fd1c
> .... r21 0xc000000fcaa69000
> .... r22 0xc0000000001e4968
> .... r23 0xc000000001523100
> .... r24 0xc000000fe733f850
> .... r25 0xc000000fcaa69000
> .... r26 0xc000000003b8fcf0
> .... r27 0xfffffffffffffead
> .... r28 0x0
> .... r29 0xc000000fcaa69000
> .... r30 0x1
> .... r31 0x0
> .... nip 0xc0000000001dd320
> .... msr 0x9000000000009032
> .... orig_r3 0xc0000000001e538c
> .... ctr 0xc00000000009d550
> .... link 0xc0000000001e5e34
> .... xer 0x0
> .... ccr 0x84022882
> .... softe 0x0
> .... trap 0xf01
> .... dar 0x0
> .... dsisr 0xf00040060000004
> ... thread: :4522:4522
> ...... dso: /root/.debug/.build-id/b0/ef11b1a1629e62ac9de75199117ee5ef9469e9
> :4522 4522 496.768515: 1 cycles: c0000000001e538c .perf_event_context_sched_in (/boot/vmlinux)
>
> Signed-off-by: Anju T <anju@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/dc642e8388b63a9a221903584b
cheers
next prev parent reply other threads:[~2016-04-21 13:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 5:02 [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-02-20 5:02 ` [PATCH V11 1/4] perf/powerpc: assign an id to each powerpc register Anju T
2016-04-21 11:07 ` Naveen N. Rao
2016-04-21 13:39 ` [V11,1/4] " Michael Ellerman
2016-02-20 5:02 ` [PATCH V11 2/4] perf/powerpc: add support for sampling intr machine state Anju T
2016-04-21 11:15 ` Naveen N. Rao
2016-04-21 13:39 ` [V11, " Michael Ellerman
2016-02-20 5:02 ` [PATCH V11 3/4] tools/perf: Map the ID values with register names Anju T
2016-04-21 13:39 ` Michael Ellerman [this message]
2016-02-20 5:02 ` [PATCH V2 4/4] tool/perf: Add sample_reg_mask to include all perf_regs Anju T
2016-04-21 13:39 ` [V2,4/4] " Michael Ellerman
2016-03-07 8:23 ` [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-04-18 9:47 ` Anju T
2016-04-20 3:57 ` Arnaldo Carvalho de Melo
2016-04-20 4:55 ` Michael Ellerman
2016-04-20 13:16 ` Arnaldo Carvalho de Melo
2016-04-21 13:41 ` Michael Ellerman
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=3qrKbh2Ft4z9t3q@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=acme@redhat.com \
--cc=anju@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).