All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: slow down printk during boot.
Date: Thu, 05 Jul 2007 20:49:03 -0400	[thread overview]
Message-ID: <468D917F.90204@garzik.org> (raw)
In-Reply-To: <20070705211346.GB17030@redhat.com>

Dave Jones wrote:
> This patch from Randy has proven quite useful from time to time,
> and has been in Fedora kernels for a while for that reason.
> I fixed up some checkpatch warnings, and rediffed it a bunch
> of times, Randy did the heavy lifting.
> 
> ---
> 
> This one delays each printk() during boot by a variable time
> (from kernel command line), while system_state == SYSTEM_BOOTING.
> Caveat:  it's not terribly SMP safe or SMP nice.
> Any ideas for improvements (esp. in the SMP area) are appreciated.
> 
> ---
> 
> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Optionally add a boot delay after each kernel printk() call,
> crudely measured in milliseconds, with a maximum delay of
> 10 seconds per printk.
> 
> Enable CONFIG_BOOT_DELAY=y and then add (e.g.):
> "lpj=loops_per_jiffy boot_delay=100"
> to the kernel command line.
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Signed-off-by: Dave Jones <davej@redhat.com>
> 
> ---
> 
>  init/calibrate.c  |    2 +-
>  init/main.c       |   25 +++++++++++++++++++++++++
>  kernel/printk.c   |   33 +++++++++++++++++++++++++++++++++
>  lib/Kconfig.debug |   18 ++++++++++++++++++
>  4 files changed, 77 insertions(+), 1 deletion(-)

hey, that's pretty neat.

I've occasionally hand-hacked something similar, to achieve those effects.

	Jeff




  reply	other threads:[~2007-07-06  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 21:13 slow down printk during boot Dave Jones
2007-07-06  0:49 ` Jeff Garzik [this message]
     [not found] <8DGUc-ER-37@gated-at.bofh.it>
2007-07-06  1:50 ` Bodo Eggert
2007-07-06  1:55   ` 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=468D917F.90204@garzik.org \
    --to=jeff@garzik.org \
    --cc=davej@redhat.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.