| 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: <20110719132531.GH8006@one.firstfloor.org> Date: Tue, 19 Jul 2011 15:25:31 +0200 From: Andi Kleen <andi@...stfloor.org> To: Prarit Bhargava <prarit@...hat.com> Cc: linux-kernel@...r.kernel.org, Alan Cox <alan@...rguk.ukuu.org.uk>, Andi Kleen <andi@...stfloor.org> Subject: Re: [PATCH 01/34] System Firmware Interface Playing the devils advocate here, but this is really unclear... > There is some additional information I'd like to throw out here as > well. SMBIOS also provides information on the system state after the > BIOS/EFI is finished and before the kernel has been booted. This has > been *invaluable* to me when diagnosing some wonky hardware from OEMs. Hmm this is for SMBIOS tables that changes at runtime? Why exactly is the kernel booting a good point to dump that? Normally the kernel afaik doesn't change SMBIOS as far as I know. There may be some hotplug events that change it, but they have no particular relation to kernel boot. > I want to expand the SMBIOS layer to dump that information out when I What information exactly? And dumping = print to system log? > tl;dr: There are some other useful bits of SMBIOS we could take > advantage of but the current "dmi" layer is difficult to work with. Like what? -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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