From: Ingo Molnar <mingo@elte.hu>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v3] printk: add halt_delay parameter for printk delay in halt phase
Date: Mon, 8 Jun 2009 10:14:39 +0200 [thread overview]
Message-ID: <20090608081439.GB6372@elte.hu> (raw)
In-Reply-To: <a8e1da0906080040k7852f770v1e2aa2ebb0f52369@mail.gmail.com>
* Dave Young <hidave.darkstar@gmail.com> wrote:
> Add a halt_delay module parameter in printk.c used to read the
> printk messages in halt/poweroff/restart phase, delay each printk
> messages by halt_delay milliseconds. It is useful for debugging if
> there's no other way to dump kernel messages that time.
>
> The halt_delay max value is 65535, default value is 0, change it
> by:
>
> echo xxx > /sys/module/printk/parameters/halt_delay
>
> Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
> ---
> Documentation/kernel-parameters.txt | 5 +++++
> kernel/printk.c | 17 +++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> --- linux-2.6.orig/kernel/printk.c 2009-06-08 13:55:35.000000000 +0800
> +++ linux-2.6/kernel/printk.c 2009-06-08 13:56:23.000000000 +0800
> @@ -250,6 +250,22 @@ static inline void boot_delay_msec(void)
> }
> #endif
>
> +/* msecs delay after each halt/poweroff/restart phase printk,
> + unsigned short is enough for delay in milliseconds */
> +static unsigned short halt_delay;
> +
> +static inline void halt_delay_msec(void)
> +{
> + if (unlikely(halt_delay == 0 || !(system_state == SYSTEM_HALT
> + || system_state == SYSTEM_POWER_OFF
> + || system_state == SYSTEM_RESTART)))
> + return;
This is a tiny bit ugly (and goes into the vprintf path) but i can
see no other way either - a system_state > SYSTEM_RUNNING check
would needlessly include the suspend-to-disk state (which we dont
want to include here).
In theory we could turn system_state into a bitmask and have a
print_delay_mask check instead of these flags ... but that is a far
wider change and i'm not sure it's a net step forwards.
I've applied your patch to tip:core/printk with small edits to the
changelog - Linus & Andrew is Cc:ed, should they have any
objections.
Ingo
next prev parent reply other threads:[~2009-06-08 8:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 7:40 Dave Young
2009-06-08 8:12 ` [tip:core/printk] printk: Add halt_delay=<msecs> " tip-bot for Dave Young
2009-06-08 8:14 ` Ingo Molnar [this message]
2009-06-08 8:28 ` [PATCH v3] printk: add halt_delay " Andrew Morton
2009-06-08 8:42 ` Dave Young
2009-06-08 8:48 ` Ingo Molnar
2009-06-08 16:26 ` Andrew Morton
2009-06-08 17:15 ` Ingo Molnar
2009-06-08 21:39 ` Andrew Morton
2009-06-08 22:02 ` Ingo Molnar
2009-06-08 22:07 ` Andrew Morton
2009-06-08 22:12 ` Ingo Molnar
2009-06-09 1:01 ` Dave Young
2009-06-09 1:35 ` Dave Young
2009-06-09 2:33 ` Andrew Morton
2009-06-09 0:48 ` Dave Young
2009-06-08 8:37 ` Dave Young
2009-06-08 8:46 ` Ingo Molnar
2009-06-08 8:56 ` Dave Young
2009-06-08 8:58 ` Ingo Molnar
2009-06-08 9:00 ` Dave Young
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=20090608081439.GB6372@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®