From: Andrew Morton <akpm@linux-foundation.org>
To: Anton Blanchard <anton@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] panic: Fix panic_timeout accuracy when running on a hypervisor
Date: Mon, 1 Feb 2010 14:02:45 -0800 [thread overview]
Message-ID: <20100201140245.faeec398.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100201041430.GQ2996@kryten>
On Mon, 1 Feb 2010 15:14:30 +1100
Anton Blanchard <anton@samba.org> wrote:
>
> I've had some complaints about panic_timeout being wildly innacurate on
> shared processor PowerPC partitions (a 3 minute panic_timeout taking 30
> minutes).
>
> The problem is we loop on mdelay(1) and with a 1ms in 10ms hypervisor
> timeslice each of these will take 10ms (ie 10x) longer. I expect other
> platforms with shared processor hypervisors will see the same issue.
>
> This patch keeps the old behaviour if we have a panic_blink (only keyboard
> LEDs right now) and does 1 second mdelays if we don't.
>
> ...
>
> +static void panic_blink_one_second(void)
> +{
> + static long i = 0, end;
I assumed the `static' was a brainfart and removed it?
> + if (panic_blink) {
> + end = i + MSEC_PER_SEC;
> +
> + while (i < end) {
> + i += panic_blink(i);
> + mdelay(1);
> + i++;
> + }
> + } else {
> + /*
> + * When running under a hypervisor a small mdelay may get
> + * rounded up to the hypervisor timeslice. For example, with
> + * a 1ms in 10ms hypervisor timeslice we might inflate a
> + * mdelay(1) loop by 10x.
> + *
> + * If we have nothing to blink, spin on 1 second calls to
> + * mdelay to avoid this.
> + */
> + mdelay(MSEC_PER_SEC);
> + }
> +}
In fact we can simplify it a bit:
--- a/kernel/panic.c~panic-fix-panic_timeout-accuracy-when-running-on-a-hypervisor-fix
+++ a/kernel/panic.c
@@ -42,12 +42,10 @@ EXPORT_SYMBOL(panic_blink);
static void panic_blink_one_second(void)
{
- static long i = 0, end;
-
if (panic_blink) {
- end = i + MSEC_PER_SEC;
+ long i = 0;
- while (i < end) {
+ while (i < MSEC_PER_SEC) {
i += panic_blink(i);
mdelay(1);
i++;
_
Why does it do the mdelay() as well as calling panic_blink()? hm,
because the old code did. I guess it doesn't trust panic_blink().
next prev parent reply other threads:[~2010-02-01 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 4:14 [PATCH] panic: Fix panic_timeout accuracy when running on a hypervisor Anton Blanchard
2010-02-01 22:02 ` Andrew Morton [this message]
2010-02-02 0:50 ` Anton Blanchard
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=20100201140245.faeec398.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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