Il 04/08/2014 18:30, Marcin Gibuła ha scritto: > > > is this analysis deep enough for you? I don't know if that can be fixed > with existing api as cpu_synchronize_all_states() is all or nothing kind > of stuff. > > Kvmclock needs it only to read current cpu registers, so syncing > everything is not really necessary. Perhaps exporting one of > kvm_arch_get_* would be enough. And it wouldn't mess with lazy get/put. > > On the other hand, if in future any other driver adds > cpu_synchronize_all_states() in its change state callback it could > result in same error so perhaps more generic approach is needed.
Yeah, I need to sit down and look at the code more closely... Perhaps a cpu_mark_all_dirty() is enough. Paolo
