From: "H. Peter Anvin" <hpa@zytor.com>
To: rostedt@goodmis.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Borislav Petkov <borislav.petkov@amd.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/cpu changes for v2.6.34
Date: Mon, 01 Mar 2010 14:24:58 -0800 [thread overview]
Message-ID: <4B8C3EBA.9050407@zytor.com> (raw)
In-Reply-To: <1267472522.10871.14.camel@gandalf.stny.rr.com>
On 03/01/2010 11:42 AM, Steven Rostedt wrote:
>
> As Frederic has said you can use 'ftrace=function_graph' on the kernel
> command line. It will be initialized in early_initcall (which I believe
> is before CPUs are set up. Then add a tracing_off() after the trouble
> code. You can make the trace buffers bigger with the kernel command
> line:
>
> trace_buf_size=10000000
>
> The above will make the trace buffer 10Meg per CPU. Unlike the
> "buffer_size_kb" file, this number is in bytes, even though it will
> round to the nearest page. (I probably should make this into kb, and
> rename it to trace_buf_size_kb, and deprecate trace_buf_size).
>
Memory sizes specified on the kernel command line should generally be in
units of bytes, but accepting suffixes.
-hpa
next prev parent reply other threads:[~2010-03-01 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 15:09 [GIT PULL] x86/cpu changes for v2.6.34 Ingo Molnar
2010-02-27 17:10 ` Arjan van de Ven
2010-02-27 20:03 ` H. Peter Anvin
2010-02-28 20:09 ` Linus Torvalds
2010-02-28 20:45 ` Linus Torvalds
2010-03-01 8:00 ` Ingo Molnar
2010-03-01 13:17 ` Frederic Weisbecker
2010-03-01 16:47 ` Linus Torvalds
2010-03-01 19:42 ` Steven Rostedt
2010-03-01 22:23 ` Steven Rostedt
2010-03-01 22:24 ` H. Peter Anvin [this message]
2010-03-01 19:29 ` Steven Rostedt
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=4B8C3EBA.9050407@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=borislav.petkov@amd.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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