Gleb Natapov <gleb@xxxxxxxxxx> wrote: > On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote: > > Gleb Natapov <gleb@xxxxxxxxxx> wrote: > > > > Of course, you should also take a look at VMware's VMCI. If we're going > > > > to have a socket interface, if we can have a compatible userspace > > > > interface, that would probably be a good thing. > > > > > > I looked at what I could find about VMCI (http://pubs.vmware.com/vmci-sdk/index.html). > > > I believe Anthony intended for you to look at the sockets interface to > > VMCI: http://www.vmware.com/pdf/ws65_s2_vmci_sockets.pdf. > > > Thanks for the link! Are you going to push this interface into upstream kernel? Pushing it upstream is definitely something we want to do, since it will make our development easier and allow us to clean up some unnecessary code in the module. That said, before we can start that effort we have some issues to resolve internally (for example, getting our upgrade story straight in this model and ensuring our infrastructure / installer can handle it) so we don't have an estimate for when this will happen just yet. There are people here whose jobs are to resolve these things and they are working on it, so I am confident this will happen even if slower than we'd all like. > > The link you referenced was experimental and is actually now > > deprecated in favor of the sockets interface. > You should influence google somehow to drop old link. That the first > search result for "vmci vmware" ;) You know, we talked a while ago about putting a notice at the top of that page stating what I said and redirecting to the VMCI Sockets programming guide, but somehow that seems to have not gotten done. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
