Next round, addressing review comments and new findings: - new: Flush coalesced mmio buffer on IO window exits - new: Do not use qemu_fair_mutex in kvm mode - new: Implicitly clear nmi_injected/pending on reset - new: Fix !CONFIG_KVM_PARA build - reworked: Read kvmclock only once per stopped phase - reworked: Consolidate must-have capability checks - reworked: Keep TSS/identity map reservation unconditional - fixed: qemu-user breakage of CPU_DUMP_CODE patch - fixed: Avoid redundant reset of MSR state variables Jan Kiszka (21): kvm: Fix coding style violations kvm: Drop return value of kvm_cpu_exec kvm: Stop on all fatal exit reasons kvm: Improve reporting of fatal errors x86: Optionally dump code bytes on cpu_dump_state kvm: x86: Align kvm_arch_put_registers code with comment kvm: x86: Prepare kvm_get_mp_state for in-kernel irqchip kvm: x86: Remove redundant mp_state initialization kvm: x86: Fix xcr0 reset mismerge kvm: x86: Refactor msr_star/hsave_pa setup and checks kvm: x86: Reset paravirtual MSRs kvm: x86: Drop MCE MSRs write back restrictions kvm: Eliminate KVMState arguments kvm: x86: Fix !CONFIG_KVM_PARA build kvm: x86: Introduce kvmclock device to save/restore its state kvm: Drop smp_cpus argument from init functions kvm: Consolidate must-have capability checks kvm: x86: Rework identity map and TSS setup for larger BIOS sizes kvm: Flush coalesced mmio buffer on IO window exits kvm: Do not use qemu_fair_mutex kvm: x86: Implicitly clear nmi_injected/pending on reset configure | 39 +++-- cpu-all.h | 2 + cpu-defs.h | 2 - cpus.c | 2 - kvm-all.c | 447 +++++++++++++++++++++++-------------------------- kvm-stub.c | 8 +- kvm.h | 29 ++-- target-i386/cpu.h | 8 +- target-i386/cpuid.c | 14 +- target-i386/helper.c | 21 +++ target-i386/kvm.c | 362 +++++++++++++++++++++++++--------------- target-i386/kvm_x86.h | 3 + target-ppc/kvm.c | 20 ++- target-s390x/kvm.c | 12 +- vl.c | 2 +- 15 files changed, 546 insertions(+), 425 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
