> From: Dexuan Cui
> Sent: Wednesday, August 16, 2017 15:34
> > From: Jorgen S. Hansen [mailto:jhan...@vmware.com]
> > > Without the patch, vmw_vsock_vmci_transport.ko and vmw_vmci.ko can
> > > automatically load when an application creates an AF_VSOCK socket.
> > >
> > > This is the expected good
> From: Jorgen S. Hansen [mailto:jhan...@vmware.com]
> > Without the patch, vmw_vsock_vmci_transport.ko and vmw_vmci.ko can
> > automatically load when an application creates an AF_VSOCK socket.
> >
> > This is the expected good behavior on VMware hypervisor, but as we
> > are going to add hv_sock.
> On Aug 16, 2017, at 12:13 AM, Dexuan Cui wrote:
>
>
> Without the patch, vmw_vsock_vmci_transport.ko and vmw_vmci.ko can
> automatically load when an application creates an AF_VSOCK socket.
>
> This is the expected good behavior on VMware hypervisor, but as we
> are going to add hv_sock.ko (
From: Dexuan Cui
Date: Wed, 16 Aug 2017 18:51:36 +
> It looks typically modern Linux distros have CONFIG_HYPERVISOR_GUEST=y
> by default
It doesn't matter what any distribution does or does not do.
People are going to do 'randconfig' builds over thousands and
thousands of configuration comb
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Wednesday, August 16, 2017 11:07
>
> From: Dexuan Cui
> Date: Tue, 15 Aug 2017 22:13:29 +
>
> > + /*
> > +* Check if we are running on VMware's hypervisor and bail out
> > +* if we are not.
> > +*/
> > + if (x86_hyper
From: Dexuan Cui
Date: Tue, 15 Aug 2017 22:13:29 +
> + /*
> + * Check if we are running on VMware's hypervisor and bail out
> + * if we are not.
> + */
> + if (x86_hyper != &x86_hyper_vmware)
> + return -ENODEV;
This symbol is only available when CONFIG_HYP
Without the patch, vmw_vsock_vmci_transport.ko and vmw_vmci.ko can
automatically load when an application creates an AF_VSOCK socket.
This is the expected good behavior on VMware hypervisor, but as we
are going to add hv_sock.ko (i.e. Hyper-V transport for AF_VSOCK), we
should make sure vmw_vsock
