On Fri, 28 Jan 2011, Arnaldo Carvalho de Melo wrote: > > So far I wrote some that generate tracepoint events, but I can envision > for instance, figuring out the size of the L2 processor cache, creating > an array that is of that size, then go on touching it till it trashes > the cache while measuring the relevant event.
Unfortunately it is harder to validate perf events than you might guess. For your L2 example, most processors do hardware prefetch in very hard to model way, so the "expected" value never matches anything that you get with the counters. This is even if you write the tests in assembly language to avoid any weird behavior from the C compilers (and there can be, even on something as simple as an array walk). Even things you might think are simple, like retired-instructions can vary wildly. There are enough differences caused by Linux and processor errata with retired-instructions that I wrote a whole 10 page paper about the differences you see. I have started writing some validation tests, though they use the PAPI library which runs on top of perf-events. You can see that and other validation work linked to here: http://web.eecs.utk.edu/~vweaver1/projects/validation-tests/ Vince -- 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
