From: Wincy Van <fanwenyi0529@gmail.com>
To: pbonzini@redhat.com, gleb@kernel.org, yang.z.zhang@intel.com,
fanwenyi0529@gmail.com
Cc: wanpeng.li@linux.intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, jan.kiszka@web.de
Subject: [PATCH resend v5 0/6] KVM: nVMX: Enable nested apicv support
Date: Tue, 3 Feb 2015 23:46:55 +0800 [thread overview]
Message-ID: <1422978415-2006-1-git-send-email-fanwenyi0529@gmail.com> (raw)
v1 ---> v2:
Use spin lock to ensure vmcs12 is safe when doing nested
posted interrupt delivery.
v2 ---> v3:
1. Add a new field in nested_vmx to avoid the spin lock in v2.
2. Drop send eoi to L1 when doing nested interrupt delivery.
3. Use hardware MSR bitmap to enable nested virtualize x2apic
mode.
v3 ---> v4:
1. Optimize nested msr bitmap merging.
2. Allocate nested msr bitmap only when nested == 1.
3. Inline the nested vmx control checking functions.
v4 ---> v5:
1. Move EXIT_REASON_APIC_WRITE to the apic register
virtualization patch.
2. Accomplish nested posted interrupts manually if
they are not recognized by hardware.
Wincy Van (6):
KVM: nVMX: Use hardware MSR bitmap
KVM: nVMX: Enable nested virtualize x2apic mode
KVM: nVMX: Make nested control MSRs per-cpu
KVM: nVMX: Enable nested apic register virtualization
KVM: nVMX: Enable nested virtual interrupt delivery
KVM: nVMX: Enable nested posted interrupt processing
arch/x86/kvm/lapic.c | 13 +-
arch/x86/kvm/lapic.h | 1 +
arch/x86/kvm/vmx.c | 647 ++++++++++++++++++++++++++++++++++++++++++--------
3 files changed, 557 insertions(+), 104 deletions(-)
next reply other threads:[~2015-02-03 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 15:46 Wincy Van [this message]
2015-02-03 16:15 ` [PATCH resend v5 0/6] KVM: nVMX: Enable nested apicv support Paolo Bonzini
2015-02-04 2:09 ` Wincy Van
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=1422978415-2006-1-git-send-email-fanwenyi0529@gmail.com \
--to=fanwenyi0529@gmail.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wanpeng.li@linux.intel.com \
--cc=yang.z.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