From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Sunil Naidu" <akula2.shark@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Frederik Deweerdt" <deweerdt@free.fr>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Linux 2.6.21 - something wrong with dmesg.
Date: Fri, 27 Apr 2007 16:39:13 +0100 [thread overview]
Message-ID: <200704271639.13419.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <8355959a0704270731k97da30anf1c010f7ae3dc18c@mail.gmail.com>
On Friday 27 April 2007 15:31:37 Sunil Naidu wrote:
> On 4/26/07, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> > > Don't you need to increase CONFIG_LOG_BUF_SHIFT ?
>
> Yep, I need to. But, have to enable the Kernel Debug (DEBUG_KERNEL) to
> increase the value from default 14 value to 15/16. I feel that this
> might increase the kernel size?
>From a quick grep, DEBUG_KERNEL will only increase the kernel size on PARISC
(arch/parisc/mm/init.c), so setting it won't have any adverse affect on your
kernel size (if you disable all the options under it).
> Ummm, is it possible to move CONFIG_LOG_BUF_SHIFT under the General
> Setup area? (say, down the Kernel .config support - IKCONFIG).
I agree with this. It's also quite interesting to see that one can enable
DEBUG_KERNEL, increase CONFIG_LOG_BUF_SHIFT, and then disable DEBUG_KERNEL,
and the changed value is still used.
I think it should be easier to change this value, as anybody with it set too
low has a useless kernel log buffer and it can make reporting more difficult.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2007-04-27 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 12:14 Sunil Naidu
2007-04-26 13:03 ` Frederik Deweerdt
2007-04-26 14:35 ` Alistair John Strachan
2007-04-27 14:31 ` Sunil Naidu
2007-04-27 15:39 ` Alistair John Strachan [this message]
2007-04-27 15:55 ` Randy Dunlap
2007-04-27 19:53 ` [PATCH] Move LOG_BUF_SHIFT to a more sensible place Alistair John Strachan
2007-04-27 21:37 ` Randy Dunlap
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=200704271639.13419.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=akula2.shark@gmail.com \
--cc=deweerdt@free.fr \
--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
all inboxes | Powered by JetHome®