From: TAMUKI Shoichi <tamuki@linet.gr.jp>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Anton Blanchard <anton@samba.org>,
Andi Kleen <andi@firstfloor.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: Fri, 04 Jun 2010 06:49:22 +0900 [thread overview]
Message-ID: <201006032149.AA00423@tamuki.linet.gr.jp> (raw)
In-Reply-To: <20100602113446.060847eb.akpm@linux-foundation.org>
Hello,
On Wed, 2 Jun 2010 11:34:46 -0700 Andrew Morton wrote:
> 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);
> }
>
> ?
Your proposal is rather simpler than the current patch, indeed.
I carefully went into the proposal:
- With this implementation, the time to call to mdelay() needs to be
variable in order to change the speed of blinking.
- It is not desirable that the period to call to touch_nmi_watchdog()
or touch_softlockup_watchdog() depends on the speed of blinking.
- We would like to leave the room that can be implemented as not only
a simple blinking but also as a so-called morse blinking which con-
tains useful information when kernel panics.
That being the reason, I will keep the current implementation that the
time to call mdelay() is a short constant (as 1ms usually).
BTW, there are some sanity checks or something in panic_blink_enter(),
which need not exist there, so I have moved them to appropriate place.
Thank you for the suggestion. See you next PATCH v2.
Regards,
TAMUKI Shoichi
prev parent reply other threads:[~2010-06-03 21:50 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
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 [this message]
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=201006032149.AA00423@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