Reilly Grant 2a89f9247a VSOCK: Support VM sockets connected to the hypervisor. ...

The resource ID used for VM socket control packets (0) is already
used for the VMCI_GET_CONTEXT_ID hypercall so a new ID (15) must be
used when the guest sends these datagrams to the hypervisor.

The hypervisor context ID must also be removed from the internal
blacklist.

Signed-off-by: Reilly Grant <grantr@vmware.com>
Acked-by: Andy King <acking@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

2013-03-15 08:26:26 -04:00

..

af_vsock.c

VSOCK: Don't reject PF_VSOCK protocol

2013-02-18 15:02:51 -05:00

af_vsock.h

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

Kconfig

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

Makefile

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

vmci_transport_notify_qstate.c

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

vmci_transport_notify.c

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

vmci_transport_notify.h

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

vmci_transport.c

VSOCK: Support VM sockets connected to the hypervisor.

2013-03-15 08:26:26 -04:00

vmci_transport.h

VSOCK: Support VM sockets connected to the hypervisor.

2013-03-15 08:26:26 -04:00

vsock_addr.c

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00

vsock_addr.h

VSOCK: Introduce VM Sockets

2013-02-10 19:41:08 -05:00