mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: "Dave Young" <hidave.darkstar@gmail.com>
Cc: "Dave Jones" <davej@codemonkey.org.uk>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: two questions about the boot_delay
Date: Sat, 11 Aug 2007 16:33:31 -0700	[thread overview]
Message-ID: <20070811163331.b8ff4a6b.rdunlap@xenotime.net> (raw)
In-Reply-To: <a8e1da0708080039w1deed062hf5920e1257eb1cbb@mail.gmail.com>

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?

It sure seems like a kernel debug option to me, although
I have no strong preference pro or con on this.

> 2. In My system if I boot with boot_delay=200 the early part of
> booting will be very slow, eapecially at the very beginning (after the
> compressing  and start kernel, it nearly stop here many minutes).
> 
> And I wonder if we can simply use mdelay in the boot_delay_msec(). I
> tested the mdelay , and the result is more accurate.

I wasn't convinced that loops_per_jiffy was always set for all
architectures that early during boot.  Did you audit and verify that
it is set early enough to use during boot_delay_msec()?
and if so, for all architectures?
What architectures did you test this on?


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

  reply	other threads:[~2007-08-11 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  7:39 Dave Young
2007-08-11 23:33 ` Randy Dunlap [this message]
2007-08-15  7:45   ` Dave Young
2007-08-15 15:19     ` Dave Jones

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=20070811163331.b8ff4a6b.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=davej@codemonkey.org.uk \
    --cc=hidave.darkstar@gmail.com \
    --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®