]> git.kernelconcepts.de Git - karo-tx-linux.git/commit
ftrace: Update the kconfig for DYNAMIC_FTRACE
authorSteven Rostedt <srostedt@redhat.com>
Thu, 28 Feb 2013 02:48:09 +0000 (21:48 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 20 Mar 2013 15:03:28 +0000 (15:03 +0000)
commit3ac94a54e1e69d5e510c92c56dda242a7398ce54
tree8ac2fc5d7ccacf68f5c9482b0722fad4820af33c
parent7feecf3f2b587e535550bb3e7bf75b2fee06fccf
ftrace: Update the kconfig for DYNAMIC_FTRACE

commit db05021d49a994ee40a9735d9c3cb0060c9babb8 upstream.

The prompt to enable DYNAMIC_FTRACE (the ability to nop and
enable function tracing at run time) had a confusing statement:

 "enable/disable ftrace tracepoints dynamically"

This was written before tracepoints were added to the kernel,
but now that tracepoints have been added, this is very confusing
and has confused people enough to give wrong information during
presentations.

Not only that, I looked at the help text, and it still references
that dreaded daemon that use to wake up once a second to update
the nop locations and brick NICs, that hasn't been around for over
five years.

Time to bring the text up to the current decade.

Reported-by: Ezequiel Garcia <elezegarcia@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
kernel/trace/Kconfig