Howdy!
I'm a first-time user of toplev.py today. The -l option isn't working
for me, and I'm wondering if someone can help me understand why?
I've tested with a few different programs under test and combinations
of -l<n>, -v, and -d. No luck yet. Here's an example below:
$ uname -a
Linux chur 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
$ perf --version
perf version 3.11.1
$ git log | head -1
commit c765cf1ae73efce887468abf4c7a3f4fbe549763
$ ./toplev.py -v -d -l4 sleep 5
WARNING: HT enabled
Measuring multiple processes/threads on the same core may not be reliable.
perf stat -x, -e '{r2c2,r100030d,r19c,r10e,cycles}' sleep 5
Frontend Bound: 10.11% below
This category reflects slots where the Frontend of the
processor undersupplies
its Backend.
Bad Speculation: 9.05% below
This category reflects slots wasted due to incorrect speculations, which
include slots used to allocate uops that do not eventually get
retired and
slots for which allocation was blocked due to recovery from
earlier incorrect
speculation. For example, wasted work due to miss-predicted branches is
categorized under the Bad Speculation category
Backend Bound: 59.36% above
This category reflects slots where no uops are being delivered
due to a lack
of required resources for accepting more uops in the Backend
of the pipeline.
Retiring: 21.48% below
This category reflects slots utilized by good uops i.e.
allocated uops that
eventually get retired.
any tips would be much appreciated.
Cheers,
-Luke
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
