aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorAndi Kleen <[email protected]>2014-09-22 15:27:06 -0700
committerIngo Molnar <[email protected]>2014-10-03 06:02:49 +0200
commit4f971248bc6ad2bb2a89a25a072ebfec5757d298 (patch)
tree0b3282180645dc7e7c9010e3c55b0721f9350d9c /tools/perf/util/scripting-engines/trace-event-python.c
parent69e8f5b15ef43da1e177665a3e2063711ee4c9de (diff)
perf/x86/intel/uncore: Fix minor race in box set up
I was looking for the trinity oops cause in the uncore driver. (so far didn't found it) However I found this tiny race: when a box is set up two threads on the same CPU, they may be setting up the box in parallel (e.g. with kernel preemption). This could lead to the reference count being increasing too much. Always recheck there is no existing cpu reference inside the lock. Signed-off-by: Andi Kleen <[email protected]> Signed-off-by: Peter Zijlstra (Intel) <[email protected]> Cc: [email protected] Cc: Arnaldo Carvalho de Melo <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions