From: Dave Young <hidave.darkstar@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
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 v2] printk: add halt_delay parameter for printk delay in halt phase
Date: Mon, 8 Jun 2009 15:29:30 +0800 [thread overview]
Message-ID: <a8e1da0906080029n28699e6ctea4a2cf452f7459@mail.gmail.com> (raw)
In-Reply-To: <20090607143221.GE21340@elte.hu>
On Sun, Jun 7, 2009 at 10:32 PM, Ingo Molnar<mingo@elte.hu> wrote:
>
> * 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>
>> ---
>> kernel/printk.c | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> --- linux-2.6.orig/kernel/printk.c 2009-06-03 10:16:55.000000000 +0800
>> +++ linux-2.6/kernel/printk.c 2009-06-03 10:32:43.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;
>> +
>> + mdelay(halt_delay);
>> +}
>> +
>> +module_param(halt_delay, ushort, S_IRUGO | S_IWUSR);
>> +
>> /*
>> * Commands to do_syslog:
>> *
>> @@ -649,6 +665,7 @@ asmlinkage int vprintk(const char *fmt,
>> char *p;
>>
>> boot_delay_msec();
>> + halt_delay_msec();
>>
>> preempt_disable();
>> /* This stops the holder of console_sem just where we want him */
>
> Looks nice now - but please also add a description to
> Documentation/kernel-parameters.txt.
Oops, will add in v3
>
> Thanks,
>
> Ingo
>
--
Regards
dave
prev parent reply other threads:[~2009-06-08 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 3:09 Dave Young
2009-06-07 14:32 ` Ingo Molnar
2009-06-08 7:29 ` Dave Young [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=a8e1da0906080029n28699e6ctea4a2cf452f7459@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®