summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoonsoo Kim <iamjoonsoo.kim@lge.com>2014-12-03 10:39:20 +0900
committerSteven Rostedt <rostedt@goodmis.org>2014-12-03 17:10:11 -0500
commit3e6fb8e94329270c70ea00867112a2c6f348207f (patch)
tree2a65d60618b93d667f3bb63dcee1c17b143f91b6
parenteabb8980a96cff42ae70cc6ab143f4003f02c874 (diff)
downloadlinux-3e6fb8e94329270c70ea00867112a2c6f348207f.tar.gz
linux-3e6fb8e94329270c70ea00867112a2c6f348207f.tar.bz2
linux-3e6fb8e94329270c70ea00867112a2c6f348207f.zip
Documentation: describe trace_buf_size parameter more accurately
I'm stuck into panic that too litte free memory is left when I boot with trace_buf_size parameter. After digging into the problem, I found that trace_buf_size is the size of trace buffer on each cpu rather than total size of trace buffer. To prevent victim like me, change description of trace_buf_size parameter more accurately. Link: http://lkml.kernel.org/r/1417570760-10620-1-git-send-email-iamjoonsoo.kim@lge.com Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-rw-r--r--Documentation/kernel-parameters.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 7dbe5ec9d9cd..1d09eb37c562 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -3477,7 +3477,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
are saved.
trace_buf_size=nn[KMG]
- [FTRACE] will set tracing buffer size.
+ [FTRACE] will set tracing buffer size on each cpu.
trace_event=[event-list]
[FTRACE] Set and start specified trace events in order