All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: Document ftrace command line limitations
Date: Mon, 03 Nov 2014 21:30:27 -0500	[thread overview]
Message-ID: <54583A43.2000303@hurleysoftware.com> (raw)
In-Reply-To: <20141103211431.0d8a80b8@gandalf.local.home>

On 11/03/2014 09:14 PM, Steven Rostedt wrote:
> On Mon,  3 Nov 2014 20:45:25 -0500
> Peter Hurley <peter@hurleysoftware.com> wrote:
> 
>> When using the function or function_graph tracers from the command
>> line, certain command line options have limitations.
>>
>> Document that only kernel built-in functions can be filtered via
>> ftrace_filter= or ftrace_graph_filter=. Also document that tracer-
>> specific options cannot be set on the command line via trace_options.
> 
> It's not just a command line limitation. The command line behaves
> exactly like set_ftrace_filter does. That is, it only affects the
> functions that are loaded when the filter is modified. It never updates
> functions that will be loaded when modules are.
> 
> Adding this documentation makes it seem that set_ftrace_filter has the
> ability to update functions that were not loaded yet. This is not true.
> The command line filtering behaves exactly like set_ftrace_filter does.
> It only enables the functions that are loaded at the time the function
> is set. Which was at boot up, and it just happens to be only built in
> functions at that time.

Ah, ok. I'll clarify those two lines and add to the documentation in
Documentation/trace/ftrace.txt


      reply	other threads:[~2014-11-04  2:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  1:45 [PATCH] ftrace: Document ftrace command line limitations Peter Hurley
2014-11-04  2:14 ` Steven Rostedt
2014-11-04  2:30   ` Peter Hurley [this message]

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=54583A43.2000303@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.