Messages in this thread | | | Subject | Re: [PATCH] perf events: Add stalled cycles generic event - PERF_COUNT_HW_STALLED_CYCLES | From | Peter Zijlstra <> | Date | Tue, 26 Apr 2011 11:25:56 +0200 |
| |
On Sat, 2011-04-23 at 23:16 -0700, Arun Sharma wrote: > Conceptually looks fine. I'd prefer a more precise name such as: > PERF_COUNT_EXECUTION_STALLED_CYCLES (to differentiate from frontend or > retirement stalls).
Very nice example!! This is the stuff we want people to do, but instead of focusing on the raw event aspect, put in a little more effort and see what it takes to make it work across the board.
None of the things you mention are very specific to Intel, afaik those concepts you listed: Retirement, Frontend (instruction decode/uop-issue), Backend (uop execution), I-cache (instruction fetch) map to pretty much all hardware I know (PMU coverage of these aspects aside).
So in fact you propose these concepts, and that is the kind of feedback perf wants and needs.
The thing that set off this whole discussion is that most people don't seem to believe in concepts and stick to their very narrow HPC every last cycle matters therefore we need absolute events mentality.
That too is a form of vendor lock, once you're so dependent on a particular platform the cost of switching increases dramatically. Furthermore very few people are actually interested in it.
That is not to say we should not enable those people, but the current state of affairs seems to be that some people are only interested in enabling that and simply don't care (and don't want to care) about cross platform performance analysis and useful abstractions.
We'd very much like to make the cost of entry -- the cost of supporting lowlevel capabilities -- the addition of high level concepts, means for the greater public to use them.
| |