From: Steven Rostedt <rostedt@goodmis.org>
To: monstr@monstr.eu
Cc: wuzhangjin@gmail.com, linux-kernel@vger.kernel.org,
John Williams <john.williams@petalogix.com>
Subject: Re: dynamic ftrace - graph
Date: Fri, 11 Dec 2009 09:37:35 -0500 [thread overview]
Message-ID: <1260542255.2146.350.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4B21F4F6.5080600@monstr.eu>
On Fri, 2009-12-11 at 08:29 +0100, Michal Simek wrote:
> Steven Rostedt wrote:
> > Hi Michal,
> >
> > Sorry for such a late reply, you sent this email to me at the worst
> > time. My wife was having shoulder surgery and I heading for a
> > conference. I fell very far behind in email and I only now just noticed
> > this.
>
> No problem. I prepared Microblaze ftrace patches. You can find them in
> linux-next. I am going to send pull request to Linus soon that's why if
> you have any your comments please let me know.
>
Hey, if they work and they are only in your arch, then I'm fine with
them ;-)
> >
> >
> > I'll answer these ever though you may already figured it out.
> >
> > On Mon, 2009-11-09 at 17:52 +0100, Michal Simek wrote:
> >> Hi Steve and others,
> >>
> >> I have working dynamic ftrace function. :-)
> >>
> >> I look at __ftrace_modify_code function and I have one question about.
> >> Below are function which are called when I enable function_graph.
> >>
> >> I personally think that make more sense to call
> >> ftrace_enable_ftrace_graph_caller before ftrace_update_ftrace_func.
> >> The reason for it is that graph_caller enable calling graph tracing
> >> which should be setup before ftrace_update_ftrace_func which enable
> >> whole tracing function.
> >
> > Have you seen any difference in output with this?
>
> I haven't tested it. It was just suggestion. I don't know if is relevant
> or not.
I'm not sure it is relevant. Those are enabled in stop_machine so the
only thing you would be missing is the tracer enabling itself.
-- Steve
next prev parent reply other threads:[~2009-12-11 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 16:52 Michal Simek
2009-12-11 4:37 ` Steven Rostedt
2009-12-11 7:29 ` Michal Simek
2009-12-11 14:37 ` Steven Rostedt [this message]
2009-12-11 14:40 ` Michal Simek
2009-12-11 14:54 ` Steven Rostedt
2009-12-11 15:28 ` Michal Simek
2009-12-11 15:54 ` Steven Rostedt
2009-12-11 16:42 ` Michal Simek
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=1260542255.2146.350.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=wuzhangjin@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
all inboxes | Powered by JetHome®