All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: mingo@elte.hu, eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmemtrace: fix kernel parameter documentation
Date: Tue, 26 May 2009 08:23:46 -0700	[thread overview]
Message-ID: <4A1C0982.1090300@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0905241112190.10296@rocky>

Pekka Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
> 
> The kmemtrace.enable kernel parameter no longer works. To enable
> kmemtrace at
> boot-time, you must pass "ftrace=kmemtrace" instead.

Can someone also list the possible tracers in the ftrace= area, please?

	ftrace=[tracer]
			[ftrace] will set and start the specified tracer
			as early as possible in order to facilitate early
			boot debugging.

Thanks.

> Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
>  Documentation/kernel-parameters.txt |   10 ----------
>  1 files changed, 0 insertions(+), 10 deletions(-)
> 
> diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> index e87bdbf..9243dd8 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -56,7 +56,6 @@ parameter is applicable:
>      ISAPNP    ISA PnP code is enabled.
>      ISDN    Appropriate ISDN support is enabled.
>      JOY    Appropriate joystick support is enabled.
> -    KMEMTRACE kmemtrace is enabled.
>      LIBATA  Libata driver is enabled
>      LP    Printer support is enabled.
>      LOOP    Loopback device support is enabled.
> @@ -1054,15 +1053,6 @@ and is between 256 and 4096 characters. It is
> defined in the file
>              use the HighMem zone if it exists, and the Normal
>              zone if it does not.
> 
> -    kmemtrace.enable=    [KNL,KMEMTRACE] Format: { yes | no }
> -                Controls whether kmemtrace is enabled
> -                at boot-time.
> -
> -    kmemtrace.subbufs=n    [KNL,KMEMTRACE] Overrides the number of
> -            subbufs kmemtrace's relay channel has. Set this
> -            higher than default (KMEMTRACE_N_SUBBUFS in code) if
> -            you experience buffer overruns.
> -
>      kgdboc=        [HW] kgdb over consoles.
>              Requires a tty driver that supports console polling.
>              (only serial suported for now)


-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

  reply	other threads:[~2009-05-26 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24  8:13 [PATCH] kmemtrace: fix kernel parameter documentation Pekka Enberg
2009-05-26 15:23 ` Randy Dunlap [this message]
2009-05-27 22:34 ` [tip:tracing/core] " tip-bot for Pekka Enberg

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=4A1C0982.1090300@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=eduard.munteanu@linux360.ro \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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 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.