From: Ingo Molnar <mingo@elte.hu>
To: Bruce Duncan <bwduncan@gmail.com>
Cc: Steven Rostedt <srostedt@redhat.com>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [git pull] ftrace for v2.6.27
Date: Fri, 15 Aug 2008 11:29:47 +0200 [thread overview]
Message-ID: <20080815092947.GE22209@elte.hu> (raw)
In-Reply-To: <200808131908.48721.bwduncan@gmail.com>
* Bruce Duncan <bwduncan@gmail.com> wrote:
> On Wednesday 13 August 2008 18:15:14 Steven Rostedt wrote:
> > Seems that the issue is with the "ftraced" daemon. The patch you
> > reverted was just a fix in the ftrace startup test. If something fails
> > in the start up test, that something is disabled. There was a bug in
> > the start up test that caused the dynamic ftrace to fail, and thus
> > disabling dynamic ftrace. The patch you reverted, was the fix to that
> > bug, so you indirectly disabled dynamic ftrace with that revert.
> >
> > I've been developing a way to get rid of the "ftraced" daemon. Here's a
> > big patch to do so against latest git (as of today). Can you go back to
> > the original git, apply this patch and see if you can resume again.
>
> I've been following that thread with great interest! Glad to see it's
> taking shape.
>
> The patch works beautifully. Thanks very much!
it's now integrated into tip/master (with a few other ftrace goodies),
if you want to test the end result check out tip/master via:
http://people.redhat.com/mingo/tip.git/README
Ingo
prev parent reply other threads:[~2008-08-15 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:22 [git pull] ftrace for v2.6.27 Ingo Molnar
2008-08-13 1:48 ` Bruce Duncan
2008-08-13 7:19 ` Ingo Molnar
2008-08-13 15:11 ` Steven Rostedt
2008-08-13 15:18 ` Ingo Molnar
2008-08-13 19:53 ` Andi Kleen
2008-08-13 17:15 ` Steven Rostedt
2008-08-13 18:08 ` Bruce Duncan
2008-08-15 9:29 ` 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=20080815092947.GE22209@elte.hu \
--to=mingo@elte.hu \
--cc=bwduncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.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