From: Willy Tarreau <w@1wt.eu>
To: Andi Kleen <ak@suse.de>
Cc: pageexec@freemail.hu, davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] exception processing in early boot
Date: Wed, 30 Aug 2006 22:03:54 +0200 [thread overview]
Message-ID: <20060830200354.GA496@1wt.eu> (raw)
In-Reply-To: <200608302136.54624.ak@suse.de>
On Wed, Aug 30, 2006 at 09:36:54PM +0200, Andi Kleen wrote:
>
> > Andi, if you remove the HLT here, some CPUs will spin at full speed. This
> > is nasty during boot because some of them might not have enabled their
> > fans yet for instance
>
> That would be a severe bug in the platform. Basically always the fans are managed
> by SMM code.
It was just an example. Other examples include virtual machines never
stopping because they will see the guest is working and not halted.
Anyway, the "hlt;jmp $" is already used in boot/setup.S, and the
HLT bug you have pointed is, as explained by Richard, a problem
preventing some CPUs from WAKING up from HLT. It causes a problem
when HLT is used in the idle loop. Users who have this problem must
pass the "no-hlt" command line option, otherwise their CPU will
halt during the idle loop (which is the effect we're looking for),
and those without the bug (those who don't have to pass "no-hlt")
will also have the HLT working.
So, to conclude, with or without the bug, "hlt;jmp $" will halt the
CPU as we expect it to. Therefore, I'd like you to restore it in
the patch.
Thanks,
Willy
next prev parent reply other threads:[~2006-08-30 20:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 6:39 [PATCH][RFC] exception processing in early boot Willy Tarreau
2006-08-30 9:51 ` Andi Kleen
2006-08-30 12:18 ` Willy Tarreau
2006-08-30 12:59 ` Andi Kleen
2006-08-30 13:16 ` Willy Tarreau
[not found] ` <20060830100015.6b967c32.seanlkml@sympatico.ca>
2006-08-30 13:46 ` Willy Tarreau
2006-08-30 14:00 ` Sean
[not found] ` <44F5D81A.9650.5BE48F99@pageexec.freemail.hu>
2006-08-30 16:30 ` Andi Kleen
2006-08-30 16:59 ` linux-os (Dick Johnson)
2006-08-30 17:02 ` Andi Kleen
2006-08-30 17:15 ` linux-os (Dick Johnson)
[not found] ` <44F5E818.20898.5C230A79@pageexec.freemail.hu>
2006-08-30 17:52 ` Andi Kleen
[not found] ` <44F5F348.1251.5C4EBCCB@pageexec.freemail.hu>
2006-08-30 18:26 ` Andi Kleen
2006-08-30 19:01 ` Willy Tarreau
2006-08-30 19:36 ` Andi Kleen
2006-08-30 20:03 ` Willy Tarreau [this message]
2006-08-30 20:06 ` Andi Kleen
2006-08-30 20:40 ` Willy Tarreau
2006-08-30 21:31 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 2:05 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=20060830200354.GA496@1wt.eu \
--to=w@1wt.eu \
--cc=ak@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.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