Vitaly Kuznetsov 8700a98443 target/i386: always create kvmclock device ... QEMU's kvmclock device is only created when KVM PV feature bits for kvmclock (KVM_FEATURE_CLOCKSOURCE/KVM_FEATURE_CLOCKSOURCE2) are exposed to the guest. With 'kvm=off' cpu flag the device is not created and we don't call KVM_GET_CLOCK/KVM_SET_CLOCK upon migration. It was reported that without these call at least Hyper-V TSC page clocksouce (which can be enabled independently) gets broken after migration. Switch to creating kvmclock QEMU device unconditionally, it seems to always make sense to call KVM_GET_CLOCK/KVM_SET_CLOCK on migration. Use KVM_CAP_ADJUST_CLOCK check instead of CPUID feature bits. Reported-by: Antoine Damhet <antoine.damhet@blade-group.com> Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Message-Id: <20200922151934.899555-1-vkuznets@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2020-09-30 19:11:36 +02:00
..
9pfs
acpi
adc
alpha
arm
audio
avr
block
char	hw/char/serial-{isa, pci}: Alias QDEV properties from generic serial object	2020-09-30 19:09:20 +02:00
core	numa: remove fixup numa_state->num_nodes to MAX_NODES	2020-09-30 19:09:20 +02:00
cpu
cris
display
dma
gpio
hppa
hyperv
i2c
i386	target/i386: always create kvmclock device	2020-09-30 19:11:36 +02:00
ide
input
intc
ipack
ipmi
isa
lm32
m68k
mem
microblaze
mips	hw/mips/mipssim: Use MMIO serial device on fake ISA I/O	2020-09-30 19:09:20 +02:00
misc
moxie
net
nios2
nubus
nvram
openrisc
pci
pci-bridge
pci-host
pcmcia
ppc	numa: drop support for '-numa node' (without memory specified)	2020-09-30 19:09:20 +02:00
rdma
riscv
rtc
rx
s390x
scsi	hw: megasas: consider 'iov_count=0' is an error in megasas_map_sgl	2020-09-30 19:09:20 +02:00
sd
semihosting
sh4
smbios
sparc
sparc64
ssi
timer
tpm
tricore
unicore32
usb
vfio
virtio
watchdog
xen
xenpv
xtensa
Kconfig
meson.build