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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] panic: keep blinking in spite of long spin timer mode
Date: Wed, 2 Jun 2010 11:34:46 -0700 [thread overview]
Message-ID: <20100602113446.060847eb.akpm@linux-foundation.org> (raw)
In-Reply-To: <201005272156.AA00412@tamuki.linet.gr.jp>
On Fri, 28 May 2010 06:56:45 +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 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).
The whole panic-blink setup seems rather poorly thought out.
Would it not be better if a call to (*panic_blink)() were to simply set
the state of the LED and then return? So callers can do
int state = 0;
for ( ; ; ) {
(*panic_blink)(state);
state ^= 1;
mdelay(MSEC_PER_SEC);
}
?
next prev parent reply other threads:[~2010-06-02 18:40 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
2010-05-30 21:58 ` TAMUKI Shoichi
2010-06-02 18:34 ` Andrew Morton [this message]
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=20100602113446.060847eb.akpm@linux-foundation.org \
--to=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).