From: confucius <henanwxr@hotmail.com>
To: xen-devel@lists.xensource.com
Subject: Question about EPT translation
Date: Fri, 27 May 2011 09:17:23 -0700 (PDT) [thread overview]
Message-ID: <1306513043984-4432564.post@n5.nabble.com> (raw)
Hi,everyone. I have some questions.
1. Does hvmoader need EPT for address translation when it is running?
2. I am sure the guest kernel need EPT when running, but not sure whether
hvmloader also needs. I think when virtual bios in hvmloader running, we
should make virtual bios sees as if the memory starting from 0, so hvmloader
needs EPT, am I right?
3. If hvmloader needs EPT, where we construct EPT structure for it? I can't
find correlative part in code flow.
Any helps?
--
View this message in context: http://xen.1045712.n5.nabble.com/Question-about-EPT-translation-tp4432564p4432564.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next reply other threads:[~2011-05-27 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 16:17 confucius [this message]
2011-05-30 8:42 ` Question about EPT translation Tim Deegan
[not found] <BLU163-ds373A534D93901C3E0FB82DE780@phx.gbl>
2011-05-29 21:49 ` Daniel Castro
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=1306513043984-4432564.post@n5.nabble.com \
--to=henanwxr@hotmail.com \
--cc=xen-devel@lists.xensource.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).