From: Ingo Molnar <mingo@elte.hu>
To: Simon K??mpflein <s.kaempflein@gmx.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>,
Fr??d??ric Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: perf counters: problem with perf record
Date: Sun, 15 Nov 2009 11:34:59 +0100 [thread overview]
Message-ID: <20091115103459.GC24931@elte.hu> (raw)
In-Reply-To: <4AFFD2B8.5060400@gmx.de>
* Simon K??mpflein <s.kaempflein@gmx.de> wrote:
> Peter Zijlstra schrieb:
> > On Sun, 2009-11-15 at 03:14 +1000, Simon K??mpflein wrote:
> >> Hello,
> >>
> >> I have a problem with the new kernel perf tools in kernel 2.6.31.6 (very
> >> nice tools by the way). I like to monitor the cache-misses of a program.
> >> "perf stat -e cache-misses program" works without problems, but I can't
> >> get "perf record -e cache-misses program" working (even running as root
> >> and CONFIG_PERF_COUNTERS=y):
> >>
> >> Error: perfcounter syscall returned with -1 (Operation not supported)
> >> Fatal: No CONFIG_PERF_COUNTERS=y kernel support configured?
> >>
> >> My CPU is a "Intel(R) Pentium(R) M processor 1.80GHz":
> >
> > Does the bootlog perchance contain the output of?
> >
> > if (!cpu_has_apic) {
> > pr_info("no APIC, boot with the \"lapic\" boot parameter
> > to force-enable it.\n");
> > pr_info("no hardware sampling interrupt available.\n");
> > x86_pmu.apic = 0;
> > }
>
> Yes. I didn't realize that it has something to do with the Performance
> Counters because I didn't see that it belongs to the Performance Counter
> output.
> Maybe it's a good idea to add another comment making it clear that the
> performance counters are not fully working in this case. Or detect this
> case in "perf-record" and output a message relating to that.
Ok. Mind sending a patch that changes the message so that it explains it
all to you more clearly?
> > And does booting with the suggested lapic parameter cure your problems?
> >
>
> Yes, thank you!
Great.
You might want to send another patch that allows the .config enabling of
that lapic boot parameter. It sucks to carry around boot parameters.
Ingo
next prev parent reply other threads:[~2009-11-15 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 17:14 perf counters: problem with perf record Simon Kämpflein
2009-11-14 19:46 ` Peter Zijlstra
2009-11-15 10:06 ` Simon Kämpflein
2009-11-15 10:34 ` Ingo Molnar [this message]
2009-11-16 5:25 ` Simon Kämpflein
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=20091115103459.GC24931@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.kaempflein@gmx.de \
/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