public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: TAMUKI Shoichi <tamuki@linet.gr.jp>, Ingo Molnar <mingo@elte.hu>,
	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: Thu, 10 Jun 2010 12:30:33 +1000	[thread overview]
Message-ID: <20100610023033.GN28295@kryten> (raw)
In-Reply-To: <20100609151552.d1a8ca8d.akpm@linux-foundation.org>

 
Hi,

> 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?

I agree. The panic_blink() interface is quite painful and I have no idea
why someone would want to configure the blink frequency of their keyboard
LED when panicing. Maybe they want to match it to the beat of their techno
music.

Since the keyboard LED default is a transition every 0.5s, why don't we just
remove i8042.panicblink and change all users (all 2 of them) to expect a 2 HZ
call rate? The hypervisor case should be fine with 0.5s mdelays, so we end up
removing that special case.

I would have said 1 HZ, but it seems like the default was chosen to be
different to kdb:

	/*
         * We expect frequency to be about 1/2s. KDB uses about 1s.
         * Make sure they are different.
	 */

No idea if that comment is still valid.

Anton

  reply	other threads:[~2010-06-10  2:34 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
2010-06-10  2:30       ` Anton Blanchard [this message]
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=20100610023033.GN28295@kryten \
    --to=anton@samba.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=andy@warmcat.com \
    --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