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]

Date:	Wed, 10 Mar 2010 14:31:25 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	David Miller <davem@...emloft.net>
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

On 03/10/2010 02:17 PM, David Miller wrote:
> From: Yinghai Lu <yinghai@...nel.org>
> Date: Wed, 10 Mar 2010 14:10:22 -0800
> 
>> On 03/10/2010 01:36 PM, David Miller wrote:
>>> And LMB cannot fill this void with some minor modifications?
>>
>> early_res array could be increased automatically...
>>
>> could be something like:
>> keep lmb.memory part, and use early_res for reserved parts...
> 
> LMB has a reserved region.
> 
> I still have yet to see any fundamental reason why LMB
> cannot, all by itself, be used to solve this problem too.

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.

so arch only need to have it's own setup_memory_map, to fill fw_memmap according to FW,
and later using find_fw_memmap_area and reserve_early all the way...
<don't need allocate bootmem map anymore>

later in mem_init to call free_all_memory_core_early instead.
<it will use memory subtract all reserved list to get final free list, and ...>

YH

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