linux-kernel - Re: [PATCH 1/9] x86: move range related operation to one file

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: <4B2C14A3.90906@kernel.org>
Date:	Fri, 18 Dec 2009 15:47:47 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/9] x86: move range related operation to one file

H. Peter Anvin wrote:
> On 12/18/2009 12:17 PM, Yinghai Lu wrote:
>> yes here is we have [start, end] instead of [start, end)
>>
>> those range operation is used for one purpose:
>> add several ranges, and subtract some other ranges, it will take out overlap between those two sets.
>> and leave out the range that could be used.
>>
>> and it is array based...for early stage.
>>
> 
> Yes.  We should be able to use the *exact same code* for the e820
> ranges, using the e820 attribute as the attribute parameters, and a
> simple boolean for the case where all you want is inclusion/exclusion.
> And yes, I agree array based is the right thing to do for the early code.

i could try to merge range handling to to early_res handling code.
first step is change the end in range to be consistent to the one in early_res.

later could move them into kernel/range.c or kernel/early_res.c after we convert all bootmem to early_res.

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/