Move kvm.arch.hyperv initialization and cleanup to separate functions.
For now only a mutex is inited in the former, and the latter is empty;
more stuff will go in there in a followup patch.
Signed-off-by: Roman Kagan
Reviewed-by: David Hildenbrand
Signed-off-by: Radim Krčmář
(cherry picked fr
From: Dan Carpenter
"rep_done" is always zero so the "(((u64)rep_done & 0xfff) << 32)"
expression is just zero. We can remove the "res" temporary variable as
well and just use "ret" directly.
Signed-off-by: Dan Carpenter
Signed-off-by: Paolo Bonzini
(cherry picked from commit d32ef547fdbbeb9c
From: Vitaly Kuznetsov
When a new vector is written to SINx we update vec_bitmap/auto_eoi_bitmap
but we forget to remove old vector from these masks (in case it is not
present in some other SINTx).
Signed-off-by: Vitaly Kuznetsov
Reviewed-by: Roman Kagan
Signed-off-by: Radim Krčmář
(cherry pi
From: Paolo Bonzini
Introduce a new mutex to avoid an AB-BA deadlock between kvm->lock and
vcpu->mutex. Protect accesses in kvm_hv_setup_tsc_page too, as suggested
by Roman.
Reported-by: Dmitry Vyukov
Reviewed-by: Roman Kagan
Signed-off-by: Paolo Bonzini
(cherry picked from commit 3f5ad8be37
A few commits backported from mainline kernel related to hyperv
emulation: a feature to allow to accelerate hyperv device emulation in
QEMU, several prerequisite patches, and some bugfixes.
Dan Carpenter (1):
kvm: x86: hyperv: delete dead code in kvm_hv_hypercall()
Paolo Bonzini (2):
KVM: hyp
In Hyper-V, the fast guest->host notification mechanism is the
SIGNAL_EVENT hypercall, with a single parameter of the connection ID to
signal.
Currently this hypercall incurs a user exit and requires the userspace
to decode the parameters and trigger the notification of the potentially
different I
From: Vitaly Kuznetsov
Hyper-V 2016 on KVM with SynIC enabled doesn't boot with the following
trace:
kvm_entry:vcpu 0
kvm_exit: reason MSR_WRITE rip 0xf8000131c1e5 info 0 0
kvm_hv_synic_set_msr: vcpu_id 0 msr 0x4090 data 0x1 host 0
kvm_msr:
From: Paolo Bonzini
SRCU uses a delayed work item. Skip cleaning it up, and
the result is use-after-free in the work item callbacks.
Reported-by: Dmitry Vyukov
Suggested-by: Dmitry Vyukov
Cc: sta...@vger.kernel.org
Fixes: 0eb05bf290cfe8610d9680b49abef37febd1c38a
Reviewed-by: Xiao Guangrong
S