Re: [Qemu-devel] [PATCH 00/21] Kemari for KVM 0.2

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

 



> >> Could you formulate the constraints so developers are aware of them in
> >> the future and can protect the codebase.  How about expanding the
> >> Kemari wiki pages?
> > 
> > If you like the idea above, I'm happy to make the list also on
> > the wiki page.
> 
> Here's a different question: what requirements must an emulated device
> meet in order to be added to the Kemari supported whitelist?  That's
> what I want to know so that I don't break existing devices and can add
> new devices that work with Kemari :).

Why isn't it completely device agnostic? i.e. if a device has to care about 
Kemari at all (of vice-versa) then IMO you're doing it wrong. The whole point 
of the internal block/net APIs is that they isolate the host implementation 
details from the device emulation.

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