On Tue, Oct 30, 2012 at 09:27:23AM -0700, Greg KH wrote: > On Tue, Oct 30, 2012 at 09:18:07AM -0700, Dmitry Torokhov wrote: > > > > I think that even if we had a special directory for vmci having network > > > > drivers in Dave's realm and pvscsi in James's is best option, so the new > > > > directory would contain vmci and the balloon driver (vsock will go into > > > > net/). Given that balloon is already in drivers/misc it looked like > > > > obvious place for VMCI as well. > > > > > > I agree that the individual drivers should go in the subsystem area, > > > it's this "hypervisor bus core" type code that I'm questioning. Right > > > now every hypervisor is putting that logic in a different place in the > > > kernel, having some consistency here would be nice. > > > > Hmm, I wonder if miscellaneous and core hypervisor drivers should end > > up in drivers/platform: > > > > drivers/platform/hyperv > > drivers/platform/olpc > > drivers/platform/vmware > > drivers/platform/xen > > drivers/platform/x86 > > That makes sense to me, nice. > > > But really we'd like to get VMCI into mainline first and move to a new > > place later if such a better place is found. > > Heh, no one wants to fight for something to help everyone out, they just > want their own code accepted :) No, this is more about finding a person who would be maintaining it and thus would review our code. For now we got you tagged and do not want to let go of you :P Or should we maintain our own stuff and have Linus pull it directly, like Xen guys appear to be doing? Really, moving it is not an issue for us. Thanks, Dmitry _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
