lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 14 Nov 2009 20:46:20 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Simon Kämpflein <s.kaempflein@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: perf counters: problem with perf record

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?
> 
> strace of "perf stat":
> SYS_336(0x8508da0, 0x1074, 0xffffffff, 0xffffffff, 0) = 3
> 
> strace of "perf record":
> SYS_336(0x8508da0, 0xf85, 0xffffffff, 0xffffffff, 0) = -1 EOPNOTSUPP
> (Operation not supported)
> 
> My CPU is a "Intel(R) Pentium(R) M processor 1.80GHz":
> [    0.004337] p6 PMU driver.
> [    0.004343] ... version:                 0
> [    0.004345] ... bit width:               32
> [    0.004347] ... generic counters:        2
> [    0.004349] ... value mask:              00000000ffffffff
> [    0.004351] ... max period:              000000007fffffff
> [    0.004353] ... fixed-purpose counters:  0
> [    0.004355] ... counter mask:            0000000000000003

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;
        }

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ