Messages in this thread | | | Date | Mon, 3 Sep 2012 08:32:36 +0300 | Subject | Re: [PATCH -v2 09/13] x86: Fixup code testing if a pfn is direct mapped | From | Pekka Enberg <> |
| |
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu <yinghai@kernel.org> wrote: > From: Jacob Shin <jacob.shin@amd.com> > > 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@amd.com>
Yinghai's sign-off is missing.
| |