On 01/11/2011 05:12 PM, Anthony Liguori wrote:
No, it really doesn't :-) Cirrus VGA and std VGA share a lot of
code. But that doesn't mean that we treat them as one device.
Cirrus and VGA really are separate devices. They share code because
on evolved from the other, and is backwards compatible with the
other. i8254 and i8254-kvm did not evolve from each other,
Actually, they did, but that's besides the point.
The code did, the devices did not.
Why not? Whatever state the kernel keeps, we expose to userspace and
allow sending it over the wire.
What exactly is the scenario you're concerned about?
Migration between userspace HPET and in-kernel HPET?
Yes. To a lesser extent, a client doing 'info hpet' or similar and
failing for kernel hpet.
One thing I've been considering is essentially migration filters. It
would be a set of rules that essentially were "hpet-kvm.* = hpet.*"
which would allow migration from hpet to hpet-kvm given a translation
of state. I think this sort of higher level ruleset would make it
easier to support migration between versions of the device model.
Of course, that only gives you a forward path. It doesn't give you a
backwards path.
It would be easier to have them use the same device id in the first place.
If it looks like an i8254, quacks like an i8254, and live migrates like
an i8254, it's probably an i8254.
--
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
