|
From: | Avi Kivity |
Subject: | [Qemu-devel] Re: [PATCH v2 14/17] kvm: x86: Introduce kvmclock device to save/restore its state |
Date: | Mon, 03 Jan 2011 18:04:53 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7 |
On 01/03/2011 10:33 AM, Jan Kiszka wrote:
From: Jan Kiszka<address@hidden> 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.
kvmclock is a per-cpu affair.
@@ -534,6 +599,10 @@ int kvm_arch_init(int smp_cpus) int ret; struct utsname utsname; +#ifdef KVM_CAP_ADJUST_CLOCK + sysbus_register_withprop(&kvmclock_info); +#endif +
So this doesn't look right. I think we're fine with just migrating the MSRs, like we migrate anything else that has to do with the cpu.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |