linux-kernel - Re: [PATCH] x86: default to reboot via ACPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Aug 2008 15:14:33 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Pavel Machek <pavel@...e.cz>, Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] x86: default to reboot via ACPI

Alan Cox wrote:
>> It seems excessive.  Most machines will hardly run without acpi.
>>     
>
> *Recent* machines.
>   

Most machines are recent machines.

If a machine doesn't have acpi, this change is safe.

If a machine has acpi, but doesn't have the reset register set in the 
FADT, this change is safe.

If a machine has acpi, and the reset register is set incorrectly, this 
change is safe.

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.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/