From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Chandan Kumar <chandan.kumar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.vnet.ibm.com, hemant@linux.vnet.ibm.com,
anju@linux.vnet.ibm.com, jolsa@redhat.com
Subject: Re: [PATCH 0/3] Add support for perf user stack dump in powerpc
Date: Thu, 28 Apr 2016 12:29:58 -0300 [thread overview]
Message-ID: <20160428152958.GA2730@redhat.com> (raw)
In-Reply-To: <20160428142341.GD7880@naverao1-tp.in.ibm.com>
Em Thu, Apr 28, 2016 at 07:53:41PM +0530, Naveen N. Rao escreveu:
> On 2016/04/28 03:01PM, Chandan Kumar wrote:
> > This patch set enables perf user stack dump on powerpc
>
> For this patch-set:
> Reviewed-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
>
> I suppose that implies my testing, but nonetheless:
> Tested-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
>
> >
> > Example with "ls" command as user program
> > ./perf record --call-graph=dwarf,8192 ls
> >
> > ./perf script
> > ---------8< -----
> > ..
> > ...
> > perf 12549 75938.934539: 1771 cycles:ppp:
> > 210d90 .perf_event_exec (/boot/vmlinux)
> > 34b914 .load_elf_binary (/boot/vmlinux)
> > 2dcabc .search_binary_handler (/boot/vmlinux)
> > 2dd6f0 .do_execveat_common.isra.28 (/boot/vmlinux)
> > 2ddcd8 .sys_execve (/boot/vmlinux)
> > 19258 system_call (/boot/vmlinux)
>
> To expand on this, with upstream libunwind
> (git://git.sv.gnu.org/libunwind.git) and with debuginfo installed:
>
> # ./perf record -e cycles -g --call-graph dwarf -- find . -iname
> '*linux*'
> ./tests/vmlinux-kallsyms.c
> ./tests/vmlinux-kallsyms.o
> ./tests/.vmlinux-kallsyms.o.cmd
> ./util/include/linux
> [ perf record: Woken up 2 times to write data ]
> [ perf record: Captured and wrote 0.371 MB perf.data (45 samples) ]
> # ./perf script
> <snip>
> find 23858 167788.657182: 881967 cycles:
> 8e758c _cond_resched (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 3f83bc selinux_inode_getattr (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 3ee254 security_inode_getattr (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 3063a4 vfs_getattr (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 306530 vfs_fstatat (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 306c60 sys_newfstatat (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 19210 system_call (/lib/modules/4.6.0-rc3-nnr+/build/vmlinux)
> 3fffa31829a8 __fxstatat64 (/usr/lib64/libc-2.17.so)
> 10025ac8 fts_stat.isra.2 (/usr/bin/find)
> 10027c04 fts_read (/usr/bin/find)
> 10003e18 find (/usr/bin/find)
> 100035ec main (/usr/bin/find)
> 3fffa30a4580 generic_start_main.isra.0 (/usr/lib64/libc-2.17.so)
> 3fffa30a4774 __libc_start_main (/usr/lib64/libc-2.17.so)
>
> <snip>
>
>
> Arnaldo, Michael,
> Can we take this through powerpc/next as well since this pretty much
> rides on the recent perf regs work?
I haven't tested with the bits that touch the common code, have you? But
I think it should be harmless and overall this patchset looks fine, so,
if you, just in case, have tested this on a x86_64 machine and all seems
well, i.e. perf test, perf record/report with a perf-probe generated
event, to exercise this stuff, then:
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
next prev parent reply other threads:[~2016-04-28 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:31 [PATCH 0/3] Add support for perf user stack dump in powerpc Chandan Kumar
2016-04-28 9:31 ` [PATCH 1/3] powerpc: Add HAVE_PERF_USER_STACK_DUMP support Chandan Kumar
2016-05-08 3:59 ` [1/3] " Michael Ellerman
2016-04-28 9:31 ` [PATCH 2/3] powerpc/perf: Add support for unwinding perf-stackdump Chandan Kumar
2016-05-08 3:59 ` [2/3] " Michael Ellerman
2016-04-28 9:31 ` [PATCH 3/3] perf tools: Fix perf regs mask generation Chandan Kumar
2016-05-08 3:59 ` [3/3] " Michael Ellerman
2016-04-28 14:23 ` [PATCH 0/3] Add support for perf user stack dump in powerpc Naveen N. Rao
2016-04-28 15:29 ` Arnaldo Carvalho de Melo [this message]
2016-04-28 16:14 ` Naveen N. Rao
2016-04-28 16:31 ` Arnaldo Carvalho de Melo
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=20160428152958.GA2730@redhat.com \
--to=acme@redhat.com \
--cc=anju@linux.vnet.ibm.com \
--cc=chandan.kumar@linux.vnet.ibm.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 \
/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).