[lkml]   [2010]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 3/3 v2] perf: Update perf tool to monitor uncore events
On Sun, Nov 21, 2010 at 5:52 PM, Andi Kleen <> wrote:
>>> In fact I suspect uncore events are only really useful
>>> with "stat", but not with "top", or if they are used in top
>>> then the symbol reporting should be disabled.
>> I agree, uncore should only be used for counting on a
>> per-cpu basis. You can leave the perf tool as is, but

I meant one cpu per socket: perf stat -a -C 0 -e unc_clk_unhalted.
One could envision the tool picking one CPU per socket. It can
figure this out from the topology information in sysfs.

If you do perf stat -a -e unc_*, then you'll get into multiplexing very
quickly AND it is useless especially because auto aggregation will
yield bogus counts.

> I think you mean per socket base, right? per cpu (= cpu core thread)
> doesn't make sense for the uncore either.
> Per socket would need a new command line mode. The new mode should
> never report any symbols or processes, just events per socket.
> -Andi

 \ /
  Last update: 2010-11-23 10:21    [W:0.077 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site