linux-kernel - Re: [PATCH] Limit E820 map and /proc/iomem for mem parameter on x86-64

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] [day] [month] [year] [list]

Message-ID: <86802c440806121843k221aaed9wc49b3a6a1ea966af@mail.gmail.com>
Date:	Thu, 12 Jun 2008 18:43:09 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	kexec@...ts.infradead.org, vgoyal@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Limit E820 map and /proc/iomem for mem parameter on x86-64

On Tue, Jun 10, 2008 at 2:53 PM, Bernhard Walle <bwalle@...e.de> wrote:
> This patch tries to unify the behaviour of i386 and x86-64 when parsing
> the memory (mem/memmap) parameter of the kernel command line:
>
> On i386, the view was limited (i.e. the actual view was presented).
> On x86-64, the view was full (i.e. the BIOS view was presented).
>
> This patch moves the limit_regions() function and the print_memory_map()
> function to a new file e820.c, shared between the two x86 flavours. Then
> it adds calls to limit_regions() in 64 bit code.
>
> I gave the patch a bit testing. However, it's not for merging, it's just
> to get early feedback to see if that goes into the right direction.

can you check tip/master about that e820 merge?

http://people.redhat.com/mingo/tip.git/readme.txt

it made 32bit using e820_register_active_region...and limit_region in
32bit is remove.

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