From: David Vrabel Subject: Re: [PATCH 3/3] xen: use correct type for physical addresses Date: Fri, 9 Jan 2015 12:51:49 +0000 Message-ID: <54AFCEE5.3060402@citrix.com> References: <1420736490-15351-1-git-send-email-jgross@suse.com> <1420736490-15351-4-git-send-email-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1420736490-15351-4-git-send-email-jgross@suse.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Juergen Gross , linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com, david.vrabel@citrix.com, boris.ostrovsky@oracle.com List-Id: xen-devel@lists.xenproject.org On 08/01/15 17:01, Juergen Gross wrote: > When converting a pfn to a physical address be sure to use 64 bit > wide types. > > Also avoid invalidating memory for zero sized non-aligned extra > memory regions. "Also" means this bit should be in another patch... > Signed-off-by: Juergen Gross > Tested-by: Boris Ostrovsky > --- > arch/x86/xen/setup.c | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c > index feb6d86..8839d7b 100644 > --- a/arch/x86/xen/setup.c > +++ b/arch/x86/xen/setup.c > @@ -160,6 +160,8 @@ void __init xen_inv_extra_mem(void) > int i; > > for (i = 0; i < XEN_EXTRA_MEM_MAX_REGIONS; i++) { > + if (!xen_extra_mem[i].size) > + continue; > pfn_s = PFN_DOWN(xen_extra_mem[i].start); > pfn_e = PFN_UP(xen_extra_mem[i].start + xen_extra_mem[i].size); > for (pfn = pfn_s; pfn < pfn_e; pfn++) i.e., this hunk should be in a separate path. David