linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Petlan <mpetlan@redhat.com>
To: Patrick Agrain <patrick.agrain@al-enterprise.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf records  no samples on an IBM x3250M5
Date: Thu, 03 Dec 2015 16:42:25 +0100	[thread overview]
Message-ID: <1449157345.24573.149.camel@redhat.com> (raw)
In-Reply-To: <loom.20151203T151613-447@post.gmane.org>

On Thu, 2015-12-03 at 14:26 +0000, Patrick Agrain wrote:
> Hello,
> 
> perf record no samples in perf.data on an IBM x3250M5.
> perf stat is OK (in that way that it displays some stats).

1) Which stats are displayed? Do the basic events from "perf list hw"
work?

perf stat -e cycles -- sleep 1
perf stat -e instructions -- sleep 1


2) What does "perf list hw" show?


> Before digging into the hardware, let us check together if my 'perf'
> compilation fulfills all requirements :
> 
> I tried to compile the perf inside a linux kernel 3.19 from kernel.org.
> Compilation is made on a Centos 6.6 with following info:
> 
> [root@localhost Desktop]# cat /proc/version
> Linux version 2.6.32-504.23.4.el6.i686 (mockbuild@c6b9.bsys.dev.centos.org)
> (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Tue Jun 9
> 18:09:42 UTC 2015
> [root@localhost Desktop]# cd /usr/src/kernels/linux-3.19/tools/perf/
> [root@localhost perf]# make
>   BUILD:   Doing 'make -j1' parallel build
> config/Makefile:128: The path 'python-config' is not executable.
> config/Makefile:390: No libunwind found. Please install libunwind-dev[el] >=
> 1.1 and/or set LIBUNWIND_DIR
> config/Makefile:494: Missing perl devel files. Disabling perl scripting
> support, consider installing perl-ExtUtils-Embed
> config/Makefile:525: No python-config tool was found
> config/Makefile:525: Python support will not be built
> config/Makefile:627: No numa.h found, disables 'perf bench numa mem'
> benchmark, please install numactl-devel/libnuma-devel/libnuma-dev
> 
> Auto-detecting system features:
> ...                         dwarf: [ on  ]
> ...                         glibc: [ on  ]
> ...                          gtk2: [ on  ]
> ...                      libaudit: [ on  ]
> ...                        libbfd: [ on  ]
> ...                        libelf: [ on  ]
> ...                       libnuma: [ OFF ]
> ...                       libperl: [ OFF ]
> ...                     libpython: [ OFF ]
> ...                      libslang: [ on  ]
> ...                     libunwind: [ OFF ]
> ...            libdw-dwarf-unwind: [ on  ]
> ...                          zlib: [ on  ]
> ...     DWARF post unwind library: libdw
> 
>   CC       perf.o
>   LINK     perf
>   GEN      perf-archive
>   GEN      perf-with-kcore
> [root@localhost perf]#
> 
> Do you see here anything unusual (or wrong, or missing) ?
> FYI, I saw no error message during compilation.
> 
> Thanks.
> Kind regards,
> Patrick Agrain
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-03 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 14:26 perf records no samples on an IBM x3250M5 Patrick Agrain
2015-12-03 15:42 ` Michael Petlan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-04  8:45 Patrick Agrain

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=1449157345.24573.149.camel@redhat.com \
    --to=mpetlan@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=patrick.agrain@al-enterprise.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).