xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: xen-devel@lists.xen.org
Cc: eddie.dong@intel.com, jun.nakajima@intel.com
Subject: [PATCH v2 00/11] nested vmx: bug fixes and feature enabling
Date: Wed,  5 Dec 2012 21:02:03 +0800	[thread overview]
Message-ID: <1354712534-31338-1-git-send-email-dongxiao.xu@intel.com> (raw)

This series of patches contain some bug fixes and feature enabling for
nested vmx, please help to review and pull.

For the following patches, it doesn't have influence about Xen on Xen functionality.
No special need to backport to 4.2.x (My own opinion).

Changes from v1 to v2:
 - Use literal name instead of hard numbers to expose default 1 settings in VMX related MSRs.
 - For TRUE VMX MSRs, we use the same value as normal VMX MSRs.
 - Fix a coding style issue.

Thanks,
Dongxiao

Dongxiao Xu (11):
  nested vmx: emulate MSR bitmaps
  nested vmx: use literal name instead of hard numbers
  nested vmx: expose bit 55 of IA32_VMX_BASIC_MSR to guest VMM
  nested vmx: fix rflags status in virtual vmexit
  nested vmx: fix handling of RDTSC
  nested vmx: fix DR access VM exit
  nested vmx: enable IA32E mode while do VM entry
  nested vmx: enable "Virtualize APIC accesses" feature for L1 VMM
  nested vmx: enable PAUSE and RDPMC exiting for L1 VMM
  nested vmx: fix interrupt delivery to L2 guest
  nested vmx: check host ability when intercept MSR read

 xen/arch/x86/hvm/vmx/intr.c        |   11 ++-
 xen/arch/x86/hvm/vmx/vmcs.c        |   28 +++++++++
 xen/arch/x86/hvm/vmx/vmx.c         |    2 +-
 xen/arch/x86/hvm/vmx/vvmx.c        |  115 ++++++++++++++++++++++++++++++------
 xen/include/asm-x86/hvm/vmx/vmcs.h |    1 +
 xen/include/asm-x86/hvm/vmx/vmx.h  |    2 +
 xen/include/asm-x86/hvm/vmx/vvmx.h |   10 +++
 7 files changed, 145 insertions(+), 24 deletions(-)

             reply	other threads:[~2012-12-05 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 13:02 Dongxiao Xu [this message]
2012-12-05 13:02 ` [PATCH v2 01/11] nested vmx: emulate MSR bitmaps Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 02/11] nested vmx: use literal name instead of hard numbers Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 03/11] nested vmx: expose bit 55 of IA32_VMX_BASIC_MSR to guest VMM Dongxiao Xu
2012-12-05 16:31   ` Jan Beulich
2012-12-05 13:02 ` [PATCH v2 04/11] nested vmx: fix rflags status in virtual vmexit Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 05/11] nested vmx: fix handling of RDTSC Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 06/11] nested vmx: fix DR access VM exit Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 07/11] nested vmx: enable IA32E mode while do VM entry Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 08/11] nested vmx: enable "Virtualize APIC accesses" feature for L1 VMM Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 09/11] nested vmx: enable PAUSE and RDPMC exiting " Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 10/11] nested vmx: fix interrupt delivery to L2 guest Dongxiao Xu
2012-12-05 13:02 ` [PATCH v2 11/11] nested vmx: check host ability when intercept MSR read Dongxiao Xu
2012-12-05 16:33 ` [PATCH v2 00/11] nested vmx: bug fixes and feature enabling Jan Beulich

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=1354712534-31338-1-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.xen.org \
    /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).