From: Andrew Morton <akpm@linux-foundation.org>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>
Cc: Ingo Molnar <mingo@elte.hu>, Anton Blanchard <anton@samba.org>,
Andi Kleen <andi@firstfloor.org>, Andy Green <andy@warmcat.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@mail.ru>
Subject: Re: [PATCH v4] panic: keep blinking in spite of long spin timer mode
Date: Tue, 22 Jun 2010 13:16:54 -0700 [thread overview]
Message-ID: <20100622131654.05032c22.akpm@linux-foundation.org> (raw)
In-Reply-To: <201006202252.AA00437@tamuki.linet.gr.jp>
On Mon, 21 Jun 2010 07:52:24 +0900
TAMUKI Shoichi <tamuki@linet.gr.jp> 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 the problem is the keyboard
> LEDs don't blink at all on that situation.
>
> This patch changes to call to panic_blink_enter() between every mdelay
> and keeps blinking in spite of long spin timer mode.
>
> The time to call to mdelay is now 100ms. Even this change will keep
> panic_timeout accuracy enough when running under a hypervisor.
>
Thaks for sticking with it - I think the code's a lot better now. Are
you happy with it?
> ---
> Changes since v3:
> - get rid of CONFIG_PANIC_LONGSPIN_TIMER kernel config option
>
> Documentation/kernel-parameters.txt | 3 -
> arch/arm/mach-s3c2440/mach-gta02.c | 17 ++-----
> drivers/input/serio/i8042.c | 25 ++---------
> include/linux/kernel.h | 2
> kernel/panic.c | 58 +++++++++++---------------
> 5 files changed, 37 insertions(+), 68 deletions(-)
And isn't that a nice sight.
> --- a/drivers/input/serio/i8042.c
> +++ b/drivers/input/serio/i8042.c
Dmitry, I think drivers/input/serio/i8042.c is buggy. It does
panic_blink = NULL;
as the very last thing on module exit. However it surely should do
this at least at the _start_ of i8042_exit() and I suspect it really
should be doing this at the start of i8042_shutdown()?
As things stand, a well-timed panic will end up trying to flash LEDs
via hardware which has been "shut down".
next prev parent reply other threads:[~2010-06-22 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 22:52 TAMUKI Shoichi
2010-06-22 20:16 ` Andrew Morton [this message]
2010-06-22 20:33 ` Dmitry Torokhov
2010-06-23 22:35 ` 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=20100622131654.05032c22.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=andy@warmcat.com \
--cc=anton@samba.org \
--cc=dtor@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--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
all inboxes | Powered by JetHome®