xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 1/9] nested vmx: enable Monitor Trap Flag for L1 VMM
Date: Wed, 28 Nov 2012 15:11:56 +0800	[thread overview]
Message-ID: <1354086724-1959-2-git-send-email-dongxiao.xu@intel.com> (raw)
In-Reply-To: <1354086724-1959-1-git-send-email-dongxiao.xu@intel.com>

Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
---
 xen/arch/x86/hvm/vmx/vvmx.c |   10 ++++++++--
 1 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/xen/arch/x86/hvm/vmx/vvmx.c b/xen/arch/x86/hvm/vmx/vvmx.c
index 4f6c712..c953278 100644
--- a/xen/arch/x86/hvm/vmx/vvmx.c
+++ b/xen/arch/x86/hvm/vmx/vvmx.c
@@ -1259,7 +1259,7 @@ int nvmx_msr_read_intercept(unsigned int msr, u64 *msr_content)
         break;
     case MSR_IA32_VMX_PROCBASED_CTLS:
         /* 1-seetings */
-        data = (CPU_BASED_HLT_EXITING |
+        data = CPU_BASED_HLT_EXITING |
                CPU_BASED_VIRTUAL_INTR_PENDING |
                CPU_BASED_CR8_LOAD_EXITING |
                CPU_BASED_CR8_STORE_EXITING |
@@ -1272,7 +1272,8 @@ int nvmx_msr_read_intercept(unsigned int msr, u64 *msr_content)
                CPU_BASED_ACTIVATE_IO_BITMAP |
                CPU_BASED_USE_TSC_OFFSETING |
                CPU_BASED_UNCOND_IO_EXITING |
-               CPU_BASED_RDTSC_EXITING);
+               CPU_BASED_RDTSC_EXITING |
+               CPU_BASED_MONITOR_TRAP_FLAG;
         /* bit 1, 4-6,8,13-16,26 must be 1 (refer G4 of SDM) */
         tmp = ( (1<<26) | (0xf << 13) | 0x100 | (0x7 << 4) | 0x2);
         /* 0-settings */
@@ -1475,6 +1476,11 @@ int nvmx_n2_vmexit_handler(struct cpu_user_regs *regs,
         if ( ctrl & CPU_BASED_VIRTUAL_NMI_PENDING )
             nvcpu->nv_vmexit_pending = 1;
         break;
+    case EXIT_REASON_MONITOR_TRAP_FLAG:
+        ctrl = __n2_exec_control(v);
+        if ( ctrl & CPU_BASED_MONITOR_TRAP_FLAG)
+            nvcpu->nv_vmexit_pending = 1;
+        break;
     /* L1 has priority handling several other types of exits */
     case EXIT_REASON_HLT:
         ctrl = __n2_exec_control(v);
-- 
1.7.1

  reply	other threads:[~2012-11-28  7:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  7:11 [PATCH 0/9] nested vmx: expose some vmx features to L1 VMM Dongxiao Xu
2012-11-28  7:11 ` Dongxiao Xu [this message]
2012-11-28  7:11 ` [PATCH 2/9] nested vmx: enable NMI-window exiting for " Dongxiao Xu
2012-11-28  7:11 ` [PATCH 3/9] nested vmx: enable secondary processor-based VM-Execution controls Dongxiao Xu
2012-11-28  7:11 ` [PATCH 4/9] nested vmx: enable Descriptor-table exiting for L1 VMM Dongxiao Xu
2012-11-28  7:12 ` [PATCH 5/9] nested vmx: enable VMX-preemption timer " Dongxiao Xu
2012-11-28  7:12 ` [PATCH 6/9] nested vmx: enable save VMX-preemption timer feature " Dongxiao Xu
2012-11-28  7:12 ` [PATCH 7/9] nested vmx: enable load and save IA32_PAT " Dongxiao Xu
2012-11-28  7:12 ` [PATCH 8/9] nested vmx: enable load and save IA32_EFER " Dongxiao Xu
2012-11-28  7:12 ` [PATCH 9/9] nested vmx: enable load IA32_PERF_GLOBAL_CTRL " Dongxiao Xu
2012-11-28 10:08 ` [PATCH 0/9] nested vmx: expose some vmx features to " Jan Beulich
2012-11-30  1:54   ` Nakajima, Jun

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=1354086724-1959-2-git-send-email-dongxiao.xu@intel.com \
    --to=dongxiao.xu@intel.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).