From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: CaT <cat@zip.com.au>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use correct x86 reboot vector
Date: 11 May 2003 13:04:59 -0600 [thread overview]
Message-ID: <m11xz5719g.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1052673863.29921.17.camel@dhcp22.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sul, 2003-05-11 at 19:01, Eric W. Biederman wrote:
> > > At least some SMP boxes freak if you do a poweroff request on CPU != 0
> >
> > As per the MP spec. The system should reboot on the bootstrap cpu.
> > smp_processor_id() == 0 on x86. apicid??
>
> APM now makes its calls on CPU#0 which was the trigger for these
> problems
I have a couple of issues with the current state of affairs.
1) We should always do this to be safe.
2) Reboot has this issue as well.
3) The way APM does it overrides the kernel command line option,
and apm_power_off forces the cpu twice.
4) We have this implemented in 3 different ways in 3 different places.
5) machine_reboot needs this to do this in interrupt context for
Sys-req-B and certain cases of panic and that is not currently handled.
On a related note do you know why machine_halt and machine_power_off return?
After shutting everything down that seems very much like the wrong thing
to do.
Eric
next prev parent reply other threads:[~2003-05-11 18:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 2:56 [PATCH] Use correct x86 reboot vector Andi Kleen
2003-05-10 3:35 ` CaT
2003-05-10 3:58 ` H. Peter Anvin
2003-05-10 14:49 ` Alan Cox
2003-05-10 16:17 ` Jamie Lokier
2003-05-10 18:47 ` Jos Hulzink
2003-05-11 18:01 ` Eric W. Biederman
2003-05-11 17:24 ` Alan Cox
2003-05-11 19:04 ` Eric W. Biederman [this message]
2003-05-12 5:48 ` [PATCH] always shutdown on the bootstrap processor Eric W. Biederman
2003-05-10 16:15 ` [PATCH] Use correct x86 reboot vector Jamie Lokier
2003-05-10 17:09 ` Randy.Dunlap
2003-05-10 19:41 ` Jos Hulzink
2003-05-10 18:10 ` Jamie Lokier
2003-05-10 20:55 ` Jos Hulzink
2003-05-11 3:50 ` Linus Torvalds
2003-05-11 9:37 ` Jos Hulzink
2003-05-11 14:01 ` Jamie Lokier
2003-05-11 17:38 ` Davide Libenzi
2003-05-11 17:56 ` Eric W. Biederman
2003-05-11 18:23 ` Davide Libenzi
2003-05-11 19:12 ` Eric W. Biederman
2003-05-12 15:36 ` Maciej W. Rozycki
2003-05-13 6:35 ` H. Peter Anvin
2003-05-11 18:38 ` Linus Torvalds
2003-05-11 19:00 ` Matt Mackall
2003-05-11 19:16 ` Eric W. Biederman
2003-05-12 1:07 ` H. Peter Anvin
2003-05-11 19:10 ` Eric W. Biederman
2003-05-11 18:43 ` Christer Weinigel
2003-05-11 20:22 ` wingel
2003-05-11 20:26 ` Davide Libenzi
2003-05-11 17:54 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 12:49 Chuck Ebbert
2003-05-13 18:45 ` H. Peter Anvin
2003-05-13 19:04 ` Richard B. Johnson
2003-05-13 19:27 ` H. Peter Anvin
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=m11xz5719g.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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