Re: [PATCH -v2 09/13] x86: Fixup code testing if a pfn is direct mapped
From: Pekka Enberg
Date: Mon Sep 03 2012 - 01:32:29 EST
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> From: Jacob Shin <jacob.shin@xxxxxxx>
>
> Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and
> [ 4GB - max_pfn_mapped ) were always direct mapped, to now look up
> pfn_mapped ranges instead.
What problem does this fix? How did you find about it?
> -v2: change applying sequence to keep git bisecting working.
> so add dummy pfn_range_is_mapped(). - Yinghai Lu
>
> Signed-off-by: Jacob Shin <jacob.shin@xxxxxxx>
Yinghai's sign-off is missing.
--
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/