aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/vmware/vmci/vmci_kernel_api_1.h
Commit message (Collapse)AuthorAgeFilesLines
* sys: Remove $FreeBSD$: two-line .h patternWarner Losh2023-08-161-2/+0
| | | | Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
* Update VMCI license based on comments from core, the FreeBSD Foundation,Mark Peek2018-04-081-1/+1
| | | | | | | | | | | | | | and VMware legal: - Add a dual BSD-2 Clause/GPLv2 LICENSE file in the VMCI directory - Remove the use of "All Rights Reserved" - Per best practice, remove copyright/license info from Makefile Reviewed by: imp, emaste, jhb, Vishnu Dasa <vdasa@vmware.com> Approved by: VMware legal via Mark Peek <markpeek@vmware.com> Differential Revision: https://reviews.freebsd.org/D14979 Notes: svn path=/head/; revision=332263
* Rectify VMCI SPDX licenseMark Peek2018-03-271-1/+1
| | | | | | | Approved by: Vishnu Dasa <vdasa@vmware.com> Notes: svn path=/head/; revision=331609
* Add VMCI (Virtual Machine Communication Interface) driverMark Peek2018-03-251-0/+71
In a virtual machine, VMCI is exposed as a regular PCI device. The primary communication mechanisms supported are a point-to-point bidirectional transport based on a pair of memory-mapped queues, and asynchronous notifications in the form of datagrams and doorbells. These features are available to kernel level components such as vSockets through the VMCI kernel API. In addition to this, the VMCI kernel API provides support for receiving events related to the state of the VMCI communication channels, and the virtual machine itself. Submitted by: Vishnu Dasa <vdasa@vmware.com> Reviewed by: bcr, imp Obtained from: VMware Differential Revision: https://reviews.freebsd.org/D14289 Notes: svn path=/head/; revision=331510