On Tue, Jan 13, 2015 at 12:47:59PM +0000, Zhiqiang Zhang wrote: > From:Jiri Olsa <jolsa@xxxxxxxxxx> > > commit f61ff6c06dc8f32c7036013ad802c899ec590607 upstream > > Linus reported perf report command being interrupted due to processing > of 'out of order' event, with following error: > > Timestamp below last timeslice flush > 0x5733a8 [0x28]: failed to process type: 3 > > I could reproduce the issue and in my case it was caused by one CPU > (mmap) being behind during record and userspace mmap reader seeing the > data after other CPUs data were already stored. > > This is expected under some circumstances because we need to limit the > number of events that we queue for reordering when we receive a > PERF_RECORD_FINISHED_ROUND or when we force flush due to memory > pressure. > > Reported-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Jiri Olsa <jolsa@xxxxxxxxxx> > Acked-by: Ingo Molnar <mingo@xxxxxxxxxx> > Cc: Andi Kleen <ak@xxxxxxxxxxxxxxx> > Cc: Corey Ashford <cjashfor@xxxxxxxxxxxxxxxxxx> > Cc: David Ahern <dsahern@xxxxxxxxx> > Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx> > Cc: Ingo Molnar <mingo@xxxxxxxxxx> > Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> > Cc: Matt Fleming <matt.fleming@xxxxxxxxx> > Cc: Namhyung Kim <namhyung@xxxxxxxxxx> > Cc: Paul Mackerras <paulus@xxxxxxxxx> > Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> > Cc: Stephane Eranian <eranian@xxxxxxxxxx> > Link: http://lkml.kernel.org/r/1417016371-30249-1-git-send-email-jolsa@xxxxxxxxxx > Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> > > [zhangzhiqiang: backport to 3.10: > - adjust context > - commit f61ff6c06d struct events_stats was defined in tools/perf/util/event.h > while 3.10 stable defined in tools/perf/util/hist.h. > - 3.10 stable there is no pr_oe_time() which used for debug. > - After the above adjustments, becomes same to the original patch: > https://github.com/torvalds/linux/commit/f61ff6c06dc8f32c7036013ad802c899ec590607 seems ok jirka -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html