[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53CD5DC6.3030605@gmail.com>
Date: Mon, 21 Jul 2014 12:36:54 -0600
From: David Ahern <dsahern@...il.com>
To: Adrian Hunter <adrian.hunter@...el.com>,
Andi Kleen <andi@...stfloor.org>
CC: Jiri Olsa <jolsa@...nel.org>, linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Jean Pihet <jean.pihet@...aro.org>,
Namhyung Kim <namhyung@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCHv3 00/19] perf tools: Factor ordered samples queue
On 7/21/14, 12:23 PM, Adrian Hunter wrote:
> On 21/07/2014 7:31 p.m., Andi Kleen wrote:
>> Jiri Olsa <jolsa@...hat.com> writes:
>>>
>>> [jolsa@...-x3650m4-01 perf]$ sudo ./perf report --stdio
>>> Timestamp below last timeslice flush
>>> 0x2276f58 [0x68]: failed to process type: 9
>>
>> FWIW we're seeing this frequently too.
>
> Jiri's example didn't work for me. Do you have one?
$ perf sched record -m 8192 -- perf bench sched all
# Running sched/messaging benchmark...
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 0.087 [sec]
# Running sched/pipe benchmark...
# Executed 1000000 pipe operations between two processes
Total time: 12.043 [sec]
12.043779 usecs/op
83030 ops/sec
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 289.549 MB perf.data (~12650569 samples) ]
0x54b4828 [0]: failed to process type: 0
No overload condition, no dropped chunks message - yet can't process events.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists