From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH 1/1] VSOCK: Introduce VM Sockets Date: Tue, 12 Feb 2013 11:58:11 +0100 Message-ID: <511A2043.6040805@redhat.com> References: <1360196636-9357-1-git-send-email-acking@vmware.com> <1360196636-9357-2-git-send-email-acking@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: pv-drivers@vmware.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, gregkh@linuxfoundation.org, davem@davemloft.net To: Andy King Return-path: In-Reply-To: <1360196636-9357-2-git-send-email-acking@vmware.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org On 02/07/13 01:23, Andy King wrote: Hi, > +/* Option name for socket's service label. Use as the option name in > + * setsockopt(3) or getsockopt(3) to set or get the service label for a socket. > + * The service label is a C-style NUL-terminated string. Only available for > + * hypervisor endpoints. > + */ > + > +#define SO_VM_SOCKETS_SERVICE_LABEL 4 > + What is this and how does it work? cheers, Gerd