[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141203040620.254a8a02@gandalf.local.home>
Date: Wed, 3 Dec 2014 04:06:20 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Joonsoo Kim <iamjoonsoo.kim@....com>
Cc: Ingo Molnar <mingo@...hat.com>, Jonathan Corbet <corbet@....net>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: describe trace_buf_size parameter more
accurately
On Wed, 3 Dec 2014 10:39:20 +0900
Joonsoo Kim <iamjoonsoo.kim@....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@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists