Am 16.11.2009 um 18:00 schrieb Jan Kiszka <jan.kiszka@xxxxxxxxxxx>:
This patch aims at addressing the mp_state writeback issue in a
cleaner
fashion. By introducing additional information about the scope of the
scheduled vcpu state writeback, we can simply skin mp_state (and maybe
other specific states in the future) when updating the in-kernel
state.
The writeback scope is defined when calling cpu_synchronize_state. It
accumulated, ie. once a full writeback was requested, this will stick
until it was performed.
This unbreaks --disable-kvm builds of qemu-kvm again.
Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
---
A corresponding upstream patch is ready to be posted as well, just
waiting for comments on the general direction from KVM POV.
I think I'd rather have a sync function that implicitly does the
RUNTIME sync, the way it is now, and an 'advanced' one you can pass a
constant what it syncs.
That way most code continues to work the way it is now. It also makes
it easier readable IMHO.
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
