linux-kernel - Re: reserve memory in low physical address

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: <20061031081239.GA9539@linux-sh.org>
Date:	Tue, 31 Oct 2006 17:12:39 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Jun Sun <jsun@...sun.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: reserve memory in low physical address - possible?

On Mon, Oct 30, 2006 at 11:22:03PM -0800, Jun Sun wrote:
> I understand it is possible to reserve some memory at the end by
> specifying "mem=xxxM" option in kernel command line.  I looked into
> "memmap=xxxM" option but it appears not helpful for what I want.
> 
memmap takes multiple arguments, including the start address for the
memory map. You could also bump min_low_pfn manually if memmap= isn't
suitable for you, something like:

	magic_space = PFN_UP(init_pg_tables_end);
	min_low_pfn = magic_space + magic_size;

(assuming magic_size is rounded up already), should work fine. Though
memmap= already takes care of most of this for you, could you explain why
it's unsuitable?
-
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/