public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Kämpflein" <s.kaempflein@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: perf counters: problem with perf record
Date: Sun, 15 Nov 2009 20:06:48 +1000	[thread overview]
Message-ID: <4AFFD2B8.5060400@gmx.de> (raw)
In-Reply-To: <1258227980.30187.512.camel@laptop>

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.

> And does booting with the suggested lapic parameter cure your problems?
> 

Yes, thank you!

Regars,
Simon


  reply	other threads:[~2009-11-15 10:07 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 [this message]
2009-11-15 10:34     ` Ingo Molnar
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=4AFFD2B8.5060400@gmx.de \
    --to=s.kaempflein@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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