From: Avi Kivity <avi@redhat.com>
To: "Li, Jiongxi" <jiongxi.li@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/5]KVM:Enable APIC-Register Virtualization and Virtual-interrupt delivery
Date: Thu, 06 Sep 2012 18:45:24 +0300 [thread overview]
Message-ID: <5048C514.6090207@redhat.com> (raw)
In-Reply-To: <D9137FCD9CFF644B965863BCFBEDABB877AC42@SHSMSX101.ccr.corp.intel.com>
On 09/05/2012 08:40 AM, Li, Jiongxi wrote:
> The VMCS includes controls that enable the virtualization of interrupts and the Advanced Programmable Interrupt Controller (APIC).
> When these controls are used, the processor will emulate many accesses to the APIC, track the state of the virtual APIC, and deliver virtual interrupts - all in VMX non-root operation without a VM exit.
> You can refer to Chapter 29 of the latest SDM.
>
> APICv support in KVM is split into 5 patches:
> 0001-x86-apicv-add-APICv-register-virtualization-support.patch - enable APICv register virtualization
> 0002-x86-apicv-adjust-for-virtual-interrupt-delivery.patch - add basic KVM frameowrk for virtual interrupt delivery
> 0003-x86-apicv-enable-virtual-interrupt-delivery-for-VMX.patch - enable APICv virtual interrupt delivery
> 0004-x86-apicv-add-interface-for-poking-EOI-exit-bitmap.patch - EOI exit bitmap handling
> 0005-x86-apicv-add-virtual-x2apic-support.patch - handle MSR style in virtual x2apic
>
> Apply them in above order
> APICv is disabled by default, and use below command to enable it:
> modprobe enable_apicv_reg=1 enable_apicv_vid=1
>
Please use git send-email in the future for correct threading of the
messages.
I don't see patches for enabling posted interrupts? This can improve
both assigned and virtual interrupt delivery.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-06 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 5:40 [PATCH 0/5]KVM:Enable APIC-Register Virtualization and Virtual-interrupt delivery Li, Jiongxi
2012-09-06 15:45 ` Avi Kivity [this message]
2012-09-14 14:14 ` Li, Jiongxi
2012-09-16 9:30 ` Avi Kivity
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=5048C514.6090207@redhat.com \
--to=avi@redhat.com \
--cc=jiongxi.li@intel.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.