[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <m2y692vjq7.fsf@gmail.com>
Date: Tue, 09 Nov 2010 12:07:12 +0100
From: Francis Moreau <francis.moro@...il.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Stephane Eranian <eranian@...gle.com>,
linux-perf-users@...r.kernel.org
Subject: Re: perf tools miscellaneous questions
Frederic Weisbecker <fweisbec@...il.com> writes:
> On Thu, Nov 04, 2010 at 09:52:09AM +0100, Francis Moreau wrote:
[...]
>>
>> No problem, but yes this part should be documented somewhere. And I
>> think the syntax of event too, specially the modifier like 'u' or 'p'.
>
> Ah that is documented in "man perf-list".
Ok, after updating my 3 weeks old kernel, modifiers are now documented.
But I failed to generate it:
XMLTO perf-record.1
xmlto: /home/fmoreau/linux-2.6/tools/perf/Documentation/perf-record.xml does not validate (status 3)
BTW, what does 'skid' mean ? s(?) k(?) instruction delay ?
[...]
> I have the same problem. But running perf record with this :p works
> for me. Which is what we want: pebs is useful for sampling, not
> counting-only.
That makes sense but I still have a problem:
$ perf record -e cache-misses:p -p $(pgrep test)
Error: perfcounter syscall returned with -1 (No space left on device)
Fatal: No CONFIG_PERF_EVENTS=y kernel support configured?
> Ah and that won't work if you don't run some intel CPU I think. Check
> you have PEBS support in /proc/cpuinfo
It seems so:
$ grep -qi pebs /proc/cpuinfo && echo pebs
pebs
Thanks
--
Francis
--
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