| 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
| ||
|
Message-ID: <4720CD80.5030106@zytor.com> Date: Thu, 25 Oct 2007 10:08:16 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Andi Kleen <ak@...ell.com> CC: "Eric W. Biederman" <ebiederm@...ssion.com>, Thomas Gleixner <tglx@...utronix.de>, "Huang, Ying" <ying.huang@...el.com>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...hat.com>, Chandramouli Narayanan <mouli@...ux.intel.com>, LKML <linux-kernel@...r.kernel.org>, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH 1/3 -v4] x86_64 EFI runtime service support: EFI basic runtime service support Andi Kleen wrote: >> Especially for accessing the real time clock that has a well >> defined hardware interface going through efi an additional >> software emulation layer looks like asking for trouble. > > I agree it's pointless for the hardware clock, but EFI > also offers services to write some data to the CMOS RAM > which could be very useful to save oops data over reboot. > I don't think this can be done safely otherwise > without BIOS cooperation. > The ability to scurry away even a small amount of data without relying on the disk system is highly desirable. Think next-boot type information. -hpa - 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