Jan Kiszka wrote:
What we could do is embed a kvm_context_t variable in the real KVMState,
and start using that. Then, we could, function by function, use the
upstream KVMState functionality and remove the corresponding
kvm_context_t functionality.
That would be great and was also what I had vaguely in mind. Likely
there are already fields that can be used from KVMState (fd and vmfd?).
Obvious candidates are to start using kvm_*_ioctl() everywhere.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
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
