
Messages in this thread
SubjectRe: [PATCH 2/2] perf: Use hot regs with software sched switch/migrate events
On Tue, 2010-03-30 at 00:43 +0200, Frederic Weisbecker wrote:

> Actually I have doubts about what should be the strict sense
> of exclude_kernel.
> Does that mean we exclude any event that happened in the kernel?
> Or does that mean we exclude the part that happened in the kernel?
> Depending on the case, we do either.
> In perf_swevent_hrtimer(), we simply go back to task_pt_regs()
> if exclude_kernel.
> But in other software events, we don't such fix, we actually
> filter out the event if it is not user_mode().
> So, I'm a bit confused on what to do.
> I'm tempted to adopt the meaning from perf_swevent_hrtimer()
> for software events too, I'm not sure...

Yes, that is indeed a good point. Problem is that perf_swevent_hrtimer()
is not quite correct either, since strictly speaking its timeline should
stop on the excluded region, but implementing that would make context
switches horribly expensive.

That said, the option that would be most correct is to simply not count
these events, and in that respect the current behaviour seems best.

Maybe we can make a new perf feature that would for each kernel event
(hw pmu included) report on the userspace state, would that be useful?

 \ /
  Last update: 2010-03-30 20:57    [W:0.198 / U:0.072 seconds]
©2003-2011 Jasper Spaans