From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Date: Tue, 27 Oct 2015 19:19:52 +0000 (-0400)
Subject: xen: fix the check of e_pfn in xen_find_pfn_range
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=abed7d0710e8f892c267932a9492ccf447674fb8;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git

xen: fix the check of e_pfn in xen_find_pfn_range

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>
---

diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 387b60d9bd0e..d1fac0e53d57 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -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);