public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v2] panic: keep blinking in spite of long spin timer mode
Date: Wed, 9 Jun 2010 15:15:52 -0700	[thread overview]
Message-ID: <20100609151552.d1a8ca8d.akpm@linux-foundation.org> (raw)
In-Reply-To: <201006061319.AA01345@tamuki.linet.gr.jp>

On Sun, 06 Jun 2010 22:19:18 +0900
TAMUKI Shoichi <tamuki@linet.gr.jp> wrote:

> Hello,
> 
> Thank you for the review.
> 
> On Thu, 3 Jun 2010 15:30:16 -0700 Andrew Morton wrote:
> 
> > > +	panicblink=	[KNL] The speed of panic blink (default is 12 wpm)
> > > +			The period of panic blink can be computed by the
> > > +			formula T = 7200 / W, where T is the period in milli-
> > > +			seconds, W is the speed in wpm (words per minute).
> > > +			Should be 5 or less when running under a hypervisor
> > 
> > Nobody will know what "wpm" means.  What is a "word" in this context?
> > Unclear.
> > 
> > How about "bpm": "blinks per minute".  That's nice and direct.
> 
> The current explanation of panicblink= still makes no sense, indeed.
> 
> "bpm" seems to be nice and direct, but the range at a practicable
> blinking speed will be 8.33 to 833 bpm.  That is too wide and the step
> size is too small for the speed of panic blink.  That will be hard to
> deal with.
> 
> OTOH, the range at a practicable blinking speed in "wpm" fits in 1 to
> 100.  I think that will sit well with us.
> 
> Now, I need to explain what "wpm" means and what a "word" in the con-
> text is:
> 
> The speed of morse code is measured in wpm, which defines the speed of
> morse transmission as the timing needed to send the word "PARIS" a
> given number of times per minute.
> 
> The time for one (minimum) unit can be computed by the formula T =
> 1200 / W, where T is the unit time in milliseconds, W is the speed in
> wpm.  The panic blink here is assumed as a word of infinite length to
> which "T" continues (i.e. "TTTTTTTT...").  The letter "T" represents
> three units long and the short gap (between letters) also represents
> three units long.  The period of panic blink thus can be computed by
> the formula T = 7200 / W.

Morse code?  Kidding?

Sorry, no.  Nobody who uses this feature will know what what
"words per minute" means.  It's nutty!

Please remind me why we're making this configurable at all.  Can't we
just hardwire the thing to 1Hz or something?  Add an
im_using_a_hypervisor boot option or something, if necessary?


  reply	other threads:[~2010-06-09 22:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 22:01 [PATCH v2] panic: keep blinking in spite of long spin timer mode TAMUKI Shoichi
2010-06-03 22:30 ` Andrew Morton
2010-06-06 13:19   ` TAMUKI Shoichi
2010-06-09 22:15     ` Andrew Morton [this message]
2010-06-10  2:30       ` Anton Blanchard
2010-06-10 22:31         ` TAMUKI Shoichi
2010-06-10 22:31       ` TAMUKI Shoichi
2010-06-14 21:14         ` Andrew Morton
2010-06-15 22:25           ` TAMUKI Shoichi
2010-06-06 13:33   ` [PATCH v2.1] " 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=20100609151552.d1a8ca8d.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