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]
Date:	Wed, 25 Jun 2008 18:11:01 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Paul Jackson <pj@....com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Jack Steiner <steiner@....com>, Mike Travis <travis@....com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	"Huang, Ying" <ying.huang@...el.com>,
	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 2/2] x86 boot: only pick up additional EFI memmap if
	add_efi_memmap flag


* Paul Jackson <pj@....com> wrote:

> From: Paul Jackson <pj@....com>
> 
> Applies on top of the previous patch:
>   x86 boot: add code to add BIOS provided EFI memory entries to kernel
> 
> Instead of always adding EFI memory map entries (if present) to the 
> memory map after initially finding either E820 BIOS memory map entries 
> and/or kernel command line memmap entries, -instead- only add such 
> additional EFI memory map entries if the kernel boot option:
> 
>     add_efi_memmap
> 
> is specified.
> 
> Requiring this 'add_efi_memmap' option is backward compatible with 
> kernels that didn't load such additional EFI memory map entries in the 
> first place, and it doesn't override a configuration that tries to 
> replace all E820 or EFI BIOS memory map entries with ones given 
> entirely on the kernel command line.

applied to tip/x86/setup-memory - thanks Paul.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ