From: Avi Kivity <avi@qumranet.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@suse.cz>,
Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] x86: default to reboot via ACPI
Date: Tue, 26 Aug 2008 16:33:37 +0300 [thread overview]
Message-ID: <48B40631.5090007@qumranet.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0808261406330.28361@cliff.in.clinika.pl>
Maciej W. Rozycki wrote:
> On Tue, 26 Aug 2008, Avi Kivity wrote:
>
>
>> Most machines are recent machines.
>>
>
> This is a bold statement I would say. Any numbers to back it up?
>
>
Only common sense. Non-recent machines are barely usable these days.
Sure they work well as a firewall or server-in-a-closet, but if you run
a desktop or a server that actually does useful work, you're running a
relatively recent machine.
>> If a machine has acpi, and the reset register is wired to the launch
>> controller, then perhaps this change is unsafe. Don't issue sysrq-b on
>> such machines.
>>
>
> If a machine has ACPI and it is broken randomly, then the results can be
> arbitrary. Hopefully not destructively. If even such a simple thing as
> wiring the reset line so that it functions correctly can be got wrong,
> more so can be more complex matters.
>
If we find that the reset was wired to the launch controller after all,
we can back out the change (after we re-evolve technology and Linux;
after all we are doomed to keep reinventing it, aren't we?).
> Failing a better alternative, I suppose the change has to go in though.
>
Let's see what breaks, if any. I understand the disgust people feel
when ACPI is mentioned, but we can't ignore reality.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-26 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 10:11 [PATCH] x86: default to reboot via ACPI Avi Kivity
2008-08-25 10:32 ` Ingo Molnar
2008-08-26 9:50 ` Pavel Machek
2008-08-26 10:05 ` Avi Kivity
2008-08-26 10:33 ` Alan Cox
2008-08-26 12:14 ` Avi Kivity
2008-08-26 12:31 ` Andi Kleen
2008-08-26 13:24 ` Maciej W. Rozycki
2008-08-26 13:33 ` Avi Kivity [this message]
2008-08-26 14:12 ` Pavel Machek
2008-08-26 14:50 ` Maciej W. Rozycki
2008-08-26 14:24 ` Maciej W. Rozycki
2008-08-26 16:10 ` Alan Cox
2008-08-26 16:16 ` Andi Kleen
2008-08-27 9:18 ` Pavel Machek
2008-08-27 10:51 ` Avi Kivity
2008-08-27 13:13 ` Pavel Machek
2008-08-26 11:03 ` Frans Meulenbroeks
2008-08-26 10:52 ` Alan Cox
2008-08-26 11:07 ` Ingo Molnar
2008-08-26 10:36 ` Ingo Molnar
2008-08-26 11:26 ` Andi Kleen
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=48B40631.5090007@qumranet.com \
--to=avi@qumranet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
/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