All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	Dave Jones <davej@codemonkey.org.uk>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: two questions about the boot_delay
Date: Wed, 15 Aug 2007 11:19:33 -0400	[thread overview]
Message-ID: <20070815151933.GA13881@redhat.com> (raw)
In-Reply-To: <a8e1da0708150045i4b02e0a4u51a10084f1b439da@mail.gmail.com>

On Wed, Aug 15, 2007 at 03:45:08PM +0800, Dave Young wrote:
 > >On 8/12/07, Randy Dunlap <rdunlap@xenotime.net> wrote:
 > > On Wed, 8 Aug 2007 07:39:33 +0000 Dave Young wrote:
 > >
 > > > Hi,
 > > > I have tried the "slow down printk" , and I have two questions.
 > > >
 > > > 1. why it depends the DEBUG_KERNEL? Sometimes we only need boot_delay
 > > > to see the printk infomations.  How about set it as a standalone
 > > > config option?
 > >
 > > Is depending on DEBUG_KERNEL a problem?  If so, why?
 > 
 > IMHO, the DEBUG_KERNEL will build a big kernel and the building time
 > is long, so if the we only want to look at the boot messages at panic
 > point, the DEBUG_KERNEL is not needed.
 
Only if you enable other debug options too. (Yes, some default to on,
perhaps they shouldn't).

DEBUG_KERNEL itself shouldn't make any difference to the generated
code at all.

	Dave

-- 
http://www.codemonkey.org.uk

      reply	other threads:[~2007-08-15 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  7:39 two questions about the boot_delay Dave Young
2007-08-11 23:33 ` Randy Dunlap
2007-08-15  7:45   ` Dave Young
2007-08-15 15:19     ` Dave Jones [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=20070815151933.GA13881@redhat.com \
    --to=davej@redhat.com \
    --cc=davej@codemonkey.org.uk \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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.