Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1208759 > unrolled thread
| Started by | Adrian Hunter <adrian.hunter@intel.com> |
|---|---|
| First post | 2015-08-17 19:50 +0200 |
| Last post | 2015-08-18 18:20 +0200 |
| Articles | 7 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Adrian Hunter <adrian.hunter@intel.com> - 2015-08-17 19:50 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Arnaldo Carvalho de Melo <acme@kernel.org> - 2015-08-17 20:00 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Adrian Hunter <adrian.hunter@intel.com> - 2015-08-17 21:10 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Arnaldo Carvalho de Melo <acme@kernel.org> - 2015-08-17 22:10 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Adrian Hunter <adrian.hunter@intel.com> - 2015-08-18 08:50 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Adrian Hunter <adrian.hunter@intel.com> - 2015-08-18 11:20 +0200
Re: [PATCH V8 08/25] perf tools: Add Intel BTS support Arnaldo Carvalho de Melo <acme@kernel.org> - 2015-08-18 18:20 +0200
| From | Adrian Hunter <adrian.hunter@intel.com> |
|---|---|
| Date | 2015-08-17 19:50 +0200 |
| Subject | Re: [PATCH V8 08/25] perf tools: Add Intel BTS support |
| Message-ID | <pYwHM-5TN-17@gated-at.bofh.it> |
On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote:
> Em Fri, Jul 17, 2015 at 07:33:43PM +0300, Adrian Hunter escreveu:
>> Intel BTS support fits within the new auxtrace infrastructure.
>> Recording is supporting by identifying the Intel BTS PMU, parsing
>> options and setting up events.
>>
>> Decoding is supported by queuing up trace data by thread and then
>> decoding synchronously delivering synthesized event samples into the
>> session processing for tools to consume.
>
> So, I am not being able to reproduce the results from last time I tried
> it..
>
> [root@zoo ~]# uname -r
> 4.2.0-rc5+
>
> But all the DSOs are not being resolved :-\ Same machine, will try after lunch
> with a tip/master built kernel, right now I get this, perhaps that "81649
> instruction errors" message? I'll see what are the results with tip/master,
> meanwhile what I have is at the tmp.perf/intel_pt branch in my tree.
>
> - Arnaldo
>
> [root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.884 MB perf.data ]
> [root@zoo ~]# perf evlist
> intel_bts//
> dummy:u
> [root@zoo ~]# perf evlist -v
> intel_bts//: type: 6, size: 112, { sample_period, sample_freq }: 1,
> sample_type: IP|TID|IDENTIFIER, read_format: ID, disabled: 1,
> enable_on_exec: 1, sample_id_all: 1, exclude_guest: 1
> dummy:u: type: 1, size: 112, config: 0x9, { sample_period, sample_freq
> }: 1, sample_type: IP|TID|IDENTIFIER, read_format: ID, disabled: 1,
> exclude_kernel: 1, exclude_hv: 1, mmap: 1, comm: 1, enable_on_exec: 1,
> task: 1, sample_id_all: 1, mmap2: 1, comm_exec: 1
> [root@zoo ~]#
>
> Warning:
> 81649 instruction trace errors
> # To display the perf.data header info, please use --header/--header-only options.
> #
> #
> # Total Lost Samples: 0
> #
> # Samples: 0 of event 'intel_bts//'
> # Event count (approx.): 0
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ............. ......
> #
>
>
> # Samples: 0 of event 'dummy:u'
> # Event count (approx.): 0
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ............. ......
> #
>
>
> # Samples: 81K of event 'branches'
> # Event count (approx.): 81649
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ................ ......................
> #
> 2.71% usleep [unknown] [.] 0x00007fa0ff695061
> 2.62% usleep [unknown] [.] 0x00007fa0ffb3de7e
> 1.96% usleep [unknown] [.] 0x00007fa0ffb2e726
> 1.92% usleep [unknown] [.] 0x00007fa0ff695086
> 1.60% usleep [unknown] [.] 0xffffffff811c91d0
> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d
> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7
>
>
>
>
It is very weird that it doesn't know the dso.
I presume there is nothing unusual about the environment e.g. in a chroot or anything
What if you try a different event e.g. perf record --per-thread -e cycles sleep 1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Arnaldo Carvalho de Melo <acme@kernel.org> |
|---|---|
| Date | 2015-08-17 20:00 +0200 |
| Message-ID | <pYwRt-654-23@gated-at.bofh.it> |
| In reply to | #1208759 |
Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu:
> On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote:
> > 1.92% usleep [unknown] [.] 0x00007fa0ff695086
> > 1.60% usleep [unknown] [.] 0xffffffff811c91d0
> > 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d
> > 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7
> It is very weird that it doesn't know the dso.
> I presume there is nothing unusual about the environment e.g. in a chroot or anything
> What if you try a different event e.g. perf record --per-thread -e cycles sleep 1
[root@zoo ~]# perf record --per-thread -e cycles sleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ]
[root@zoo ~]# perf report | grep -v ^# | head -5
42.57% sleep libc-2.20.so [.] malloc_hook_ini
41.81% sleep [kernel.vmlinux] [k] filemap_fault
14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range
1.18% sleep [kernel.vmlinux] [k] strlcpy
0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe
[root@zoo ~]#
[root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]'
42.57% sleep [.] malloc_hook_ini
[root@zoo ~]#
[root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 1.825 MB perf.data ]
[root@zoo ~]# perf report | grep -v ^# | head -5
Warning:
79074 instruction trace errors
2.80% usleep [unknown] [.] 0x00007f48888aa061
[root@zoo ~]#
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Adrian Hunter <adrian.hunter@intel.com> |
|---|---|
| Date | 2015-08-17 21:10 +0200 |
| Message-ID | <pYxXc-7RH-21@gated-at.bofh.it> |
| In reply to | #1208764 |
On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote: > Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu: >> On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote: >>> 1.92% usleep [unknown] [.] 0x00007fa0ff695086 >>> 1.60% usleep [unknown] [.] 0xffffffff811c91d0 >>> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d >>> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7 > >> It is very weird that it doesn't know the dso. > >> I presume there is nothing unusual about the environment e.g. in a chroot or anything > >> What if you try a different event e.g. perf record --per-thread -e cycles sleep 1 > > [root@zoo ~]# perf record --per-thread -e cycles sleep 1 > [ perf record: Woken up 1 times to write data ] > [ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ] > [root@zoo ~]# perf report | grep -v ^# | head -5 > 42.57% sleep libc-2.20.so [.] malloc_hook_ini > 41.81% sleep [kernel.vmlinux] [k] filemap_fault > 14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range > 1.18% sleep [kernel.vmlinux] [k] strlcpy > 0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe > [root@zoo ~]# > > [root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]' > 42.57% sleep [.] malloc_hook_ini > > > [root@zoo ~]# > > [root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1 > [ perf record: Woken up 1 times to write data ] > [ perf record: Captured and wrote 1.825 MB perf.data ] > [root@zoo ~]# perf report | grep -v ^# | head -5 > Warning: > 79074 instruction trace errors > > > > > 2.80% usleep [unknown] [.] 0x00007f48888aa061 > [root@zoo ~]# Running out of ideas. Can you somehow share or send me the offending perf.data file? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Arnaldo Carvalho de Melo <acme@kernel.org> |
|---|---|
| Date | 2015-08-17 22:10 +0200 |
| Message-ID | <pYyTf-Mb-13@gated-at.bofh.it> |
| In reply to | #1208795 |
Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu:
> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote:
> >Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu:
> >>On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote:
> >>> 1.92% usleep [unknown] [.] 0x00007fa0ff695086
> >>> 1.60% usleep [unknown] [.] 0xffffffff811c91d0
> >>> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d
> >>> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7
> >
> >>It is very weird that it doesn't know the dso.
> >
> >>I presume there is nothing unusual about the environment e.g. in a chroot or anything
> >
> >>What if you try a different event e.g. perf record --per-thread -e cycles sleep 1
> >
> >[root@zoo ~]# perf record --per-thread -e cycles sleep 1
> >[ perf record: Woken up 1 times to write data ]
> >[ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ]
> >[root@zoo ~]# perf report | grep -v ^# | head -5
> > 42.57% sleep libc-2.20.so [.] malloc_hook_ini
> > 41.81% sleep [kernel.vmlinux] [k] filemap_fault
> > 14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range
> > 1.18% sleep [kernel.vmlinux] [k] strlcpy
> > 0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe
> >[root@zoo ~]#
> >
> >[root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]'
> > 42.57% sleep [.] malloc_hook_ini
> >
> >[root@zoo ~]#
> >
> >[root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1
> >[ perf record: Woken up 1 times to write data ]
> >[ perf record: Captured and wrote 1.825 MB perf.data ]
> >[root@zoo ~]# perf report | grep -v ^# | head -5
> >Warning:
> >79074 instruction trace errors
> > 2.80% usleep [unknown] [.] 0x00007f48888aa061
> >[root@zoo ~]#
>
> Running out of ideas. Can you somehow share or send me the offending perf.data file?
http://vger.kernel.org/~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz
It works if I use a tip/master kernel:
[root@perf4 ~]# uname -r
4.2.0-rc7+
[root@perf4 ~]# uname -r
4.2.0-rc7+
[root@perf4 ~]# perf record --per-thread -e intel_bts// usleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 1.785 MB perf.data ]
[root@perf4 ~]# dmesg | grep Performance
[ 0.188477] Performance Events: PEBS fmt2+, 16-deep LBR, Broadwell
events, full-width counters, Intel PMU driver.
[root@perf4 ~]# perf report --stdio | grep -v ^# | head -10
10.81% usleep libc-2.17.so [.] _dl_addr
6.56% usleep [kernel.kallsyms] [.] unmap_single_vma
3.33% usleep ld-2.17.so [.] strcmp
2.53% usleep [kernel.kallsyms] [.] mem_cgroup_begin_page_stat
2.49% usleep ld-2.17.so [.] _dl_lookup_symbol_x
2.39% usleep ld-2.17.so [.] _dl_relocate_object
[root@perf4 ~]#
Probably some fix for the kernel driver is missing?
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Adrian Hunter <adrian.hunter@intel.com> |
|---|---|
| Date | 2015-08-18 08:50 +0200 |
| Message-ID | <pYISC-6MD-15@gated-at.bofh.it> |
| In reply to | #1208853 |
On 17/08/15 22:58, Arnaldo Carvalho de Melo wrote: > Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu: >> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote: >>> Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu: >>>> On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote: >>>>> 1.92% usleep [unknown] [.] 0x00007fa0ff695086 >>>>> 1.60% usleep [unknown] [.] 0xffffffff811c91d0 >>>>> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d >>>>> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7 >>> >>>> It is very weird that it doesn't know the dso. >>> >>>> I presume there is nothing unusual about the environment e.g. in a chroot or anything >>> >>>> What if you try a different event e.g. perf record --per-thread -e cycles sleep 1 >>> >>> [root@zoo ~]# perf record --per-thread -e cycles sleep 1 >>> [ perf record: Woken up 1 times to write data ] >>> [ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ] >>> [root@zoo ~]# perf report | grep -v ^# | head -5 >>> 42.57% sleep libc-2.20.so [.] malloc_hook_ini >>> 41.81% sleep [kernel.vmlinux] [k] filemap_fault >>> 14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range >>> 1.18% sleep [kernel.vmlinux] [k] strlcpy >>> 0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe >>> [root@zoo ~]# >>> >>> [root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]' >>> 42.57% sleep [.] malloc_hook_ini >>> >>> [root@zoo ~]# >>> >>> [root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1 >>> [ perf record: Woken up 1 times to write data ] >>> [ perf record: Captured and wrote 1.825 MB perf.data ] >>> [root@zoo ~]# perf report | grep -v ^# | head -5 >>> Warning: >>> 79074 instruction trace errors >>> 2.80% usleep [unknown] [.] 0x00007f48888aa061 >>> [root@zoo ~]# >> >> Running out of ideas. Can you somehow share or send me the offending perf.data file? > > http://vger.kernel.org/~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz Says: You don't have permission to access /~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz on this server. > > It works if I use a tip/master kernel: > > [root@perf4 ~]# uname -r > 4.2.0-rc7+ > [root@perf4 ~]# uname -r > 4.2.0-rc7+ > [root@perf4 ~]# perf record --per-thread -e intel_bts// usleep 1 > [ perf record: Woken up 1 times to write data ] > [ perf record: Captured and wrote 1.785 MB perf.data ] > [root@perf4 ~]# dmesg | grep Performance > [ 0.188477] Performance Events: PEBS fmt2+, 16-deep LBR, Broadwell > events, full-width counters, Intel PMU driver. > [root@perf4 ~]# perf report --stdio | grep -v ^# | head -10 > > > > > 10.81% usleep libc-2.17.so [.] _dl_addr > 6.56% usleep [kernel.kallsyms] [.] unmap_single_vma > 3.33% usleep ld-2.17.so [.] strcmp > 2.53% usleep [kernel.kallsyms] [.] mem_cgroup_begin_page_stat > 2.49% usleep ld-2.17.so [.] _dl_lookup_symbol_x > 2.39% usleep ld-2.17.so [.] _dl_relocate_object > [root@perf4 ~]# > > Probably some fix for the kernel driver is missing? Works for me though. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Adrian Hunter <adrian.hunter@intel.com> |
|---|---|
| Date | 2015-08-18 11:20 +0200 |
| Message-ID | <pYLdM-1Qz-9@gated-at.bofh.it> |
| In reply to | #1209074 |
On 18/08/15 09:39, Adrian Hunter wrote: > On 17/08/15 22:58, Arnaldo Carvalho de Melo wrote: >> Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu: >>> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote: >>>> Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu: >>>>> On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote: >>>>>> 1.92% usleep [unknown] [.] 0x00007fa0ff695086 >>>>>> 1.60% usleep [unknown] [.] 0xffffffff811c91d0 >>>>>> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d >>>>>> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7 >>>> >>>>> It is very weird that it doesn't know the dso. >>>> >>>>> I presume there is nothing unusual about the environment e.g. in a chroot or anything >>>> >>>>> What if you try a different event e.g. perf record --per-thread -e cycles sleep 1 >>>> >>>> [root@zoo ~]# perf record --per-thread -e cycles sleep 1 >>>> [ perf record: Woken up 1 times to write data ] >>>> [ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ] >>>> [root@zoo ~]# perf report | grep -v ^# | head -5 >>>> 42.57% sleep libc-2.20.so [.] malloc_hook_ini >>>> 41.81% sleep [kernel.vmlinux] [k] filemap_fault >>>> 14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range >>>> 1.18% sleep [kernel.vmlinux] [k] strlcpy >>>> 0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe >>>> [root@zoo ~]# >>>> >>>> [root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]' >>>> 42.57% sleep [.] malloc_hook_ini >>>> >>>> [root@zoo ~]# >>>> >>>> [root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1 >>>> [ perf record: Woken up 1 times to write data ] >>>> [ perf record: Captured and wrote 1.825 MB perf.data ] >>>> [root@zoo ~]# perf report | grep -v ^# | head -5 >>>> Warning: >>>> 79074 instruction trace errors >>>> 2.80% usleep [unknown] [.] 0x00007f48888aa061 >>>> [root@zoo ~]# >>> >>> Running out of ideas. Can you somehow share or send me the offending perf.data file? >> >> http://vger.kernel.org/~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz > > Says: You don't have permission to access > /~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz on this server. > >> >> It works if I use a tip/master kernel: >> >> [root@perf4 ~]# uname -r >> 4.2.0-rc7+ >> [root@perf4 ~]# uname -r >> 4.2.0-rc7+ >> [root@perf4 ~]# perf record --per-thread -e intel_bts// usleep 1 >> [ perf record: Woken up 1 times to write data ] >> [ perf record: Captured and wrote 1.785 MB perf.data ] >> [root@perf4 ~]# dmesg | grep Performance >> [ 0.188477] Performance Events: PEBS fmt2+, 16-deep LBR, Broadwell >> events, full-width counters, Intel PMU driver. >> [root@perf4 ~]# perf report --stdio | grep -v ^# | head -10 >> >> >> >> >> 10.81% usleep libc-2.17.so [.] _dl_addr >> 6.56% usleep [kernel.kallsyms] [.] unmap_single_vma >> 3.33% usleep ld-2.17.so [.] strcmp >> 2.53% usleep [kernel.kallsyms] [.] mem_cgroup_begin_page_stat >> 2.49% usleep ld-2.17.so [.] _dl_lookup_symbol_x >> 2.39% usleep ld-2.17.so [.] _dl_relocate_object >> [root@perf4 ~]# >> >> Probably some fix for the kernel driver is missing? > > Works for me though. I looked at the code and noticed a minor issue, but I don't think it is the cause of the problem. I sent a fix - see "perf tools: Fix use of wrong event when processing exit events" -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Arnaldo Carvalho de Melo <acme@kernel.org> |
|---|---|
| Date | 2015-08-18 18:20 +0200 |
| Message-ID | <pYRMe-2Xf-31@gated-at.bofh.it> |
| In reply to | #1209074 |
Em Tue, Aug 18, 2015 at 09:39:46AM +0300, Adrian Hunter escreveu: > On 17/08/15 22:58, Arnaldo Carvalho de Melo wrote: > > Em Mon, Aug 17, 2015 at 10:09:26PM +0300, Adrian Hunter escreveu: > >> On 17/08/2015 8:58 p.m., Arnaldo Carvalho de Melo wrote: > >>> Em Mon, Aug 17, 2015 at 08:43:09PM +0300, Adrian Hunter escreveu: > >>>> On 17/08/2015 6:52 p.m., Arnaldo Carvalho de Melo wrote: > >>>>> 1.92% usleep [unknown] [.] 0x00007fa0ff695086 > >>>>> 1.60% usleep [unknown] [.] 0xffffffff811c91d0 > >>>>> 1.48% usleep [unknown] [.] 0x00007fa0ffb3030d > >>>>> 1.24% usleep [unknown] [.] 0x00007fa0ff6950c7 > >>> > >>>> It is very weird that it doesn't know the dso. > >>> > >>>> I presume there is nothing unusual about the environment e.g. in a chroot or anything > >>> > >>>> What if you try a different event e.g. perf record --per-thread -e cycles sleep 1 > >>> > >>> [root@zoo ~]# perf record --per-thread -e cycles sleep 1 > >>> [ perf record: Woken up 1 times to write data ] > >>> [ perf record: Captured and wrote 0.014 MB perf.data (9 samples) ] > >>> [root@zoo ~]# perf report | grep -v ^# | head -5 > >>> 42.57% sleep libc-2.20.so [.] malloc_hook_ini > >>> 41.81% sleep [kernel.vmlinux] [k] filemap_fault > >>> 14.35% sleep [kernel.vmlinux] [k] flush_tlb_mm_range > >>> 1.18% sleep [kernel.vmlinux] [k] strlcpy > >>> 0.09% sleep [kernel.vmlinux] [k] native_write_msr_safe > >>> [root@zoo ~]# > >>> > >>> [root@zoo ~]# perf report --dsos libc-2.20.so | grep -v '^[#]' > >>> 42.57% sleep [.] malloc_hook_ini > >>> > >>> [root@zoo ~]# > >>> > >>> [root@zoo ~]# perf record --per-thread -e intel_bts// usleep 1 > >>> [ perf record: Woken up 1 times to write data ] > >>> [ perf record: Captured and wrote 1.825 MB perf.data ] > >>> [root@zoo ~]# perf report | grep -v ^# | head -5 > >>> Warning: > >>> 79074 instruction trace errors > >>> 2.80% usleep [unknown] [.] 0x00007f48888aa061 > >>> [root@zoo ~]# > >> > >> Running out of ideas. Can you somehow share or send me the offending perf.data file? > > > > http://vger.kernel.org/~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz > > Says: You don't have permission to access > /~acme/perf/perf.data.intel_bts-4.2.0-rc5+.xz on this server. Ooops, fixed. > > It works if I use a tip/master kernel: > > > > [root@perf4 ~]# uname -r > > 4.2.0-rc7+ > > [root@perf4 ~]# uname -r > > 4.2.0-rc7+ > > [root@perf4 ~]# perf record --per-thread -e intel_bts// usleep 1 > > [ perf record: Woken up 1 times to write data ] > > [ perf record: Captured and wrote 1.785 MB perf.data ] > > [root@perf4 ~]# dmesg | grep Performance > > [ 0.188477] Performance Events: PEBS fmt2+, 16-deep LBR, Broadwell > > events, full-width counters, Intel PMU driver. > > [root@perf4 ~]# perf report --stdio | grep -v ^# | head -10 > > > > > > > > > > 10.81% usleep libc-2.17.so [.] _dl_addr > > 6.56% usleep [kernel.kallsyms] [.] unmap_single_vma > > 3.33% usleep ld-2.17.so [.] strcmp > > 2.53% usleep [kernel.kallsyms] [.] mem_cgroup_begin_page_stat > > 2.49% usleep ld-2.17.so [.] _dl_lookup_symbol_x > > 2.39% usleep ld-2.17.so [.] _dl_relocate_object > > [root@perf4 ~]# > > > > Probably some fix for the kernel driver is missing? > > Works for me though. Works for you if you test in lockstep the tooling with the kernel sources, right? It works for me as well, if I use the latest tip/master tooling _and_ kernel, my report was for using the 4.2.0-rc latest for the kernel and the tooling in tip/master. I think this would be just a matter of having a better message, or perhaps some fix that we need to send to the stable@kernel.org guys, so that the new tooling works with a slightly older kernel. Anyway, consider looking at that perf.data file that I fixed the permissions on vger, and I will look at the fix you mentioned in another message. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web