From: Randy Dunlap <randy.dunlap@oracle.com>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Anton Blanchard <anton@samba.org>,
Andi Kleen <andi@firstfloor.org>, Andy Green <andy@warmcat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] panic: keep blinking in spite of long spin timer mode
Date: Fri, 28 May 2010 15:22:41 -0700 [thread overview]
Message-ID: <20100528152241.4f5db28f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201005272156.AA00412@tamuki.linet.gr.jp>
On Fri, 28 May 2010 06:56:45 +0900 TAMUKI Shoichi wrote:
> To keep panic_timeout accuracy when running under a hypervisor, the
> current implementation only spins on long time (1 second) calls to
> mdelay. That brings a good effect, but we must give up blinking even
> if we have a panic_blink.
>
> This patch keeps blinking in spite of long spin timer mode.
>
> We now have new kernel parameter (panic_longspin) to enable long spin
> timer mode when kernel panics. This is to be used when running under
> a hypervisor (default is disable).
>
> Signed-off-by: TAMUKI Shoichi <tamuki@linet.gr.jp>
> ---
> Documentation/kernel-parameters.txt | 7 +-
> arch/arm/mach-s3c2440/mach-gta02.c | 17 +----
> drivers/input/serio/i8042.c | 25 +-------
> include/linux/kernel.h | 2
> kernel/panic.c | 81 +++++++++++++++++---------
> 5 files changed, 70 insertions(+), 62 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index fc89cac..7709450 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -918,9 +918,6 @@ and is between 256 and 4096 characters. It is defined in the file
> controller
> i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX
> controllers
> - i8042.panicblink=
> - [HW] Frequency with which keyboard LEDs should blink
> - when kernel panics (default is 0.5 sec)
> i8042.reset [HW] Reset the controller during init and cleanup
> i8042.unlock [HW] Unlock (ignore) the keylock
>
> @@ -1870,6 +1867,10 @@ and is between 256 and 4096 characters. It is defined in the file
>
> panic= [KNL] Kernel behaviour on panic
> Format: <timeout>
> + panic_longspin [KNL] Enable long spin timer mode when kernel panics.
> + This is to be used when running under a hyper-
> + visor (default is disable)
> + panicblink= [KNL] The speed of panic blink (default is 12 wpm)
What is "wpm"? In typing, it's words per minute.
Is it "winks per minute" here? If not, what?
> parkbd.port= [HW] Parallel port number the keyboard adapter is
> connected to, default is 0.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-28 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 21:56 [PATCH] panic: keep blinking in spite of long spin timer mode TAMUKI Shoichi
2010-05-28 9:13 ` Andi Kleen
2010-05-28 22:11 ` TAMUKI Shoichi
2010-05-30 6:55 ` Andi Kleen
2010-06-02 21:57 ` TAMUKI Shoichi
2010-05-28 22:22 ` Randy Dunlap [this message]
2010-05-30 21:58 ` TAMUKI Shoichi
2010-06-02 18:34 ` Andrew Morton
2010-06-03 21:49 ` TAMUKI Shoichi
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=20100528152241.4f5db28f.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=andy@warmcat.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tamuki@linet.gr.jp \
/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;
as well as URLs for NNTP newsgroup(s).