From: Jason Wang
Date: Sat, 8 Dec 2012 01:04:54 +0800
> This series is an update version (hope the final version) of multiqueue
> (VIRTIO_NET_F_MQ) support in virtio-net driver. All previous comments were
> addressed, the work were based on Krishna Kumar's work to let virtio-net use
> multiple r
https://bugzilla.kernel.org/show_bug.cgi?id=42980
--- Comment #21 from Ian Pilcher 2012-12-08 20:50:25 ---
I just hit this again (I think). Pretty much out of the blue, with a bunch of
VMs running, including at least 2 nested guests.
I have been trying to get a kdump of this, and I believe
Hi Alex,
first of all, I apologize for not reporting things properly. The "vector"
values that I see passed to request_threaded_irq() are not zeros. They are
unique IRQ values as you mentioned. I do not, however, see the
disabling-and-reenabling sequence as you wrote. The usual sequence for me
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 need
update architecture specific indica
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
Signed-off-by: Kevin Tian
---
arch/x8
From: Yang Zhang
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 in
- APIC read doesn't cause VM-Exit
- APIC write becomes trap-like
Signed-off-by: Yang Zhang
---
arch/x86/include/asm/vmx.h |2 ++
arch/x86/kvm/lapic.c | 15 +++
arch/x86/kvm/lapic.h |2 ++
arch/x86/kvm/vmx.c | 33 -
4 fil
On 2012-12-07 20:51, Andrew Honig wrote:
> I've noticed a memory leak that occurs in vmx.c.
>
> In alloc_apic_access_page, it calls __kvm_set_memory_region(kvm,
> &kvm_userspace_mem, 0). __kvm_set_memory_region calls
> kvm_arch_prepare_memory_region, which because the user_alloc parameter
> is 0
