Em Wed, Mar 25, 2020 at 11:40:36PM +0430, ahmadkhorrami escreveu:
> Thanks. But should I attach the files to the e-mail?
Which files?
I want just that you run the commands and send us the output from them,
like I'll do here:
[acme@seventh perf]$ perf -vv
perf version 5.6.rc6.g0d33b3435253
dwarf: [ on ] # HAVE_DWARF_SUPPORT
dwarf_getlocations: [ on ] # HAVE_DWARF_GETLOCATIONS_SUPPORT
glibc: [ on ] # HAVE_GLIBC_SUPPORT
gtk2: [ on ] # HAVE_GTK2_SUPPORT
syscall_table: [ on ] # HAVE_SYSCALL_TABLE_SUPPORT
libbfd: [ on ] # HAVE_LIBBFD_SUPPORT
libelf: [ on ] # HAVE_LIBELF_SUPPORT
libnuma: [ on ] # HAVE_LIBNUMA_SUPPORT
numa_num_possible_cpus: [ on ] # HAVE_LIBNUMA_SUPPORT
libperl: [ on ] # HAVE_LIBPERL_SUPPORT
libpython: [ on ] # HAVE_LIBPYTHON_SUPPORT
libslang: [ on ] # HAVE_SLANG_SUPPORT
libcrypto: [ on ] # HAVE_LIBCRYPTO_SUPPORT
libunwind: [ on ] # HAVE_LIBUNWIND_SUPPORT
libdw-dwarf-unwind: [ on ] # HAVE_DWARF_SUPPORT
zlib: [ on ] # HAVE_ZLIB_SUPPORT
lzma: [ on ] # HAVE_LZMA_SUPPORT
get_cpuid: [ on ] # HAVE_AUXTRACE_SUPPORT
bpf: [ on ] # HAVE_LIBBPF_SUPPORT
aio: [ on ] # HAVE_AIO_SUPPORT
zstd: [ on ] # HAVE_ZSTD_SUPPORT
[acme@seventh perf]$ ldd ~/bin/perf
linux-vdso.so.1 (0x00007fffcb9cc000)
libunwind-x86_64.so.8 => /lib64/libunwind-x86_64.so.8 (0x00007f7c58d94000)
libunwind.so.8 => /lib64/libunwind.so.8 (0x00007f7c58d7a000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f7c58d51000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7c58d30000)
librt.so.1 => /lib64/librt.so.1 (0x00007f7c58d26000)
libm.so.6 => /lib64/libm.so.6 (0x00007f7c58be0000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7c58bd8000)
libelf.so.1 => /lib64/libelf.so.1 (0x00007f7c58bbd000)
libdw.so.1 => /lib64/libdw.so.1 (0x00007f7c58b1e000)
libslang.so.2 => /lib64/libslang.so.2 (0x00007f7c58846000)
libperl.so.5.28 => /lib64/libperl.so.5.28 (0x00007f7c5851e000)
libc.so.6 => /lib64/libc.so.6 (0x00007f7c58358000)
libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f7c580ee000)
libz.so.1 => /lib64/libz.so.1 (0x00007f7c580d4000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f7c58029000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f7c58022000)
libnuma.so.1 => /lib64/libnuma.so.1 (0x00007f7c58014000)
libbabeltrace-ctf.so.1 => /lib64/libbabeltrace-ctf.so.1 (0x00007f7c57fbe000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f7c57fa2000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7c58dd3000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f7c57f8e000)
libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f7c57f53000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f7c57f4e000)
libbabeltrace.so.1 => /lib64/libbabeltrace.so.1 (0x00007f7c57f3e000)
libpopt.so.0 => /lib64/libpopt.so.0 (0x00007f7c57f2e000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f7c57f24000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f7c57f1e000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f7c57dfa000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f7c57d86000)
[acme@seventh perf]$
Just like a did, no attachments please.
- Arnaldo
> On 2020-03-25 23:28, Arnaldo Carvalho de Melo wrote:
>
> >Em Wed, Mar 25, 2020 at 04:46:43PM +0100, Jiri Olsa escreveu: On
> >Wed, Mar 25, 2020 at 07:48:39PM +0430, ahmadkhorrami wrote: Hi,
> >
> >Could you give me some hints about where the actual problem takes
> >place? Is
> >the problem with "Perf" or the hardware part (i.e., "Hardware
> >Performance
> >Counters")? Can I revise the problem by simply modifying the code?
> >How much
> >work is needed?
> >heya,
> >might be some callchain processing bug, but I can't reproduce it
> >on my setup..
> >would you have/make some simple example that would reproduce the issue?
> >
> >Another option is that you'd send perf.data together with 'perf
> >archive' data.
> >
> >Also.. we support 2 dwarf unwinders (libunwind/libdw).. not sure
> >which one you
> >have compiled in, but would be helpful to see if the other shows
> >the same.
>
> perf -vv
>
> +
>
> ldd `which perf`
>
> Output will help us find out which unwinder is being used, as well as
> the version of perf being used.
>
> - Arnaldo
|