#ifndef _UAPI_LINUX_VIRTIO_CONFIG_H #define _UAPI_LINUX_VIRTIO_CONFIG_H /* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so * anyone can use the definitions to implement compatible drivers/servers. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Neither the name of IBM nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ /* Virtio devices use a standardized configuration space to define their * features and pass configuration information, but each implementation can * store and access that space differently. */ #include <linux/types.h> /* Status byte for guest to report progress, and synchronize features. */ /* We have seen device and processed generic fields (VIRTIO_CONFIG_F_VIRTIO) */ #define VIRTIO_CONFIG_S_ACKNOWLEDGE … /* We have found a driver for the device. */ #define VIRTIO_CONFIG_S_DRIVER … /* Driver has used its parts of the config, and is happy */ #define VIRTIO_CONFIG_S_DRIVER_OK … /* Driver has finished configuring features */ #define VIRTIO_CONFIG_S_FEATURES_OK … /* Device entered invalid state, driver must reset it */ #define VIRTIO_CONFIG_S_NEEDS_RESET … /* We've given up on this device. */ #define VIRTIO_CONFIG_S_FAILED … /* * Virtio feature bits VIRTIO_TRANSPORT_F_START through * VIRTIO_TRANSPORT_F_END are reserved for the transport * being used (e.g. virtio_ring, virtio_pci etc.), the * rest are per-device feature bits. */ #define VIRTIO_TRANSPORT_F_START … #define VIRTIO_TRANSPORT_F_END … #ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've * suppressed them? */ #define VIRTIO_F_NOTIFY_ON_EMPTY … /* Can the device handle any descriptor layout? */ #define VIRTIO_F_ANY_LAYOUT … #endif /* VIRTIO_CONFIG_NO_LEGACY */ /* v1.0 compliant. */ #define VIRTIO_F_VERSION_1 … /* * If clear - device has the platform DMA (e.g. IOMMU) bypass quirk feature. * If set - use platform DMA tools to access the memory. * * Note the reverse polarity (compared to most other features), * this is for compatibility with legacy systems. */ #define VIRTIO_F_ACCESS_PLATFORM … #ifndef __KERNEL__ /* Legacy name for VIRTIO_F_ACCESS_PLATFORM (for compatibility with old userspace) */ #define VIRTIO_F_IOMMU_PLATFORM … #endif /* __KERNEL__ */ /* This feature indicates support for the packed virtqueue layout. */ #define VIRTIO_F_RING_PACKED … /* * Inorder feature indicates that all buffers are used by the device * in the same order in which they have been made available. */ #define VIRTIO_F_IN_ORDER … /* * This feature indicates that memory accesses by the driver and the * device are ordered in a way described by the platform. */ #define VIRTIO_F_ORDER_PLATFORM … /* * Does the device support Single Root I/O Virtualization? */ #define VIRTIO_F_SR_IOV … /* * This feature indicates that the driver passes extra data (besides * identifying the virtqueue) in its device notifications. */ #define VIRTIO_F_NOTIFICATION_DATA … /* This feature indicates that the driver uses the data provided by the device * as a virtqueue identifier in available buffer notifications. */ #define VIRTIO_F_NOTIF_CONFIG_DATA … /* * This feature indicates that the driver can reset a queue individually. */ #define VIRTIO_F_RING_RESET … /* * This feature indicates that the device support administration virtqueues. */ #define VIRTIO_F_ADMIN_VQ … #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */
Codebase Browser
linux