From: Yang Zhang <yang.z.zhang@intel.com>
To: kvm@vger.kernel.org
Cc: mtosatti@redhat.com, gleb@redhat.com,
Yang Zhang <yang.z.zhang@intel.com>
Subject: [PATCH v4 0/2] x86, apicv: Add APIC virtualization support
Date: Fri, 7 Dec 2012 15:32:11 +0800 [thread overview]
Message-ID: <1354865533-17364-1-git-send-email-yang.z.zhang@intel.com> (raw)
APIC virtualization is a new feature which can eliminate most of VM exit
when vcpu handle a interrupt:
APIC register virtualization:
APIC read access doesn't cause APIC-access VM exits.
APIC write becomes trap-like.
Virtual interrupt delivery:
Virtual interrupt delivery avoids KVM to inject vAPIC interrupts
manually, which is fully taken care of by the hardware.
Please refer to Intel SDM volume 3, chapter 29 for more details.
Changes v3 to v4:
* use one option to control both register virtualization and virtual interrupt
delivery.
* Update eoi exit bitmap when programing ioapic or programing apic's id/dfr/ldr.
* Rebased on top of KVM upstream.
Changes v2 to v3:
* Drop Posted Interrupt patch from v3.
According Gleb's suggestion, we will use global vector for all VCPUs as notification
event vector. So we will rewrite the Posted Interrupt patch. And resend it later.
* Use TMR to set the eoi exiting bitmap. We only want to set eoi exiting bitmap for
those interrupt which is level trigger or has notifier in EOI write path. So TMR is
enough to distinguish the interrupt trigger mode.
* Simplify some code according Gleb's comments.
* rebased on top of KVM upstream.
Changes v1 to v2:
* Add Posted Interrupt support in this series patch.
* Since there is a notifer hook in vAPIC EOI for PIT interrupt. So always Set PIT
interrupt in eoi exit bitmap to force vmexit when EOI to interrupt.
* Rebased on top of KVM upstream
Yang Zhang (2):
x86, apicv: add APICv register virtualization support
x86, apicv: add virtual interrupt delivery support
arch/x86/include/asm/kvm_host.h | 4 +
arch/x86/include/asm/vmx.h | 13 ++++
arch/x86/kvm/irq.c | 79 ++++++++++++++++-----
arch/x86/kvm/lapic.c | 116 ++++++++++++++++++++++++++++---
arch/x86/kvm/lapic.h | 13 ++++
arch/x86/kvm/svm.c | 19 +++++
arch/x86/kvm/vmx.c | 149 ++++++++++++++++++++++++++++++++++++++-
arch/x86/kvm/x86.c | 18 +++--
virt/kvm/ioapic.c | 35 +++++++++
virt/kvm/ioapic.h | 1 +
10 files changed, 413 insertions(+), 34 deletions(-)
next reply other threads:[~2012-12-07 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 7:32 Yang Zhang [this message]
2012-12-07 7:32 ` [PATCH v4 1/2] x86, apicv: add APICv register virtualization support Yang Zhang
2012-12-07 7:32 ` [PATCH v4 2/2] x86, apicv: add virtual interrupt delivery support Yang Zhang
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=1354865533-17364-1-git-send-email-yang.z.zhang@intel.com \
--to=yang.z.zhang@intel.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).