Re: USB Passthrough 1.1 performance problem...

On Tue, Dec 14, 2010 at 12:02:03PM +0200, Avi Kivity wrote: > That could certainly be optimized. If the BAR is all along in its > page, both on guest and host (if not, we can migrate it, at least on > the host), we can use the same offset within the page on the host as > it appears on the guest, a

Re: [GIT PULL] kvm upstream updates

Am 29.12.2010 16:42, Avi Kivity wrote: > On 12/29/2010 05:05 PM, Jan Kiszka wrote: >> Am 28.12.2010 11:36, Avi Kivity wrote: >> > The following changes since commit >> > 4cdc1cd137e0b98766916a7cdf2d5a9b3c6632fa: >> > >> >target-mips: fix host CPU consumption when guest is idle (2010-12-27 >>

[PATCH] kvm: x86: Fix xcr0 reset mismerge

From: Jan Kiszka For unknown reset, xcr0 reset ended up in kvm_arch_update_guest_debug on upstream merge. Fix this and also remove the misleading comment (1 is THE reset value). Signed-off-by: Jan Kiszka --- target-i386/kvm.c |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff -

[PATCH] kvm: x86: Remove redundant mp_state initialization

From: Jan Kiszka kvm_arch_reset_vcpu initializes mp_state, and that function is invoked right after kvm_arch_init_vcpu. Signed-off-by: Jan Kiszka --- target-i386/kvm.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/target-i386/kvm.c b/target-i386/kvm.c index 32310fa.

[PATCH 5/5] kvm: x86: Introduce kvmclock device to save/restore its state

From: Jan Kiszka If kvmclock is used, which implies the kernel supports it, register a kvmclock device with the sysbus. Its main purpose is to save and restore the kernel state on migration, but this will also allow to visualize it one day. Signed-off-by: Jan Kiszka CC: Glauber Costa --- targ

[PATCH 3/5] kvm: x86: Drop MCE MSRs write back restrictions

From: Jan Kiszka There is no need to restrict writing back MCE MSRs to reset or full state updates as setting their values has no side effects. Signed-off-by: Jan Kiszka CC: Huang Ying --- target-i386/kvm.c | 12 1 files changed, 4 insertions(+), 8 deletions(-) diff --git a/ta

[PATCH 4/5] kvm: Eliminate KVMState arguments

From: Jan Kiszka QEMU supports only one VM, so there is only one kvm_state per process, and we gain nothing passing a reference to it around. Eliminate any need to refer to it outside of kvm-all.c. Signed-off-by: Jan Kiszka --- cpu-defs.h|2 - kvm-all.c | 233 +

[PATCH 1/5] kvm: x86: Refactor msr_star/hsave_pa setup and checks

From: Jan Kiszka Simplify kvm_has_msr_star/hsave_pa to booleans and push their one-time initialization into kvm_arch_init. Also handle potential errors of that setup procedure. Signed-off-by: Jan Kiszka --- target-i386/kvm.c | 47 +++ 1 files chang

[PATCH 0/5] [uq/master] MSR refactorings, KVMState elimination, kvmclock device

More refactorings of upstream KVM to allow further unifications with qemu-kvm. See patches for details. Jan Kiszka (5): 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

[PATCH 2/5] kvm: x86: Reset paravirtual MSRs

From: Jan Kiszka Make sure to clear MSR_KVM_SYSTEM_TIME, MSR_KVM_WALL_CLOCK, and MSR_KVM_ASYNC_PF_EN so that a freshly booted guest cannot be disturbed by old values. Signed-off-by: Jan Kiszka CC: Glauber Costa --- target-i386/kvm.c | 10 ++ 1 files changed, 10 insertions(+), 0 dele

Re: [RFC 2/2] KVM, MCE, unpoison memory address across reboot

Am 31.12.2010 06:22, Huang Ying wrote: > In Linux kernel HWPoison processing implementation, the virtual > address in processes mapping the error physical memory page is marked > as HWPoison. So that, the further accessing to the virtual > address will kill corresponding processes with SIGBUS. >