From: Andi Kleen <ak@linux.intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf tools: Do not fail on processing out of order event
Date: Thu, 27 Nov 2014 11:44:13 -0800 [thread overview]
Message-ID: <20141127194413.GN10824@tassilo.jf.intel.com> (raw)
In-Reply-To: <1417016371-30249-1-git-send-email-jolsa@kernel.org>
On Wed, Nov 26, 2014 at 04:39:31PM +0100, Jiri Olsa wrote:
> 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.
I like the change. This problem hit me a couple of times too.
-Andi
next prev parent reply other threads:[~2014-11-27 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 15:39 Jiri Olsa
2014-11-26 15:44 ` Arnaldo Carvalho de Melo
2014-11-27 10:56 ` Ingo Molnar
2014-11-27 12:54 ` Jiri Olsa
2014-11-27 13:54 ` Arnaldo Carvalho de Melo
2014-11-27 13:53 ` Arnaldo Carvalho de Melo
2014-11-27 14:07 ` Jiri Olsa
2014-11-27 14:16 ` Arnaldo Carvalho de Melo
2014-11-27 14:23 ` Jiri Olsa
2014-11-27 14:45 ` Arnaldo Carvalho de Melo
2014-11-27 19:44 ` Andi Kleen [this message]
2014-12-09 10:16 ` [tip:perf/urgent] perf session: " tip-bot for Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141127194413.GN10824@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome