* [PATCH] Documentation: describe trace_buf_size parameter more accurately
@ 2014-12-03 1:39 Joonsoo Kim
2014-12-03 9:06 ` Steven Rostedt
0 siblings, 1 reply; 2+ messages in thread
From: Joonsoo Kim @ 2014-12-03 1:39 UTC (permalink / raw)
To: Steven Rostedt
Cc: Ingo Molnar, Jonathan Corbet, linux-kernel, linux-doc, Joonsoo Kim
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.
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
---
Documentation/kernel-parameters.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 70cfce5..fc77457 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -3546,7 +3546,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
--
1.7.9.5
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: describe trace_buf_size parameter more accurately
2014-12-03 1:39 [PATCH] Documentation: describe trace_buf_size parameter more accurately Joonsoo Kim
@ 2014-12-03 9:06 ` Steven Rostedt
0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2014-12-03 9:06 UTC (permalink / raw)
To: Joonsoo Kim; +Cc: Ingo Molnar, Jonathan Corbet, linux-kernel, linux-doc
On Wed, 3 Dec 2014 10:39:20 +0900
Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
> 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.
Heh, Thanks, I'll apply this.
-- Steve
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> ---
> Documentation/kernel-parameters.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 70cfce5..fc77457 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -3546,7 +3546,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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-12-03 9:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-03 1:39 [PATCH] Documentation: describe trace_buf_size parameter more accurately Joonsoo Kim
2014-12-03 9:06 ` Steven Rostedt
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.