Re: [PATCH 1/1] VSOCK: Introduce VM Sockets
From: Gerd Hoffmann
Date: Fri Feb 15 2013 - 05:32:49 EST
On 02/07/13 01:23, Andy King wrote:
> +/* Use this as the destination CID in an address when referring to the
> + * hypervisor. VMCI relies on it being 0, but this would be useful for other
> + * transports too.
> + */
> +#define VMADDR_CID_HYPERVISOR 0
> +/* This CID is specific to VMCI and can be considered reserved (even VMCI
> + * doesn't use it anymore, it's a legacy value from an older release).
> + */
> +#define VMADDR_CID_RESERVED 1
> +/* Use this as the destination CID in an address when referring to the host
> + * (any process other than the hypervisor). VMCI relies on it being 2, but
> + * this would be useful for other transports too.
> + */
> +#define VMADDR_CID_HOST 2
CIDs larger than 2 will address other VMs on the same host, with the
hypervisor forwarding the data from one guest to the other and back?
How does VMADDR_CID_HOST work? Given the age of the vsock transport
layer I don't think you have a vsock_transport_host.ko module ...
Is there some registry for the port numbers?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/