From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Stanislav Fomichev <stfomichev@yandex-team.ru>,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, artagnon@gmail.com, rusty@rustcorp.com.au,
bp@suse.de
Subject: Re: [PATCH v4 0/4] perf timechart io mode
Date: Tue, 24 Jun 2014 20:51:34 +0200 [thread overview]
Message-ID: <20140624185134.GB1148@krava.brq.redhat.com> (raw)
In-Reply-To: <53A9B7A4.9050805@gmail.com>
On Tue, Jun 24, 2014 at 11:38:44AM -0600, David Ahern wrote:
> On 6/24/14, 10:57 AM, Stanislav Fomichev wrote:
> >On Tue, Jun 24, 2014 at 01:10:22PM +0400, Stanislav Fomichev wrote:
> >>>hum, got this when trying:
> >>>
> >>>[jolsa@krava perf]$ sudo ./perf timechart record -I
> >>>^C[ perf record: Woken up 2 times to write data ]
> >>>[ perf record: Captured and wrote 1.071 MB perf.data (~46806 samples) ]
> >>>[jolsa@krava perf]$ ./perf timechart
> >>>Invalid previous event (non-zero)!
> >>>0x113f80 [0x8]: failed to process type: 68
>
> I see this kind of message a lot, but typically in high event use cases
> (e.g., 100+MB files in a run of a few seconds). I usually increase the map
> size (-m 4096) and/or bump the priority of perf (-r1) and re-run the test.
maybe we dont need to fail in this case.. seems like it should
not be hard to detect, wanr and recover? ;-)
jirka
next prev parent reply other threads:[~2014-06-24 18:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 10:29 [PATCH v4 0/4] perf timechart io mode Stanislav Fomichev
2014-06-20 10:29 ` [PATCH 1/4] perf timechart: fix rendering in Firefox Stanislav Fomichev
2014-06-20 10:29 ` [PATCH 2/4] perf timechart: implement IO mode Stanislav Fomichev
2014-06-24 8:34 ` Jiri Olsa
2014-06-24 17:00 ` Stanislav Fomichev
2014-06-24 18:21 ` Jiri Olsa
2014-06-20 10:29 ` [PATCH 3/4] perf timechart: conditionally update start_time on fork Stanislav Fomichev
2014-06-20 10:29 ` [PATCH 4/4] perf timechart: add more options to IO mode Stanislav Fomichev
2014-06-24 6:43 ` [PATCH v4 0/4] perf timechart io mode Namhyung Kim
2014-06-24 8:41 ` Jiri Olsa
2014-06-24 9:10 ` Stanislav Fomichev
2014-06-24 16:57 ` Stanislav Fomichev
2014-06-24 17:01 ` Stanislav Fomichev
2014-06-24 17:38 ` David Ahern
2014-06-24 18:51 ` Jiri Olsa [this message]
2014-06-24 19:03 ` David Ahern
2014-06-25 11:20 ` Stanislav Fomichev
2014-06-25 14:01 ` David Ahern
2014-06-25 14:19 ` Stanislav Fomichev
2014-06-25 14:38 ` Jiri Olsa
2014-07-08 16:03 Stanislav Fomichev
2014-07-09 8:23 ` Namhyung Kim
2014-07-09 11:13 ` 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=20140624185134.GB1148@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=artagnon@gmail.com \
--cc=bp@suse.de \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=stfomichev@yandex-team.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.