freebsd-dev/sys/dev/vmware/vmci/vmci_event.h

/*-
 * Copyright (c) 2018 VMware, Inc.
 *
 * SPDX-License-Identifier: (BSD-2-Clause OR GPL-2.0)
 *
 * $FreeBSD$
 */

/* Event code for the vmci guest driver. */

#ifndef _VMCI_EVENT_H_
#define _VMCI_EVENT_H_

#include "vmci_call_defs.h"
#include "vmci_defs.h"

int	vmci_event_init(void);
void	vmci_event_exit(void);
void	vmci_event_sync(void);
int	vmci_event_dispatch(struct vmci_datagram *msg);
bool	vmci_event_check_host_capabilities(void);

#endif /* !_VMCI_EVENT_H_ */
Add VMCI (Virtual Machine Communication Interface) driver 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 2018-03-25 00:57:00 +00:00			`/*-`
Update VMCI license based on comments from core, the FreeBSD Foundation, 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 2018-04-08 01:32:56 +00:00			`* Copyright (c) 2018 VMware, Inc.`
Add VMCI (Virtual Machine Communication Interface) driver 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 2018-03-25 00:57:00 +00:00			`*`
Rectify VMCI SPDX license Approved by: Vishnu Dasa <vdasa@vmware.com> 2018-03-27 06:33:00 +00:00			`* SPDX-License-Identifier: (BSD-2-Clause OR GPL-2.0)`
Add VMCI (Virtual Machine Communication Interface) driver 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 2018-03-25 00:57:00 +00:00			`*`
			`* $FreeBSD$`
			`*/`

			`/* Event code for the vmci guest driver. */`

			`#ifndef _VMCI_EVENT_H_`
			`#define _VMCI_EVENT_H_`

			`#include "vmci_call_defs.h"`
			`#include "vmci_defs.h"`

			`int vmci_event_init(void);`
			`void vmci_event_exit(void);`
			`void vmci_event_sync(void);`
			`int vmci_event_dispatch(struct vmci_datagram *msg);`
			`bool vmci_event_check_host_capabilities(void);`

			`#endif /* !_VMCI_EVENT_H_ */`