linux-kernel - Re: how to use memmap= option

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:	Thu, 30 Jan 2014 16:56:35 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Long Wind <longwind2009@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: how to use memmap= option

On 01/08/2014 06:06 AM, Long Wind wrote:
> On 1/8/14, Long Wind <longwind2009@...il.com> wrote:
>> I have asked Debian users, they don't seem to know
>> kernel 2.4/2.6 fail to boot on my PC
>> probably because it can't detect my memory
>> so I have to tell kernel memory map
>>
>> the following is copied from kernel-parameters.txt:
>>
>> memmap=exactmap	[KNL,X86] Enable setting of an exact
>> 			E820 memory map, as specified by the user.
>> 			Such memmap=exactmap lines can be constructed based on
>> 			BIOS output or other requirements. See the memmap=nn@ss
>> 			option description.
>>
>>
>>
>> Could you tell me how to construct memmap= lines?
>>
> 
> Sorry, it seems that I have posted wrong list
> If you could tell me which list I should join, I will very appreciate
> I'm leaving the list


No, this is the correct mailing list for your question (or use
linux-mm@...ck.org).

First you obtain a listing of your computer's valid memory map,
either from Linux booting on it (maybe not so likely on your computer)
or maybe from BIOS SETUP.

With that information, you construct a kernel command line with multiple
memmap= options.
You can see an example of this here:
http://lkml.indiana.edu/hypermail/linux/kernel/0809.1/0664.html


Hope that helps you.
-- 
~Randy
--
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/