mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Preisner <linux@tpreisner.de>
Cc: asdf@asdf.de, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: add simple oneshot function tracer
Date: Mon, 17 Jun 2019 20:16:27 -0400	[thread overview]
Message-ID: <20190617201627.647547c7@gandalf.local.home> (raw)
In-Reply-To: <20190612212935.4xq6dyua5d5vrrvj@stud.informatik.uni-erlangen.de>

On Wed, 12 Jun 2019 23:29:35 +0200
Thomas Preisner <linux@tpreisner.de> wrote:

Hi Thomas,

BTW, what email client do you use, because your replies seem to confuse
my email client (claws-mail) and it doesn't thread them at all.
Although they do look fine on mutt (when I view my LKML folder). Looks
like it doesn't create a "References:" header.

> On Tue, 11 Jun 2019 17:52:37 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > What do you mean? The function profile has its own file to enable it:
> > 
> >  echo 1 > /sys/kernel/tracing/function_profile_enabled
> >  
> >  And disable it:
> >  
> >   echo 0 > /sys/kernel/tracing/function_profile_enabled
> >   
> >   -- Steve  
> 
> Yes, I am aware of the function profiler providing a file operation for
> enabling and disabling itself. However, my oneshot profiler as of [PATCH
> v2] is a separate tracer/profiler without this file operation.
> 
> As this oneshot profiler is intended to be used for coverage/usage
> reports I want it to be able to record functions as soon as possible
> during bootup. Therefore, I just permanently activated the oneshot
> profiler since as of now there is no means to activate it or the
> function profiler via kernel commandline just like the normal tracers.
> 
> Still, if you want to I can add the file operation for
> enabling/disabling this new profiler together with a new kernel
> commandline argument for this profiler?
> 
> Or what would be your prefered way?
> 

Hmm, I guess I still need to think about exactly what this is for.
Perhaps we could add a "oneshot" option to the function tracer, and
when set it will only trace a function once? Is there a strong reason
to add a new event type "oneshot_entry"? It may be useful to record the
parent of the function that triggered the first instance as well.

I'm still trying to get a grip around exactly what use cases this would
be good for. Especially when adding new functionality like this.

-- Steve


  reply	other threads:[~2019-06-18  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29  9:31 Thomas Preisner
2019-05-29 14:45 ` Steven Rostedt
2019-06-11 20:33   ` [PATCH v2] ftrace: add simple oneshot function profiler Thomas Preisner
     [not found]   ` <20190611203312.13653-1-linux@tpreisner.de>
2019-06-11 21:52     ` [PATCH] ftrace: add simple oneshot function tracer Steven Rostedt
2019-06-12 21:29   ` Thomas Preisner
2019-06-18  0:16     ` Steven Rostedt [this message]
2019-06-23 12:05       ` Thomas Preisner
2019-06-26 16:04         ` Steven Rostedt
2019-07-09 13:53           ` Thomas Preisner

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=20190617201627.647547c7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=asdf@asdf.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@tpreisner.de \
    --cc=mingo@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

all inboxes | Powered by JetHome®