linux-kernel - Re: [RFC PATCH 6/6] sparc64: use early

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: <20100310.143602.266086944.davem@davemloft.net>
Date:	Wed, 10 Mar 2010 14:36:02 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	yinghai@...nel.org
Cc:	mingo@...e.hu, tglx@...utronix.de, hpa@...or.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [RFC PATCH 6/6] sparc64: use early_res and nobootmem

From: Yinghai Lu <yinghai@...nel.org>
Date: Wed, 10 Mar 2010 14:31:25 -0800

> they are array based.
> 
> 1. memmap is not changed after get it from firmware, <could be modified via mem= or memmap=>
> 2. early_res at first is static array, later it will be relocated to another position if the array is not big enough.

LMB could do this too with minor modifications.

Simply make the lmb.memory and lmb.reserved be pointers, and initially
they point into the static array(s).

Later the pointers can be repositioned to point to dynamically
allocated memory.

So please, for the third time, please show me how LMB with some minor
modifications is not able to satisfy your needs.
--
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/