From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 0/2] tracing: lost events changes
Date: Wed, 14 Apr 2010 18:00:05 +0200 [thread overview]
Message-ID: <20100414160005.GA26429@elte.hu> (raw)
In-Reply-To: <1271257888.19099.4.camel@localhost>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 2010-04-14 at 15:00 +0200, Jiri Olsa wrote:
> > hi,
> >
> > I noticed LOST EVENTS messages in the iterator "trace" file.
> > According to the comment from commit bc21b478 this won't work.
> >
> > <comment>
> > Note, it does not work with the iterator "trace" file, since it requires
> > the use of consuming the page from the ring buffer to determine how many
> > events were lost, which the iterator does not do.
> > </comment>
> >
> > I'm not sure the attached fix (2/2) is on the right place,
> > but stops the LOST EVENTS display for iterator "trace" file.
> >
>
> This has already been fixed by Lai:
>
> http://marc.info/?l=linux-kernel&m=127045871922996
>
> And I asked Ingo to pull it here:
>
> http://marc.info/?l=linux-kernel&m=127048065715829
Yeah - i pulled it earlier today and pushed it out about two hours ago.
Ingo
next prev parent reply other threads:[~2010-04-14 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 13:00 [PATCH 0/2] tracing: lost events changes Jiri Olsa
2010-04-14 13:00 ` [PATCH 1/2] tracing: adding lost-events option Jiri Olsa
2010-04-14 13:00 ` [PATCH 2/2] tracing: supress lost events message for iterator "trace" Jiri Olsa
2010-04-14 15:11 ` [PATCH 0/2] tracing: lost events changes Steven Rostedt
2010-04-14 16:00 ` Ingo Molnar [this message]
2010-04-14 16:15 ` Steven Rostedt
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=20100414160005.GA26429@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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