From: Steven Rostedt <rostedt@goodmis.org>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: describe trace_buf_size parameter more accurately
Date: Wed, 3 Dec 2014 04:06:20 -0500 [thread overview]
Message-ID: <20141203040620.254a8a02@gandalf.local.home> (raw)
In-Reply-To: <1417570760-10620-1-git-send-email-iamjoonsoo.kim@lge.com>
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
prev parent reply other threads:[~2014-12-03 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 1:39 Joonsoo Kim
2014-12-03 9:06 ` Steven Rostedt [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=20141203040620.254a8a02@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®