From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Xiaotian Feng <dfeng@redhat.com>, "x86@kernel.org" <x86@kernel.org>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
       Ingo Molnar <mingo@redhat.com>,
       "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Date: Wed, 18 Nov 2009 09:30:58 -0800
Subject: RE: [PATCH] x86/pat: no need to check overlaps with more than one
 entry in chk_conflict
Thread-Topic: [PATCH] x86/pat: no need to check overlaps with more than one
 entry in chk_conflict
Thread-Index: AcpoAYzFyqyl8wxfRzS1zs+PLRoMRwAcvGNA
Message-ID: <7E82351C108FA840AB1866AC776AEC46767A389F@orsmsx505.amr.corp.intel.com>
References: <1258512455-1891-1-git-send-email-dfeng@redhat.com>
In-Reply-To: <1258512455-1891-1-git-send-email-dfeng@redhat.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1134
Lines: 33

>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Xiaotian Feng
>Sent: Tuesday, November 17, 2009 6:48 PM
>To: x86@kernel.org
>Cc: linux-kernel@vger.kernel.org; Xiaotian Feng; Ingo Molnar; 
>Siddha, Suresh B; Pallipadi, Venkatesh
>Subject: [PATCH] x86/pat: no need to check overlaps with more 
>than one entry in chk_conflict
>
>memtype list is built via reserve_memtype, for the overlapped 
>areas, they're
>all the same type, otherwise reserve_memtype will fail to 
>insert it into the
>list. So there's no need to check overlaps with more than one 
>entry in the
>chk_conflict code.

NAK.

The reason we have to check for more than one entry is for the cases
like this.

New entry:                   s-------------------e
Existing entries:         s----e     s-----e   s----e
(s=start, e=end)

Thanks,
Venki--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/