From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xudong Hao Subject: [PATCH 2/3] xen/p2m: Using INVALID_MFN instead of mfn_valid Date: Wed, 15 Aug 2012 14:55:20 +0800 Message-ID: <1345013720-20640-1-git-send-email-xudong.hao@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org Cc: @xen.org, Xudong Hao , tim@xen.orgtim, Xiantao Zhang List-Id: xen-devel@lists.xenproject.org 64 bits big bar's MMIO address may out of the highest gfn, then mfn_valid may return failure, so using INVALID_MFN to measure. Signed-off-by: Xiantao Zhang Signed-off-by: Xudong Hao diff -r 663eb766cdde xen/arch/x86/mm/p2m-ept.c --- a/xen/arch/x86/mm/p2m-ept.c Tue Jul 24 17:02:04 2012 +0200 +++ b/xen/arch/x86/mm/p2m-ept.c Thu Jul 26 15:40:01 2012 +0800 @@ -428,7 +428,7 @@ ept_set_entry(struct p2m_domain *p2m, un } /* Track the highest gfn for which we have ever had a valid mapping */ - if ( mfn_valid(mfn_x(mfn)) && + if ( (mfn_x(mfn) != INVALID_MFN) && (gfn + (1UL << order) - 1 > p2m->max_mapped_pfn) ) p2m->max_mapped_pfn = gfn + (1UL << order) - 1;