From: Dongxiao Xu <dongxiao.xu@intel.com>
To: xen-devel@lists.xensource.com
Cc: eddie.dong@intel.com, xiantao.zhang@intel.com, jun.nakajima@intel.com
Subject: [PATCH 1/2] nEPT: fix EPT pointer setting for L2 guest
Date: Fri, 25 Jan 2013 16:21:11 +0800 [thread overview]
Message-ID: <1359102072-5562-2-git-send-email-dongxiao.xu@intel.com> (raw)
In-Reply-To: <1359102072-5562-1-git-send-email-dongxiao.xu@intel.com>
Each time in virtual_vmentry(), the code needs to cover both EPT
and shadow mode for L2 guest, updating different EPT pointer to
shadow VMCS.
This fixes the issue that, launch a guest with EPT, then kill it
and launch a second guest with shadow, the second guest will hang
at the startup screen.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
---
xen/arch/x86/hvm/vmx/vvmx.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/xen/arch/x86/hvm/vmx/vvmx.c b/xen/arch/x86/hvm/vmx/vvmx.c
index 3c152c5..a90736a 100644
--- a/xen/arch/x86/hvm/vmx/vvmx.c
+++ b/xen/arch/x86/hvm/vmx/vvmx.c
@@ -1076,6 +1076,14 @@ uint64_t get_shadow_eptp(struct vcpu *v)
return ept_get_eptp(ept);
}
+static uint64_t get_host_eptp(struct vcpu *v)
+{
+ struct domain *d = v->domain;
+ struct ept_data *ept_data = &p2m_get_hostp2m(d)->ept;
+
+ return ept_get_eptp(ept_data);
+}
+
static bool_t nvmx_vpid_enabled(struct nestedvcpu *nvcpu)
{
uint32_t second_cntl;
@@ -1159,6 +1167,8 @@ static void virtual_vmentry(struct cpu_user_regs *regs)
/* Setup virtual ETP for L2 guest*/
if ( nestedhvm_paging_mode_hap(v) )
__vmwrite(EPT_POINTER, get_shadow_eptp(v));
+ else
+ __vmwrite(EPT_POINTER, get_host_eptp(v));
/* nested VPID support! */
if ( cpu_has_vmx_vpid && nvmx_vpid_enabled(nvcpu) )
--
1.7.1
next prev parent reply other threads:[~2013-01-25 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 8:21 [PATCH 0/2] nested vmx: bug fixes for nested EPT Dongxiao Xu
2013-01-25 8:21 ` Dongxiao Xu [this message]
2013-01-25 8:21 ` [PATCH 2/2] nEPT: fix INVEPT instruction parameter Dongxiao Xu
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=1359102072-5562-2-git-send-email-dongxiao.xu@intel.com \
--to=dongxiao.xu@intel.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--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).