Gleb Natapov wrote on 2012-12-13:
On Thu, Dec 13, 2012 at 08:19:01AM +, Zhang, Yang Z wrote:
Gleb Natapov wrote on 2012-12-13:
On Thu, Dec 13, 2012 at 08:03:06AM +, Zhang, Yang Z wrote:
Gleb Natapov wrote on 2012-12-13:
On Thu, Dec 13, 2012 at 07:54:35AM +, Zhang, Yang Z wrote:
- Original Message -
From: Marc Haber mh+...@zugschlus.de
To: KVM kvm@vger.kernel.org
Sent: Saturday, December 15, 2012 7:47:11 AM
Subject: [user question] Opinions about running Windows in KVM
Hi,
I am a heavy user of virtualization in my private zoo of systems. My
main
Il 16/12/2012 19:55, Andrew Cathrow ha scritto:
After the install and the resulting patch orgy finished, I noticed
that the KVM-based Windows install was running much slower than an
existing Windows 7 guest running under VirtualBox (on the same
hardware and a similiarly configured VM), which
From: Yang Zhang yang.z.zh...@intel.com
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
- APIC read doesn't cause VM-Exit
- APIC write becomes trap-like
Signed-off-by: Kevin Tian kevin.t...@intel.com
Signed-off-by: Yang Zhang yang.z.zh...@intel.com
---
arch/x86/include/asm/vmx.h |2 ++
arch/x86/kvm/lapic.c | 15 +++
arch/x86/kvm/lapic.h |2 ++
basically to benefit from apicv, we need clear MSR bitmap for
corresponding x2apic MSRs:
0x800 - 0x8ff: no read intercept for apicv register virtualization
TPR,EOI,SELF-IPI: no write intercept for virtual interrupt delivery
Signed-off-by: Yang Zhang yang.z.zh...@intel.com
Signed-off-by:
From: Yang Zhang yang.z.zh...@intel.com
Virtual interrupt delivery avoids KVM to inject vAPIC interrupts
manually, which is fully taken care of by the hardware. This needs
some special awareness into existing interrupr injection path:
- for pending interrupt, instead of direct injection, we may
