search for: _uapi_linux_virtio_config_h

...@@ -71,4 +71,10 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * If clear - driver may use barriers suitable for CPU cores. + * If set - driver must use barriers suitable for hardware devices. + */ +#define VIRTIO_F_IO_BARRIER 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.11.0

...@@ -71,4 +71,10 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * If clear - driver may use barriers suitable for CPU cores. + * If set - driver must use barriers suitable for hardware devices. + */ +#define VIRTIO_F_IO_BARRIER 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.11.0

...config.h index b7cda39..4b5da48 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -51,4 +51,7 @@ * suppressed them? */ #define VIRTIO_F_NOTIFY_ON_EMPTY 24 +/* Can the device handle any descriptor layout? */ +#define VIRTIO_F_ANY_LAYOUT 30 + #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */

...config.h index b7cda39..4b5da48 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -51,4 +51,7 @@ * suppressed them? */ #define VIRTIO_F_NOTIFY_ON_EMPTY 24 +/* Can the device handle any descriptor layout? */ +#define VIRTIO_F_ANY_LAYOUT 30 + #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */

...gt; #define VIRTIO_F_IOMMU_PLATFORM 33 > > + > > +/* > > + * If clear - driver may use barriers suitable for CPU cores. > > + * If set - driver must use barriers suitable for hardware devices. > > + */ > > +#define VIRTIO_F_IO_BARRIER 37 > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > Hi: > > I believe this depends on Michael's patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher...

...gt; #define VIRTIO_F_IOMMU_PLATFORM 33 > > + > > +/* > > + * If clear - driver may use barriers suitable for CPU cores. > > + * If set - driver must use barriers suitable for hardware devices. > > + */ > > +#define VIRTIO_F_IO_BARRIER 37 > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > Hi: > > I believe this depends on Michael's patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher...

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

...t; > > +/* > > > > + * If clear - driver may use barriers suitable for CPU cores. > > > > + * If set - driver must use barriers suitable for hardware devices. > > > > + */ > > > > +#define VIRTIO_F_IO_BARRIER 37 > > > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > > Hi: > > > > > > I believe this depends on Michael's patch of > > > > > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > > > > > ? > > > > > > Thanks > > We already have...

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

...ch they have been made available. >+ */ >+#define VIRTIO_F_IN_ORDER 35 >+ >+/* >+ * This feature indicates that drivers pass extra data (besides >+ * identifying the Virtqueue) in their device notifications. >+ */ >+#define VIRTIO_F_NOTIFICATION_DATA 36 >+ > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ >diff --git a/include/uapi/linux/virtio_ring.h b/include/uapi/linux/virtio_ring.h >index 6d5d5faa989b..77b1d4aeef72 100644 >--- a/include/uapi/linux/virtio_ring.h >+++ b/include/uapi/linux/virtio_ring.h >@@ -44,6 +44,9 @@ > /* This means the buffer contains a list of buffer des...

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

.../* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,9 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * Does the device support Single Root I/O Virtualization? + */ +#define VIRTIO_F_SR_IOV 37 #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ -- 2.17.0

...9 @@ > > * this is for compatibility with legacy systems. > > */ > > #define VIRTIO_F_IOMMU_PLATFORM 33 > > + > > +/* > > + * Does the device support Single Root I/O Virtualization? > > + */ > > +#define VIRTIO_F_SR_IOV 37 > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > -- > > 2.17.0 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: virtio-dev-unsubscribe at lists.oasis-open.org > For additional commands, e-mail: virtio-dev-help at lists.oasis-open.org >

...> */ > > > > #define VIRTIO_F_IOMMU_PLATFORM 33 > > > > + > > > > +/* > > > > + * Does the device support Single Root I/O Virtualization? > > > > + */ > > > > +#define VIRTIO_F_SR_IOV 37 > > > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > > > -- > > > > 2.17.0 > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: virtio-dev-unsubscribe at lists.oasis-open.org > > > For additional commands, e-mail: virtio-dev...

...ORM 33 > > > > > > + > > > > > > +/* > > > > > > + * Does the device support Single Root I/O Virtualization? > > > > > > + */ > > > > > > +#define VIRTIO_F_SR_IOV 37 > > > > > > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ > > > > > > -- > > > > > > 2.17.0 > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: virtio-dev-unsubscribe at lists.oasis-open.org > &gt...

...y with legacy systems. > */ > #define VIRTIO_F_IOMMU_PLATFORM 33 > + > +/* > + * If clear - driver may use barriers suitable for CPU cores. > + * If set - driver must use barriers suitable for hardware devices. > + */ > +#define VIRTIO_F_IO_BARRIER 37 > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ Hi: I believe this depends on Michael's patch of "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" ? Thanks

..._IOMMU_PLATFORM 33 >>> + >>> +/* >>> + * If clear - driver may use barriers suitable for CPU cores. >>> + * If set - driver must use barriers suitable for hardware devices. >>> + */ >>> +#define VIRTIO_F_IO_BARRIER 37 >>> #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ >> Hi: >> >> I believe this depends on Michael's patch of >> >> "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" >> >> ? >> >> Thanks > We already have below commit and some other related commits > in the tree: &...

...lity with legacy systems. > */ > #define VIRTIO_F_IOMMU_PLATFORM 33 > + > +/* > + * If clear - driver may use barriers suitable for CPU cores. > + * If set - driver must use barriers suitable for hardware devices. > + */ > +#define VIRTIO_F_IO_BARRIER 37 > #endif /* _UAPI_LINUX_VIRTIO_CONFIG_H */ Why 37? I'd use 34 I think. > -- > 2.11.0