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
| ||
|
Date: Tue, 1 Jun 2010 20:00:50 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: "Justin P. Mattock" <justinmattock@...il.com> Cc: x86@...nel.org, tglx@...utronix.de, linux-kernel@...r.kernel.org Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table. Can you try with this patch? From what I can see of Apple ACPI tables, it should be functionally equivalent but less hate inducing. commit 9c8c25fda1b993a81b1a3a9bc4e9e8b0d7ac4062 Author: Matthew Garrett <mjg@...hat.com> Date: Tue Jun 1 14:40:55 2010 -0400 x86: Default to using ACPI for reboot Running a hacked qemu with a modified seabios image that declares support for reboot via ACPI shows that Windows will use the ACPI reboot vector before falling back to hitting i8042. Change the default reboot method to match this. This looks like it should improve life for Apples, which declare the cf9 reboot method via ACPI, don't have a competent i8042 emulation and currently have a large DMI whitelist. Signed-off-by: Matthew Garrett <mjg@...hat.com> diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index 8e1aac8..0a04c4b 100644 --- a/arch/x86/kernel/reboot.c +++ b/arch/x86/kernel/reboot.c @@ -34,7 +34,7 @@ EXPORT_SYMBOL(pm_power_off); static const struct desc_ptr no_idt = {}; static int reboot_mode; -enum reboot_type reboot_type = BOOT_KBD; +enum reboot_type reboot_type = BOOT_ACPI; int reboot_force; #if defined(CONFIG_X86_32) && defined(CONFIG_SMP) -- 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/
Powered by blists - more mailing lists