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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Mar 2010 16:02:07 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC:	David Miller <davem@...emloft.net>, 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 03:47 PM, Benjamin Herrenschmidt wrote:
> On Wed, 2010-03-10 at 14:36 -0800, David Miller wrote:
>> 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. 
> 
> So I was about to say the exact same stuff here...
> 
let see:
1. if early_res + fw_memmap could be simplified...
2. or let x86 to use lmb instead of early_res,then add more to lmb.

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/