From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] i386: halt the CPU on serious errors
Date: Tue, 20 Jun 2006 09:50:15 +0200 [thread overview]
Message-ID: <20060620075015.GB3030@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <200606200059_MC3-1-C2E8-8C46@compuserve.com>
Hi,
On Tue, Jun 20, 2006 at 12:55:25AM -0400, Chuck Ebbert wrote:
> Halt the CPU when serious errors are encountered and we
> deliberately go into an infinite loop.
>
> Suggested by Andreas Mohr.
Thanks for the very fast patch, but:
> /* Assume hlt works */
> - halt();
> - for(;;);
> + for (;;)
> + halt();
The comment above seems to hint at this code in arch/i386/kernel/smp.c/
stop_this_cpu() which does proper hlt checks:
if (cpu_data[smp_processor_id()].hlt_works_ok)
for(;;) halt();
for (;;);
So I'm unsure what happens if hlt is not supported properly. Maybe
there's an invalid opcode exception in a loop then.
I think a patch should do the following (or more):
- try to group various CPU emergency stop places together
- comment about trying to avoid overheating, mentioning ACPI
thermal protection specifications and possibly *missing protection*
in non-ACPI systems/modes (APM!)
- if (hlt_works_ok), do hlt loop
- if not, do a cpu_relax() loop (or even: for (;;) 3 times cpu_relax()
for lower activity?)
One thing that may be worth pondering about is whether using cpu_relax()
might actually keep the CPU slightly below the ACPI shutdown temperature
limit and thus do *more* harm with a broken fan. In that case we might
want to check for active ACPI mode and if active do a busy loop instead.
This however may cause temperature to cycle (will a CPU shutdown reactivate
itself after cooling down again?), so a cpu_relax() might still be better.
Andreas Mohr
next prev parent reply other threads:[~2006-06-20 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 4:55 Chuck Ebbert
2006-06-20 5:09 ` Dave Jones
2006-06-20 7:50 ` Andreas Mohr [this message]
2006-06-21 9:20 ` Andi Kleen
2006-06-21 9:26 ` Arjan van de Ven
2006-06-21 9:17 Chuck Ebbert
2006-06-21 9:17 Chuck Ebbert
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=20060620075015.GB3030@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®