virtio_config.h 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. #ifndef _UAPI_LINUX_VIRTIO_CONFIG_H
  2. #define _UAPI_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. * Redistribution and use in source and binary forms, with or without
  7. * modification, are permitted provided that the following conditions
  8. * are met:
  9. * 1. Redistributions of source code must retain the above copyright
  10. * notice, this list of conditions and the following disclaimer.
  11. * 2. Redistributions in binary form must reproduce the above copyright
  12. * notice, this list of conditions and the following disclaimer in the
  13. * documentation and/or other materials provided with the distribution.
  14. * 3. Neither the name of IBM nor the names of its contributors
  15. * may be used to endorse or promote products derived from this software
  16. * without specific prior written permission.
  17. * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND
  18. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  19. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  20. * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE
  21. * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  22. * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  23. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  24. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  25. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  26. * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  27. * SUCH DAMAGE. */
  28. /* Virtio devices use a standardized configuration space to define their
  29. * features and pass configuration information, but each implementation can
  30. * store and access that space differently. */
  31. #include <linux/types.h>
  32. /* Status byte for guest to report progress, and synchronize features. */
  33. /* We have seen device and processed generic fields (VIRTIO_CONFIG_F_VIRTIO) */
  34. #define VIRTIO_CONFIG_S_ACKNOWLEDGE 1
  35. /* We have found a driver for the device. */
  36. #define VIRTIO_CONFIG_S_DRIVER 2
  37. /* Driver has used its parts of the config, and is happy */
  38. #define VIRTIO_CONFIG_S_DRIVER_OK 4
  39. /* Driver has finished configuring features */
  40. #define VIRTIO_CONFIG_S_FEATURES_OK 8
  41. /* Device entered invalid state, driver must reset it */
  42. #define VIRTIO_CONFIG_S_NEEDS_RESET 0x40
  43. /* We've given up on this device. */
  44. #define VIRTIO_CONFIG_S_FAILED 0x80
  45. /*
  46. * Virtio feature bits VIRTIO_TRANSPORT_F_START through
  47. * VIRTIO_TRANSPORT_F_END are reserved for the transport
  48. * being used (e.g. virtio_ring, virtio_pci etc.), the
  49. * rest are per-device feature bits.
  50. */
  51. #define VIRTIO_TRANSPORT_F_START 28
  52. #define VIRTIO_TRANSPORT_F_END 41
  53. #ifndef VIRTIO_CONFIG_NO_LEGACY
  54. /* Do we get callbacks when the ring is completely used, even if we've
  55. * suppressed them? */
  56. #define VIRTIO_F_NOTIFY_ON_EMPTY 24
  57. /* Can the device handle any descriptor layout? */
  58. #define VIRTIO_F_ANY_LAYOUT 27
  59. #endif /* VIRTIO_CONFIG_NO_LEGACY */
  60. /* v1.0 compliant. */
  61. #define VIRTIO_F_VERSION_1 32
  62. /*
  63. * If clear - device has the platform DMA (e.g. IOMMU) bypass quirk feature.
  64. * If set - use platform DMA tools to access the memory.
  65. *
  66. * Note the reverse polarity (compared to most other features),
  67. * this is for compatibility with legacy systems.
  68. */
  69. #define VIRTIO_F_ACCESS_PLATFORM 33
  70. #ifndef __KERNEL__
  71. /* Legacy name for VIRTIO_F_ACCESS_PLATFORM (for compatibility with old userspace) */
  72. #define VIRTIO_F_IOMMU_PLATFORM VIRTIO_F_ACCESS_PLATFORM
  73. #endif /* __KERNEL__ */
  74. /* This feature indicates support for the packed virtqueue layout. */
  75. #define VIRTIO_F_RING_PACKED 34
  76. /*
  77. * Inorder feature indicates that all buffers are used by the device
  78. * in the same order in which they have been made available.
  79. */
  80. #define VIRTIO_F_IN_ORDER 35
  81. /*
  82. * This feature indicates that memory accesses by the driver and the
  83. * device are ordered in a way described by the platform.
  84. */
  85. #define VIRTIO_F_ORDER_PLATFORM 36
  86. /*
  87. * Does the device support Single Root I/O Virtualization?
  88. */
  89. #define VIRTIO_F_SR_IOV 37
  90. /*
  91. * This feature indicates that the driver can reset a queue individually.
  92. */
  93. #define VIRTIO_F_RING_RESET 40
  94. #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */