Messages in this thread | | | Date | Thu, 20 Feb 2014 14:21:26 -0500 (EST) | From | Vince Weaver <> | Subject | Re: x86_pmu_start WARN_ON. |
| |
On Thu, 20 Feb 2014, Vince Weaver wrote:
> Might be relevant: check the last_cpu values. Right before the above > it looks like the thread gets moved from CPU 1 to CPU 0 > (possibly as a result of the long chain started with the > close() of the tracepoint event), > so the problem NMI watchdog event being enabled is a different one than > the one that was disabled just before.
so is this a false warning? If you get scheduled to a new CPU and there's an already running CPU-wide event, is that OK?
Or should x86_pmu_disable() be setting PERF_HES_STOPPED on all events? It looks like other architectures are (such as armpmu_stop() ).
Vince
| |