From: Xishi Qiu <qiuxishi@huawei.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linn Crosetto <linn@hp.com>, Pekka Enberg <penberg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm,x86: fix span coverage in e820_all_mapped()
Date: Wed, 11 Dec 2013 09:42:16 +0800 [thread overview]
Message-ID: <52A7C2F8.4090207@huawei.com> (raw)
In-Reply-To: <b2e6fc81-a956-46f7-9a44-a707064c24a2@email.android.com>
On 2013/12/11 9:06, H. Peter Anvin wrote:
> Ok, the issue I thought we were discussing was actually [A,B) [B,C) [C,D) ...
>
Hi Peter,
Yes, in this case the function will return 1.
Thanks,
Xishi Qiu
> Yinghai Lu <yinghai@kernel.org> wrote:
>> On Tue, Dec 10, 2013 at 2:51 PM, H. Peter Anvin <hpa@zytor.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.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Xishi Qiu <qiuxishi@huawei.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linn Crosetto <linn@hp.com>, Pekka Enberg <penberg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm,x86: fix span coverage in e820_all_mapped()
Date: Wed, 11 Dec 2013 09:42:16 +0800 [thread overview]
Message-ID: <52A7C2F8.4090207@huawei.com> (raw)
In-Reply-To: <b2e6fc81-a956-46f7-9a44-a707064c24a2@email.android.com>
On 2013/12/11 9:06, H. Peter Anvin wrote:
> Ok, the issue I thought we were discussing was actually [A,B) [B,C) [C,D) ...
>
Hi Peter,
Yes, in this case the function will return 1.
Thanks,
Xishi Qiu
> Yinghai Lu <yinghai@kernel.org> wrote:
>> On Tue, Dec 10, 2013 at 2:51 PM, H. Peter Anvin <hpa@zytor.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.
>
next prev parent reply other threads:[~2013-12-11 1:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 9:06 [PATCH] mm,x86: fix span coverage in e820_all_mapped() Xishi Qiu
2013-12-10 9:06 ` Xishi Qiu
2013-12-10 21:06 ` Yinghai Lu
2013-12-10 21:06 ` Yinghai Lu
2013-12-10 21:29 ` H. Peter Anvin
2013-12-10 21:29 ` H. Peter Anvin
2013-12-10 21:52 ` Yinghai Lu
2013-12-10 21:52 ` Yinghai Lu
2013-12-10 22:51 ` H. Peter Anvin
2013-12-10 22:51 ` H. Peter Anvin
2013-12-11 0:35 ` Yinghai Lu
2013-12-11 0:35 ` Yinghai Lu
2013-12-11 1:06 ` H. Peter Anvin
2013-12-11 1:06 ` H. Peter Anvin
2013-12-11 1:42 ` Xishi Qiu [this message]
2013-12-11 1:42 ` Xishi Qiu
2013-12-11 1:35 ` Xishi Qiu
2013-12-11 1:35 ` Xishi Qiu
2013-12-11 2:55 ` H. Peter Anvin
2013-12-11 2:55 ` H. Peter Anvin
2013-12-11 3:55 ` Xishi Qiu
2013-12-11 3:55 ` Xishi Qiu
2013-12-11 4:02 ` H. Peter Anvin
2013-12-11 4:02 ` H. Peter Anvin
2013-12-11 4:39 ` Xishi Qiu
2013-12-11 4:39 ` Xishi Qiu
2013-12-11 5:27 ` H. Peter Anvin
2013-12-11 5:27 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A7C2F8.4090207@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.