From: Xudong Hao <xudong.hao@intel.com>
To: xen-devel@lists.xen.org
Cc: @xen.org, Xudong Hao <xudong.hao@intel.com>,
tim@xen.orgtim, Xiantao Zhang <xiantao.zhang@intel.com>
Subject: [PATCH 2/3] xen/p2m: Using INVALID_MFN instead of mfn_valid
Date: Wed, 15 Aug 2012 14:55:20 +0800 [thread overview]
Message-ID: <1345013720-20640-1-git-send-email-xudong.hao@intel.com> (raw)
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 <xiantao.zhang@intel.com>
Signed-off-by: Xudong Hao <xudong.hao@intel.com>
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;
next reply other threads:[~2012-08-15 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 6:55 Xudong Hao [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-15 6:57 [PATCH 2/3] xen/p2m: Using INVALID_MFN instead of mfn_valid Xudong Hao
2012-08-15 9:21 ` Jan Beulich
2012-08-16 10:05 ` Hao, Xudong
2012-08-16 10:12 ` Jan Beulich
2012-08-16 10:31 ` Hao, Xudong
2012-08-16 10:41 ` Jan Beulich
2012-08-16 11:01 ` Tim Deegan
2012-08-16 19:14 ` Mukesh Rathor
[not found] <mailman.10813.1345115327.1399.xen-devel@lists.xen.org>
2012-08-16 17:17 ` Andres Lagar-Cavilla
2012-08-16 17:47 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1345013720-20640-1-git-send-email-xudong.hao@intel.com \
--to=xudong.hao@intel.com \
--cc=tim@xen.orgtim \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).