Re: Reading perf counters at ftrace trace boundaries
> Indeed. It doesn't actually have to be at every single ftrace > begin/exit. But possibly starting with some kind of every nth and then > drilling down as the culprit is incrementally singled-out.
That's what normal sampling already does.
If you're worried about systematic shadow effects just randomize a bit.