Peter Zijlstra <[email protected]> writes: > On Fri, Dec 18, 2015 at 05:07:34PM +0200, Alexander Shishkin wrote: >> Peter Zijlstra <[email protected]> writes: >> >> > @@ -2774,9 +2696,6 @@ static void perf_event_context_sched_in( >> > */ >> > cpu_ctx_sched_out(cpuctx, EVENT_FLEXIBLE); >> > >> > - if (ctx->nr_events) >> > - cpuctx->task_ctx = ctx; >> > - >> > perf_event_sched_in(cpuctx, cpuctx->task_ctx, task); >> >> This then should probably become >> >> perf_event_sched_in(cpuctx, ctx, task); >> >> otherwise task contexts just don't get scheduled any more. > > Very good, thanks! > > Running with that triggers another WARN, I'll have a look at that later > tonight.
Hmm, is it the one from event_function() where a task context is scheduled, but is inactive and/or doesn't have events? I think there's also more fun to be had there now that you've started digging it up, I'll also poke at it more later today. Regards, -- Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
