linux-kernel - Re: [PATCH 1/2] Add /sys/firmware/memmap

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: <1214592664.12598.30.camel@nimitz>
Date:	Fri, 27 Jun 2008 11:51:04 -0700
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	Bernhard Walle <bwalle@...e.de>
Cc:	x86@...nel.org, gregkh@...e.de, kexec@...ts.infradead.org,
	yhlu.kernel@...il.com, vgoyal@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Add /sys/firmware/memmap

On Fri, 2008-06-27 at 13:12 +0200, Bernhard Walle wrote:
> 
> This patch adds /sys/firmware/memmap interface that represents the
> BIOS
> (or Firmware) provided memory map. The tree looks like:
> 
>     /sys/firmware/memmap/0/start   (hex number)
>                            end     (hex number)
>                            type    (string)
>     ...                 /1/start
>                            end
>                            type

Could we give this a slightly different name?  We have various 'mem_map'
variables in the kernel, and this confused me on first glance. 

Could we just spell out 'memory_map'?

-- Dave

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