05 Jun, 2019

1 commit

• 685a6bf84   treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 321 ... Browse Code »

  Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license as published by
  the free software foundation version 2 and no later version this
  program is distributed in the hope that it will be useful but
  without any warranty without even the implied warranty of
  merchantability or fitness for a particular purpose see the gnu
  general public license for more details

  extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

  has been chosen to replace the boilerplate/reference in 33 file(s).

  Signed-off-by: Thomas Gleixner
  Reviewed-by: Kate Stewart
  Reviewed-by: Alexios Zavras
  Reviewed-by: Allison Randal
  Cc: linux-spdx@vger.kernel.org
  Link: https://lkml.kernel.org/r/20190530000435.345978407@linutronix.de
  Signed-off-by: Greg Kroah-Hartman

  Thomas Gleixner

  2019-06-05 23:37:05 +0800  

28 Jul, 2013

1 commit

• 82a54d0eb   VSOCK: Move af_vsock.h and vsock_addr.h to include/net ... Browse Code »

  This is useful for other VSOCK transport implemented outside the
  net/vmw_vsock/ directory to use these headers.

  Signed-off-by: Asias He
  Acked-by: Andy King
  Signed-off-by: David S. Miller

  Asias He

  2013-07-28 13:14:06 +0800  

03 Apr, 2013

1 commit

• 990454b5a   VSOCK: Handle changes to the VMCI context ID. ... Browse Code »

  The VMCI context ID of a virtual machine may change at any time. There
  is a VMCI event which signals this but datagrams may be processed before
  this is handled. It is therefore necessary to be flexible about the
  destination context ID of any datagrams received. (It can be assumed to
  be correct because it is provided by the hypervisor.) The context ID on
  existing sockets should be updated to reflect how the hypervisor is
  currently referring to the system.

  Signed-off-by: Reilly Grant
  Acked-by: Andy King
  Signed-off-by: David S. Miller

  Reilly Grant

  2013-04-03 02:39:17 +0800  

11 Feb, 2013

1 commit

• d021c3440   VSOCK: Introduce VM Sockets ... Browse Code »

  VM Sockets allows communication between virtual machines and the hypervisor.
  User level applications both in a virtual machine and on the host can use the
  VM Sockets API, which facilitates fast and efficient communication between
  guest virtual machines and their host. A socket address family, designed to be
  compatible with UDP and TCP at the interface level, is provided.

  Today, VM Sockets is used by various VMware Tools components inside the guest
  for zero-config, network-less access to VMware host services. In addition to
  this, VMware's users are using VM Sockets for various applications, where
  network access of the virtual machine is restricted or non-existent. Examples
  of this are VMs communicating with device proxies for proprietary hardware
  running as host applications and automated testing of applications running
  within virtual machines.

  The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
  socket interface. The VM Sockets module supports both connection-oriented
  stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
  Sockets protocol family is defined as "AF_VSOCK" and the socket operations
  split for SOCK_DGRAM and SOCK_STREAM.

  For additional information about the use of VM Sockets, please refer to the
  VM Sockets Programming Guide available at:

  https://www.vmware.com/support/developer/vmci-sdk/

  Signed-off-by: George Zhang
  Signed-off-by: Dmitry Torokhov
  Signed-off-by: Andy king
  Signed-off-by: David S. Miller

  Andy King

  2013-02-11 08:41:08 +0800