mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Minfei Huang <mnfhuang@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Minfei Huang <mhuang@redhat.com>,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [REPOST PATCH] ftrace: Remove the unused variant ftrace_update_time
Date: Wed, 16 Sep 2015 00:00:46 +0800	[thread overview]
Message-ID: <20150915160046.GA14393@t440s.lenovo> (raw)
In-Reply-To: <20150915115057.2b9bea60@gandalf.local.home>

On 09/15/15 at 11:50am, Steven Rostedt wrote:
> On Tue, 15 Sep 2015 23:37:39 +0800
> Minfei Huang <mnfhuang@gmail.com> wrote:
> 
>  
> > I think the variant ftrace_update_time is not used any more. Previously,
> > it is used to print the time how long ftrace will spend to update the
> > code in fucntion ftraced. 
> 
> Yes, I know what it measures. It's been on my todo list to export that
> out to userspace, as it is an interesting metric.
> 

Export the time which ftrace spent to update the all of the function?
How about exporting the time ftrace spent in latest time?

Thanks
Minfei

> > 
> > > 
> > > Maybe add it to the dyn_ftrace_total_info file?
> > > 
> > 
> > This file only uses the variant ftrace_update_tot_cnt which is stored
> > the updated function number.
> 
> But we can add to that file with a space delimited output.
> 
> -- Steve
> 

  reply	other threads:[~2015-09-15 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  7:10 Minfei Huang
2015-09-15 13:35 ` Steven Rostedt
2015-09-15 15:37   ` Minfei Huang
2015-09-15 15:50     ` Steven Rostedt
2015-09-15 16:00       ` Minfei Huang [this message]
2015-09-15 16:12         ` Steven Rostedt
2015-09-15 16:32           ` Minfei Huang
2015-09-15 17:01             ` Steven Rostedt
2015-09-16  2:16               ` Minfei Huang

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=20150915160046.GA14393@t440s.lenovo \
    --to=mnfhuang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhuang@redhat.com \
    --cc=mingo@redhat.com \
    --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®