On Tue, Sep 16, 2014 at 05:42:16PM +0200, Paolo Bonzini wrote: > Il 16/09/2014 17:14, Marcelo Tosatti ha scritto: > > + /* > > + * Make sure that CPU state is synchronized from KVM > > + * once every VM state change callback has finished. > > Which other callback could affect the in-kernel state,
Do you want me to find out exactly which callback is changing the in-kernel interrupt state? To be honest: i don't know. > and should that call cpu_clean_all_dirty instead? Does not make sense: any callback which modifies any in-kernel register state should clean dirty state because its possibly set.
