1#ifndef _LINUX_VIRTIO_CONFIG_H 2#define _LINUX_VIRTIO_CONFIG_H 3/* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so 4 * anyone can use the definitions to implement compatible drivers/servers. */ 5 6/* Virtio devices use a standardized configuration space to define their 7 * features and pass configuration information, but each implementation can 8 * store and access that space differently. */ 9#include <linux/types.h> 10 11/* Status byte for guest to report progress, and synchronize features. */ 12/* We have seen device and processed generic fields (VIRTIO_CONFIG_F_VIRTIO) */ 13#define VIRTIO_CONFIG_S_ACKNOWLEDGE 1 14/* We have found a driver for the device. */ 15#define VIRTIO_CONFIG_S_DRIVER 2 16/* Driver has used its parts of the config, and is happy */ 17#define VIRTIO_CONFIG_S_DRIVER_OK 4 18/* We've given up on this device. */ 19#define VIRTIO_CONFIG_S_FAILED 0x80 20 21/* Some virtio feature bits (currently bits 28 through 31) are reserved for the 22 * transport being used (eg. virtio_ring), the rest are per-device feature 23 * bits. */ 24#define VIRTIO_TRANSPORT_F_START 28 25#define VIRTIO_TRANSPORT_F_END 32 26 27/* Do we get callbacks when the ring is completely used, even if we've 28 * suppressed them? */ 29#define VIRTIO_F_NOTIFY_ON_EMPTY 24 30 31#endif /* _LINUX_VIRTIO_CONFIG_H */ 32