virtio_ring.h 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. #ifndef _UAPI_LINUX_VIRTIO_RING_H
  2. #define _UAPI_LINUX_VIRTIO_RING_H
  3. /* An interface for efficient virtio implementation, currently for use by KVM
  4. * and lguest, but hopefully others soon. Do NOT change this since it will
  5. * break existing servers and clients.
  6. *
  7. * This header is BSD licensed so anyone can use the definitions to implement
  8. * compatible drivers/servers.
  9. *
  10. * Redistribution and use in source and binary forms, with or without
  11. * modification, are permitted provided that the following conditions
  12. * are met:
  13. * 1. Redistributions of source code must retain the above copyright
  14. * notice, this list of conditions and the following disclaimer.
  15. * 2. Redistributions in binary form must reproduce the above copyright
  16. * notice, this list of conditions and the following disclaimer in the
  17. * documentation and/or other materials provided with the distribution.
  18. * 3. Neither the name of IBM nor the names of its contributors
  19. * may be used to endorse or promote products derived from this software
  20. * without specific prior written permission.
  21. * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND
  22. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  23. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  24. * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE
  25. * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  26. * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  27. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  28. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  29. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  30. * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  31. * SUCH DAMAGE.
  32. *
  33. * Copyright Rusty Russell IBM Corporation 2007. */
  34. #ifndef __KERNEL__
  35. #include <stdint.h>
  36. #endif
  37. #include <linux/types.h>
  38. #include <linux/virtio_types.h>
  39. /* This marks a buffer as continuing via the next field. */
  40. #define VRING_DESC_F_NEXT 1
  41. /* This marks a buffer as write-only (otherwise read-only). */
  42. #define VRING_DESC_F_WRITE 2
  43. /* This means the buffer contains a list of buffer descriptors. */
  44. #define VRING_DESC_F_INDIRECT 4
  45. /* The Host uses this in used->flags to advise the Guest: don't kick me when
  46. * you add a buffer. It's unreliable, so it's simply an optimization. Guest
  47. * will still kick if it's out of buffers. */
  48. #define VRING_USED_F_NO_NOTIFY 1
  49. /* The Guest uses this in avail->flags to advise the Host: don't interrupt me
  50. * when you consume a buffer. It's unreliable, so it's simply an
  51. * optimization. */
  52. #define VRING_AVAIL_F_NO_INTERRUPT 1
  53. /* We support indirect buffer descriptors */
  54. #define VIRTIO_RING_F_INDIRECT_DESC 28
  55. /* The Guest publishes the used index for which it expects an interrupt
  56. * at the end of the avail ring. Host should ignore the avail->flags field. */
  57. /* The Host publishes the avail index for which it expects a kick
  58. * at the end of the used ring. Guest should ignore the used->flags field. */
  59. #define VIRTIO_RING_F_EVENT_IDX 29
  60. /* Virtio ring descriptors: 16 bytes. These can chain together via "next". */
  61. struct vring_desc {
  62. /* Address (guest-physical). */
  63. __virtio64 addr;
  64. /* Length. */
  65. __virtio32 len;
  66. /* The flags as indicated above. */
  67. __virtio16 flags;
  68. /* We chain unused descriptors via this, too */
  69. __virtio16 next;
  70. };
  71. struct vring_avail {
  72. __virtio16 flags;
  73. __virtio16 idx;
  74. __virtio16 ring[];
  75. };
  76. /* u32 is used here for ids for padding reasons. */
  77. struct vring_used_elem {
  78. /* Index of start of used descriptor chain. */
  79. __virtio32 id;
  80. /* Total length of the descriptor chain which was used (written to) */
  81. __virtio32 len;
  82. };
  83. struct vring_used {
  84. __virtio16 flags;
  85. __virtio16 idx;
  86. struct vring_used_elem ring[];
  87. };
  88. struct vring {
  89. unsigned int num;
  90. struct vring_desc *desc;
  91. struct vring_avail *avail;
  92. struct vring_used *used;
  93. };
  94. /* Alignment requirements for vring elements.
  95. * When using pre-virtio 1.0 layout, these fall out naturally.
  96. */
  97. #define VRING_AVAIL_ALIGN_SIZE 2
  98. #define VRING_USED_ALIGN_SIZE 4
  99. #define VRING_DESC_ALIGN_SIZE 16
  100. /* The standard layout for the ring is a continuous chunk of memory which looks
  101. * like this. We assume num is a power of 2.
  102. *
  103. * struct vring
  104. * {
  105. * // The actual descriptors (16 bytes each)
  106. * struct vring_desc desc[num];
  107. *
  108. * // A ring of available descriptor heads with free-running index.
  109. * __virtio16 avail_flags;
  110. * __virtio16 avail_idx;
  111. * __virtio16 available[num];
  112. * __virtio16 used_event_idx;
  113. *
  114. * // Padding to the next align boundary.
  115. * char pad[];
  116. *
  117. * // A ring of used descriptor heads with free-running index.
  118. * __virtio16 used_flags;
  119. * __virtio16 used_idx;
  120. * struct vring_used_elem used[num];
  121. * __virtio16 avail_event_idx;
  122. * };
  123. */
  124. /* We publish the used event index at the end of the available ring, and vice
  125. * versa. They are at the end for backwards compatibility. */
  126. #define vring_used_event(vr) ((vr)->avail->ring[(vr)->num])
  127. #define vring_avail_event(vr) (*(__virtio16 *)&(vr)->used->ring[(vr)->num])
  128. static inline void vring_init(struct vring *vr, unsigned int num, void *p,
  129. unsigned long align)
  130. {
  131. vr->num = num;
  132. vr->desc = p;
  133. vr->avail = p + num*sizeof(struct vring_desc);
  134. vr->used = (void *)(((uintptr_t)&vr->avail->ring[num] + sizeof(__virtio16)
  135. + align-1) & ~(align - 1));
  136. }
  137. static inline unsigned vring_size(unsigned int num, unsigned long align)
  138. {
  139. return ((sizeof(struct vring_desc) * num + sizeof(__virtio16) * (3 + num)
  140. + align - 1) & ~(align - 1))
  141. + sizeof(__virtio16) * 3 + sizeof(struct vring_used_elem) * num;
  142. }
  143. /* The following is used with USED_EVENT_IDX and AVAIL_EVENT_IDX */
  144. /* Assuming a given event_idx value from the other side, if
  145. * we have just incremented index from old to new_idx,
  146. * should we trigger an event? */
  147. static inline int vring_need_event(__u16 event_idx, __u16 new_idx, __u16 old)
  148. {
  149. /* Note: Xen has similar logic for notification hold-off
  150. * in include/xen/interface/io/ring.h with req_event and req_prod
  151. * corresponding to event_idx + 1 and new_idx respectively.
  152. * Note also that req_event and req_prod in Xen start at 1,
  153. * event indexes in virtio start at 0. */
  154. return (__u16)(new_idx - event_idx - 1) < (__u16)(new_idx - old);
  155. }
  156. #endif /* _UAPI_LINUX_VIRTIO_RING_H */