Mike Kravetz writes:
A small update from the last version. By popular demand, both
wall time (mftb) and cpu cycles(PURR) are collected for each call.
It is interesting to see these two values side by side in the
output files.
Did you see the patch from Anton that I posted a week or so ago, which
reduces the number of plpar_hcall_* functions? I'd rather the
instrumentation stuff was based on that.
My other comment is this: wouldn't it actually turn out simpler if we
read the timebase (and PURR, if we really want to do that too) in the
assembly code that implements plpar_hcall_*?
Paul.