From: Minfei Huang <mnfhuang@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org, mhuang@redhat.com
Subject: Re: [REPOST PATCH] ftrace: Calculate the correct dyn_ftrace number to report to the userspace
Date: Thu, 22 Oct 2015 13:14:07 +0800 [thread overview]
Message-ID: <20151022051407.GA9292@t420s.redhat.com> (raw)
In-Reply-To: <20151015222545.45a22b7e@grimm.local.home>
On 10/15/15 at 10:25pm, Steven Rostedt wrote:
> On Thu, 17 Sep 2015 00:19:42 +0800
> Minfei Huang <mnfhuang@gmail.com> wrote:
>
> > Now, ftrace only calculate the dyn_ftrace number in the adding
> > breakpoint loop, not in adding update and finish update loop.
> >
> > Calculate the correct dyn_ftrace, once ftrace reports the failure message
> > to the userspace.
> >
>
> Bah, your emails got lost in my Inbox. Sorry about that.
>
> I'll make an effort to look at this first thing tomorrow.
Ping. Any comment is appreciate.
Thanks
Minfei
>
> [ Cc'ing myself to remind me ]
>
> -- Steve
>
> > Signed-off-by: Minfei Huang <mnfhuang@gmail.com>
> > ---
> > arch/x86/kernel/ftrace.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
> > index 8b7b0a5..311bcf3 100644
> > --- a/arch/x86/kernel/ftrace.c
> > +++ b/arch/x86/kernel/ftrace.c
> > @@ -556,6 +556,7 @@ void ftrace_replace_code(int enable)
> > run_sync();
> >
> > report = "updating code";
> > + count = 0;
> >
> > for_ftrace_rec_iter(iter) {
> > rec = ftrace_rec_iter_record(iter);
> > @@ -563,11 +564,13 @@ void ftrace_replace_code(int enable)
> > ret = add_update(rec, enable);
> > if (ret)
> > goto remove_breakpoints;
> > + count++;
> > }
> >
> > run_sync();
> >
> > report = "removing breakpoints";
> > + count = 0;
> >
> > for_ftrace_rec_iter(iter) {
> > rec = ftrace_rec_iter_record(iter);
> > @@ -575,6 +578,7 @@ void ftrace_replace_code(int enable)
> > ret = finish_update(rec, enable);
> > if (ret)
> > goto remove_breakpoints;
> > + count++;
> > }
> >
> > run_sync();
>
next prev parent reply other threads:[~2015-10-22 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 16:19 [REPOST PATCH] ftrace: Calculate the correct dyn_ftrace number to report to the userspace Minfei Huang
2015-10-16 2:25 ` Steven Rostedt
2015-10-22 5:14 ` Minfei Huang [this message]
2015-10-22 17:08 ` Steven Rostedt
2015-10-22 19:44 ` 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=20151022051407.GA9292@t420s.redhat.com \
--to=mnfhuang@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).