xen: fix the check of e_pfn in xen_find_pfn_range
authorZhenzhong Duan <zhenzhong.duan@oracle.com>
Tue, 27 Oct 2015 19:19:52 +0000 (15:19 -0400)
committerDavid Vrabel <david.vrabel@citrix.com>
Mon, 2 Nov 2015 17:47:38 +0000 (17:47 +0000)
On some NUMA system, after dom0 up, we see below warning even if there are
enough pfn ranges that could be used for remapping:
"Unable to find available pfn range, not remapping identity pages"

Fix it to avoid getting a memory region of zero size in xen_find_pfn_range.

Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
arch/x86/xen/setup.c

index 387b60d9bd0ee3995aab148468be0fa6ddc335b5..d1fac0e53d570b2e4162a396b80acc305da87ef9 100644 (file)
@@ -212,7 +212,7 @@ static unsigned long __init xen_find_pfn_range(unsigned long *min_pfn)
                e_pfn = PFN_DOWN(entry->addr + entry->size);
 
                /* We only care about E820 after this */
-               if (e_pfn < *min_pfn)
+               if (e_pfn <= *min_pfn)
                        continue;
 
                s_pfn = PFN_UP(entry->addr);