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
Subject: Re: [PATCH v3] panic: keep blinking in spite of long spin timer mode
Date: Thu, 17 Jun 2010 15:20:17 -0700 [thread overview]
Message-ID: <20100617152017.1d939db3.akpm@linux-foundation.org> (raw)
In-Reply-To: <201006172136.AA00435@tamuki.linet.gr.jp>
On Fri, 18 Jun 2010 06:36:31 +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 default time to call to mdelay is 1ms. It will be switched to
> longer if the CONFIG_PANIC_LONGSPIN_TIMER kernel configuration option
> is enabled. This feature is helpful when running under a hypervisor.
>
> Signed-off-by: TAMUKI Shoichi <tamuki@linet.gr.jp>
> ---
> Changes since v2.1:
> - get rid of panicblink= kernel parameter
> - introduce new kernel config option CONFIG_PANIC_LONGSPIN_TIMER
>
I still don't get it :(
Why can't we simply do
for (i = 0; ; i++) {
(*panic_blink)(i & 1);
mdelay(250);
touch_nmi_watchdog();
}
on all kernels, regardless of virtualisation, etc?
next prev parent reply other threads:[~2010-06-17 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 21:36 [PATCH v3] panic: keep blinking in spite of long spin timer mode TAMUKI Shoichi
2010-06-17 22:20 ` Andrew Morton [this message]
2010-06-20 22:52 ` 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=20100617152017.1d939db3.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=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