linux-kernel - Re: [PATCH 18/19] x86, mm: Let "memmap=" take more entries one time

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: <CAE9FiQWajHEY=6xy3abxbCFv3Bo-Gp0KuqPZOGzOLBhaObaG9Q@mail.gmail.com>
Date:	Mon, 22 Oct 2012 12:26:56 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, Jacob Shin <jacob.shin@....com>,
	Tejun Heo <tj@...nel.org>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 18/19] x86, mm: Let "memmap=" take more entries one time

On Mon, Oct 22, 2012 at 8:19 AM, Konrad Rzeszutek Wilk
<konrad@...nel.org> wrote:
> On Thu, Oct 18, 2012 at 01:50:29PM -0700, Yinghai Lu wrote:
>> Current "memmap=" only can take one entry every time.
>> when we have more entries, we have to use memmap= for each of them.
>>
>> For pxe booting, we have command line length limitation, those extra
>> "memmap=" would waste too much space.
>>
>> This patch make memmap= could take several entries one time,
>> and those entries will be split with ','
>
> Um, not sure what this patch has to do with this patchset?
> Should this be sent seperatly?

during debug those patches, need to punch hole in memmap find this problem.

thought other guys could have the same problem while test this patch set.

will move it as last one
--
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/