On 21/12/2016 18:50, Stephen Hemminger wrote: > The other problem with the hyperv headers is they were initially done with > only the Linux driver usage in mind. This made perfect sense at the time, > the problem is that they mix internal state with protocol definitions. Yes, and this was partly fixed when KVM started to use some of those definitions too (the implementation of Hyper-V protocols is split between kernel and userspace). > Lastly, there is licensing issues on headers. It would be good to have any > userspace ABI headers licensed with a more liberal license so that BSD and DPDK drivers > could use them directly. Right now each one reinvents. Other projects are using sanitized userspace ABI headers just fine, so this is something that lawyers should sort out before kernel hackers do. Paolo -- 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
