From: Ingo Molnar <mingo@elte.hu>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
fweisbec@gmail.com
Subject: Re: [PATCH v2] tracing/filters: add run-time field descriptions to TRACE_EVENT_FORMAT events
Date: Wed, 1 Apr 2009 14:21:22 +0200 [thread overview]
Message-ID: <20090401122122.GF12966@elte.hu> (raw)
In-Reply-To: <1238478529.6749.12.camel@bookworm>
* Tom Zanussi <tzanussi@gmail.com> wrote:
> The other is that for the really high-volume tracers e.g. the
> function tracer, the volume of filtered events can be so high that
> it pushes the unfiltered events out of the ring buffer before they
> can be read so e.g. cat'ing the trace file repeatedly shows either
> no output, or once in awhile some output but that isn't there the
> next time you read the trace, which isn't what you normally expect
> when reading the trace file. If you read from the trace_pipe file
> though, you can catch them before they disappear.
yeah - this artifact of the ringbuffer needs to be fixed too. Steve,
what's the plans on that?
Ingo
prev parent reply other threads:[~2009-04-01 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 5:48 Tom Zanussi
2009-04-01 12:21 ` Ingo Molnar [this message]
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=20090401122122.GF12966@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
/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