linux-kernel - Re: [PATCH 1/3] X86: Revamp reboot behaviour to match Windows more closely

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]

Message-ID: <20101209223201.GA23894@srcf.ucam.org>
Date:	Thu, 9 Dec 2010 22:32:01 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	x86@...nel.org, linux-acpi@...r.kernel.org, lenb@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] X86: Revamp reboot behaviour to match Windows more
	closely

On Thu, Dec 09, 2010 at 02:25:05PM -0800, H. Peter Anvin wrote:
> On 12/09/2010 01:46 PM, Matthew Garrett wrote:
>> Windows reboots by hitting the ACPI reboot vector (if available), trying
>> the keyboard controller, hitting the ACPI reboot vector again and then
>> giving the keyboard controller one last go. Rework our reboot process a
>> little to default to matching this behaviour, although we'll fall through
>> to attempting a triple fault if nothing else works.
>>
>> Signed-off-by: Matthew Garrett<mjg@...hat.com>
>
> When this was discussed before we agreed to use ACPI reboot by default  
> with an ACPI cutoff date; this doesn't have any such cutoff.

Windows doesn't either. Older machines simply won't have the appropriate 
flag set in their FADT.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/