linux-kernel - Re: Introduce userspace interface for Firmware-provided memory map

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: <485C149E.1000807@kernel.org>
Date:	Fri, 20 Jun 2008 13:35:42 -0700
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	Bernhard Walle <bwalle@...e.de>, kexec@...ts.infradead.org,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: Introduce userspace interface for Firmware-provided memory map

Vivek Goyal wrote:
> On Fri, Jun 20, 2008 at 05:56:57PM +0200, Bernhard Walle wrote:
>> This patch (as request for comments) introduces a new userspace interface
>> /proc/firmware_mem that provides the unfiltered view of the BIOS on
>> memory configuration. That's usable for two reasons:
> 
> How about /proc/firmware_memmap. This is little longish but probably more
> clear in intent.

Perhaps even /proc/firmware/memmap (or /sys/firmware/memmap/...).  I 
realize introducing a new directory is annoying, but it's a namespace 
that is likely to have other users.

	-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/