public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: dedekind@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
Date: Fri, 2 Mar 2007 09:11:13 -0800	[thread overview]
Message-ID: <20070302091113.1920ca0f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1172842068.17031.55.camel@sauron>

On Fri, 02 Mar 2007 15:27:48 +0200 Artem Bityutskiy wrote:

> From: Artem Bityutskiy <artem.bityutskiy@nokia.com>
> Subject: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
> 
> This patch makes the upper kernel ring buffer size limit larger. It
> is often very handy to have huge ring-buffer for debugging purposes,
> when the subsystem which is being debugged produces large amount of
> useful output.
> 
> Index: ubi-2.6.git/lib/Kconfig.debug
> ===================================================================
> --- ubi-2.6.git.orig/lib/Kconfig.debug
> +++ ubi-2.6.git/lib/Kconfig.debug
> @@ -79,7 +79,7 @@ config DEBUG_KERNEL
>  
>  config LOG_BUF_SHIFT
>  	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
> -	range 12 21
> +	range 12 26
>  	default 17 if S390 || LOCKDEP
>  	default 16 if X86_NUMAQ || IA64
>  	default 15 if SMP

That's simple enough, but you could also just add
	log_buf_len=huge_number
or
	log_buf_len=500M
or
	log_buf_len=1G
(for megabytes or gigabytes) to the kernel boot command line.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-03-02 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 13:27 [RFC] [PATCH] Kconfig: enlarge printk buffer size limit Artem Bityutskiy
2007-03-02 17:11 ` Randy Dunlap [this message]
2007-03-07 11:33   ` Artem Bityutskiy

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=20070302091113.1920ca0f.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=dedekind@infradead.org \
    --cc=linux-kernel@vger.kernel.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