Vitaly Kuznetsov 5aa9ef5e4b i386: use global kvm_state in hyperv_enabled() check ... There is no need to use vCPU-specific kvm state in hyperv_enabled() check and we need to do that when feature expansion happens early, before vCPU specific KVM state is created. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com> Message-Id: <20210422161130.652779-15-vkuznets@redhat.com> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>		2021-05-31 15:53:03 -04:00
..
hyperv-proto.h	i386: Make migration fail when Hyper-V reenlightenment was enabled but 'user_tsc_khz' is unset	2021-03-19 08:48:18 -04:00
hyperv-stub.c
hyperv.c
hyperv.h
kvm_i386.h
kvm-cpu.c	i386: Document when features can be added to kvm_default_props	2021-05-31 15:53:02 -04:00
kvm-cpu.h	i386: split cpu accelerators from cpu.c, using AccelCPUClass	2021-05-10 15:41:49 -04:00
kvm-stub.c
kvm.c	i386: use global kvm_state in hyperv_enabled() check	2021-05-31 15:53:03 -04:00
meson.build	i386: split cpu accelerators from cpu.c, using AccelCPUClass	2021-05-10 15:41:49 -04:00
trace-events
trace.h