On Wed, 2012-05-09 at 16:10 +0300, Avi Kivity wrote:
> After a long hiatus, here are a bunch of very delayed fixes for 3.3.5.

Are any of these also applicable to 3.2.y?

Also, would you consider these two fixes from 3.3 important enough for
3.2.y?

d6185f20a0efbf175e12831d0de330e4f21725aa KVM: nVMX: Add KVM_REQ_IMMEDIATE_EXIT
51cfe38ea50aa631f58ed8c340ed6f0143c325a8 KVM: nVMX: Fix warning-causing 
idt-vectoring-info behavior

Ben.

> Alex Williamson (1):
>   KVM: lock slots_lock around device assignment
> 
> Avi Kivity (3):
>   KVM: Ensure all vcpus are consistent with in-kernel irqchip settings
>   KVM: VMX: Fix delayed load of shared MSRs
>   KVM: VMX: Fix kvm_set_shared_msr() called in preemptible context
> 
> Christian Borntraeger (1):
>   KVM: s390: Sanitize fpc registers for KVM_SET_FPU
> 
> Gleb Natapov (1):
>   KVM: x86 emulator: correctly mask pmc index bits in RDPMC instruction
>     emulation
> 
> Jens Freimann (1):
>   KVM: s390: do store status after handling STOP_ON_STOP bit
> 
> Marcelo Tosatti (1):
>   KVM: VMX: vmx_set_cr0 expects kvm->srcu locked
> 
> Nadav Har'El (1):
>   KVM: nVMX: Fix erroneous exception bitmap check
> 
> Takuya Yoshikawa (2):
>   KVM: Fix write protection race during dirty logging
>   KVM: mmu_notifier: Flush TLBs before releasing mmu_lock
> 
>  arch/ia64/kvm/kvm-ia64.c  |    5 +++++
>  arch/s390/kvm/intercept.c |   20 ++++++++++++--------
>  arch/s390/kvm/kvm-s390.c  |    2 +-
>  arch/x86/kvm/pmu.c        |    2 +-
>  arch/x86/kvm/vmx.c        |   10 +++++++++-
>  arch/x86/kvm/x86.c        |   19 +++++++++++++------
>  include/linux/kvm_host.h  |    7 +++++++
>  virt/kvm/iommu.c          |   23 +++++++++++++++--------
>  virt/kvm/kvm_main.c       |   23 ++++++++++++++---------
>  9 files changed, 77 insertions(+), 34 deletions(-)
> 

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
                                                         - Carolyn Scheppner

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to