RE: [PATCH] x86/pat: no need to check overlaps with more than oneentry in chk_conflict

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: linux-kernel-owner@xxxxxxxxxxxxxxx 
>[mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] On Behalf Of Xiaotian Feng
>Sent: Tuesday, November 17, 2009 6:48 PM
>To: x86@xxxxxxxxxx
>Cc: linux-kernel@xxxxxxxxxxxxxxx; 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/