Re: x86_pmu_start WARN_ON.

From: Vince Weaver
Date: Thu Feb 20 2014 - 13:01:37 EST


On Thu, 20 Feb 2014, Peter Zijlstra wrote:

> On Wed, Feb 19, 2014 at 05:34:49PM -0500, Vince Weaver wrote:
> > So where would the NMI counter event get disabled? Would it never get
> > disabled, just because it's always running and always gets the same fixed
> > slot? Why isn't this a problem all the time, not just with corner cases?
>
> Well it could get another counter assignment I suppose; there's no
> guarantee it always ends up in the fixed counter although that's rather
> likely.
>
> > Is somehow n_added getting confused?
>
> I'd expect worse than a warning if that happened, but who knows.
>
> You could try with the below; make sure you've got CONFIG_FUNCTION_TRACER=y.

> # cat /debug/tracing/trace | bzip2 -9 > ~/trace.bz2
>
> And send that (and look at it of course).

attached, it's not very big.

Vince

Attachment: trace.bz2
Description: Binary data