From: Daniel Ortiz <daniel.ortiz@tum.de>
To: linux-perf-users@vger.kernel.org
Subject: "precise" not supported when executing perf mem
Date: Wed, 22 Apr 2015 15:33:18 +0000 (UTC) [thread overview]
Message-ID: <mh8evt$ean$1@ger.gmane.org> (raw)
Hello
When I try to run perf mem I obtain the following error:
do@nux:~/perf$ sudo perf mem record ls
Error:
'precise' request may not be supported. Try removing 'p' modifier.
This happens despite cpuinfo reporting that the processor supports
PEBS. What could I be missing here that does not allow perf mem to work?
I am running a 64 bit system on Xubuntu with 4GB Ram, I am building perf
myself, but the error also appears with the precompiled version.
Regards
Daniel
My kernel: Linux nux 3.16.0-34-generic #47-Ubuntu SMP
perf: perf version 3.16.7-ckt8
Some cpuinfo output:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz
stepping : 7
microcode : 0x23
cpu MHz : 848.039
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
reply other threads:[~2015-04-23 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='mh8evt$ean$1@ger.gmane.org' \
--to=daniel.ortiz@tum.de \
--cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).