From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Randy Dunlap" <rdunlap@xenotime.net>
Cc: "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 15:45:08 +0800 [thread overview]
Message-ID: <a8e1da0708150045i4b02e0a4u51a10084f1b439da@mail.gmail.com> (raw)
In-Reply-To: <20070811163331.b8ff4a6b.rdunlap@xenotime.net>
>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.
>
> 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?
I386 for me. I tested boot_delay=300 again:
1. From "Uncompressing Linux.. Ok,booting the kernel" to "console
[tty0] enabled"
keep the same screen about 5-6 minutes
2. After that every line will need 20-30 seconds.
My cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) D CPU 2.80GHz
stepping : 7
cpu MHz : 2793.181
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl cid cx16 xtpr
lahf_lm
bogomips : 5591.66
clflush size : 64
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) D CPU 2.80GHz
stepping : 7
cpu MHz : 2793.181
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl cid cx16 xtpr
lahf_lm
bogomips : 5587.46
clflush size : 64
Regards
dave
next prev parent reply other threads:[~2007-08-15 7:45 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
2007-08-15 7:45 ` Dave Young [this message]
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=a8e1da0708150045i4b02e0a4u51a10084f1b439da@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=davej@codemonkey.org.uk \
--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 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®