mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: TAMUKI Shoichi <tamuki@linet.gr.jp>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anton Blanchard <anton@samba.org>, Andy Green <andy@warmcat.com>,
	TAMUKI Shoichi <tamuki@linet.gr.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] panic: keep blinking in spite of long spin timer mode
Date: Sat, 29 May 2010 07:11:06 +0900	[thread overview]
Message-ID: <201005282211.AA00413@tamuki.linet.gr.jp> (raw)
In-Reply-To: <20100528091354.GA16587@basil.fritz.box>

Hello,

On Fri, May 28, 2010 at 11:13:54 +0200, Andi Kleen 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).
> 
> Sorry I didn't understand the problem based on your description.
> 
> What exactly is the problem with the current code under your
> hypervisor?
> 
> New parameters for this are probably not the right answer,
> who would figure out when to set them.

Sorry for my poor explanation.

As Anton Blanchard wrote, who posted "[PATCH] panic: Fix panic_timeout
accuracy when running on a hypervisor", he had had some complaints
about panic_timeout being wildly innacurate on shared processor PowerPC
partitions (a 3 minute panic_timeout taking 30 minutes).

The fact is we loop on mdelay(1) and with a 1ms in 10ms hypervisor
timeslice each of these will take 10ms (i.e. 10x) longer.  To avoid
this, it had been changed to do 1 second mdelays if we don't have a
panic_blink.

The problem is the keyboard LEDs don't blink at all on that situation.

Therefore, I changed to call panic_blink_enter() between every mdelay.
The default time calls to mdelay is 1ms.  If the kernel parameter
panic_longspin is set to true, it will be switched to 240ms and the
maximum speed of blinking will be automatically limited slower due to
the granularity of the blinking time.

It is complicated to change the speed of panic blink that the indi-
vidual drivers do.

This is the reason why the place to control blinking has been moved
from panic_blink() (i.e. gta02_panic_blink() or i8042_panic_blink()
for now) to panic_blink_enter().

Regards,
TAMUKI Shoichi

  reply	other threads:[~2010-05-28 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 21:56 TAMUKI Shoichi
2010-05-28  9:13 ` Andi Kleen
2010-05-28 22:11   ` TAMUKI Shoichi [this message]
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
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=201005282211.AA00413@tamuki.linet.gr.jp \
    --to=tamuki@linet.gr.jp \
    --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 \
    /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

Powered by JetHome