Re: [PATCH] use KVMState, as upstream do

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Glauber Costa wrote:
This is a pretty mechanical change. To make code look
closer to upstream qemu, I'm renaming kvm_context_t to
KVMState. Mid term goal here is to start sharing code
whereas possible.

Doesn't apply.

Also, it's a little fishy. We now have two KVMState types, but they're pretty different.

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.

Avi, please apply, or I'll send you a video of myself
dancing naked.

The list has a size limit, so don't attach a huge video. Post a URL instead.

--
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

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux