[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190612212935.4xq6dyua5d5vrrvj@stud.informatik.uni-erlangen.de>
Date: Wed, 12 Jun 2019 23:29:35 +0200
From: Thomas Preisner <linux@...eisner.de>
To: asdf@...f.de
Cc: linux@...eisner.de, Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH] ftrace: add simple oneshot function tracer
On Tue, 11 Jun 2019 17:52:37 -0400
Steven Rostedt <rostedt@...dmis.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?
Greetings,
Thomas Preisner
Powered by blists - more mailing lists