[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2e6fc81-a956-46f7-9a44-a707064c24a2@email.android.com>
Date: Tue, 10 Dec 2013 17:06:36 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: Xishi Qiu <qiuxishi@...wei.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linn Crosetto <linn@...com>, Pekka Enberg <penberg@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux MM <linux-mm@...ck.org>
Subject: Re: [PATCH] mm,x86: fix span coverage in e820_all_mapped()
Ok, the issue I thought we were discussing was actually [A,B) [B,C) [C,D) ...
Yinghai Lu <yinghai@...nel.org> wrote:
>On Tue, Dec 10, 2013 at 2:51 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> On 12/10/2013 01:52 PM, Yinghai Lu wrote:
>>>>
>>>> What happens if it spans more than two regions?
>>>
>>> [A, B), [B+1, C), [C+1, D) ?
>>> start in [A, B), and end in [C+1, D).
>>>
>>> old code:
>>> first with [A, B), start set to B.
>>> then with [B+1, C), start still keep as B.
>>> then with [C+1, D), start still keep as B.
>>> at last still return 0...aka not_all_mapped.
>>>
>>> old code is still right.
>>>
>>
>> Why not_all_mapped?
>
>[B, B+1), and [C, C+1) are not there.
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
--
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/
Powered by blists - more mailing lists