From: Pekka Paalanen <pq@iki.fi>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [Patch -tip 1/3] Tracing/ftrace: Relay unhandled entry output
Date: Thu, 25 Sep 2008 19:01:49 +0300 [thread overview]
Message-ID: <20080925190149.208ee3a4@daedalus.pq.iki.fi> (raw)
In-Reply-To: <c62985530809250856l2c4e827cv2123b6c3c21210d7@mail.gmail.com>
On Thu, 25 Sep 2008 17:56:32 +0200
"Frédéric Weisbecker" <fweisbec@gmail.com> wrote:
> 2008/9/25 Pekka Paalanen <pq@iki.fi>:
> > My understanding is that the pipe will be broken only, if the trace
> > framework believes tracing is disabled. Recall the discussion about
> > tracer_enabled = 0. Which is a bug, and I hoped Steven would have
> > commented on how to fix that properly.
> >
> > Or was it fixed already, and this is a different issue?
> > I didn't notice.
>
> Actually there was two bugs which broke the pipe:
> _ As you say the old one when none tracer put tracer_enabled = 0
> _ And the new one I described here.
>
> I think the first is fixed since none tracer has been replaced by "nop
> tracer" (a recently implemented) which doesn't touch
> tracer_enabled at all.
Oh cool, sounds like I should try linux-next when I can.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2008-09-25 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 12:19 Frédéric Weisbecker
2008-09-25 12:38 ` Ingo Molnar
2008-09-25 14:56 ` Frédéric Weisbecker
2008-09-25 15:09 ` Pekka Paalanen
2008-09-25 15:33 ` Frédéric Weisbecker
2008-09-25 15:49 ` Pekka Paalanen
2008-09-25 15:56 ` Frédéric Weisbecker
2008-09-25 16:01 ` Pekka Paalanen [this message]
2008-09-25 16:40 ` Frédéric Weisbecker
2008-09-27 17:50 ` Ingo Molnar
2008-09-29 9:29 ` Frédéric Weisbecker
2008-09-27 17:53 ` Ingo Molnar
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=20080925190149.208ee3a4@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®