search for: virtio_transport_f_end

Displaying 20 results from an estimated 186 matches for "virtio_transport_f_end".

[virtio-dev] [PATCH] virtio_pci: support enabling VFs
2018 May 30
2
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
...91f..b7c1f4e7d59e 100644 > > --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > There is a value in the comment directly before this that should > be updated as well to be consistent with the new value for > VIRTIO_TRANSPORT_F_END below. It hasn't been updated to 34 yet. I suggest a separate patch to replace the numbers with VIRTIO_TRANSPORT_F_START and VIRTIO_TRANSPORT_F_END in the comment. Maybe replace "e.g. virtio_ring" with "e.g. virtio_ring, virtio_pci etc." as well. > > * transport be...
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
2018 May 30
2
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
...91f..b7c1f4e7d59e 100644 > > --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > There is a value in the comment directly before this that should > be updated as well to be consistent with the new value for > VIRTIO_TRANSPORT_F_END below. It hasn't been updated to 34 yet. I suggest a separate patch to replace the numbers with VIRTIO_TRANSPORT_F_START and VIRTIO_TRANSPORT_F_END in the comment. Maybe replace "e.g. virtio_ring" with "e.g. virtio_ring, virtio_pci etc." as well. > > * transport be...
[PATCH] virtio: update the comments for transport features
2018 Jun 01
2
[PATCH] virtio: update the comments for transport features
...*/ #define VIRTIO_CONFIG_S_FAILED 0x80 -/* Some virtio feature bits (currently bits 28 through 32) are reserved for the - * transport being used (eg. virtio_ring), the rest are per-device feature - * bits. */ +/* + * Some virtio feature bits (currently 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 28 #define VIRTIO_TRANSPORT_F_END 38 -- 2.17.0
[PATCH v2] virtio: update the comments for transport features
2018 Jun 01
2
[PATCH v2] virtio: update the comments for transport features
...en up on this device. */ #define VIRTIO_CONFIG_S_FAILED 0x80 -/* Some virtio feature bits (currently bits 28 through 32) are reserved for the - * transport being used (eg. virtio_ring), the rest are per-device feature - * bits. */ +/* + * 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 28 #define VIRTIO_TRANSPORT_F_END 38 -- 2.17.0
[PATCH v2] virtio: update the comments for transport features
2018 Jun 01
2
[PATCH v2] virtio: update the comments for transport features
...en up on this device. */ #define VIRTIO_CONFIG_S_FAILED 0x80 -/* Some virtio feature bits (currently bits 28 through 32) are reserved for the - * transport being used (eg. virtio_ring), the rest are per-device feature - * bits. */ +/* + * 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 28 #define VIRTIO_TRANSPORT_F_END 38 -- 2.17.0
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
2018 May 10
2
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
...> --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > * transport being used (eg. virtio_ring), the rest are per-device feature > > * bits. */ > > #define VIRTIO_TRANSPORT_F_START 28 > > -#define VIRTIO_TRANSPORT_F_END 34 > > +#define VIRTIO_TRANSPORT_F_END 37 > > Have you updated "2.2 Feature Bits" in the VIRTIO spec? > > In 1.0 it says: > > 24 to 32 > Feature bits reserved for extensions to the queue and feature negotiation mechanisms > > This information is...
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
2018 May 10
2
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
...> --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > * transport being used (eg. virtio_ring), the rest are per-device feature > > * bits. */ > > #define VIRTIO_TRANSPORT_F_START 28 > > -#define VIRTIO_TRANSPORT_F_END 34 > > +#define VIRTIO_TRANSPORT_F_END 37 > > Have you updated "2.2 Feature Bits" in the VIRTIO spec? > > In 1.0 it says: > > 24 to 32 > Feature bits reserved for extensions to the queue and feature negotiation mechanisms > > This information is...
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
2018 May 04
2
[PATCH v1] virtio: support VIRTIO_F_IO_BARRIER
...pi/linux/virtio_config.h index 308e2096291f..9fb519a9df28 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -49,7 +49,7 @@ * transport being used (eg. virtio_ring), the rest are per-device feature * bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 34 +#define VIRTIO_TRANSPORT_F_END 37 #ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,10 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * If clear - driver may use...
[PATCH] virtio_pci: support enabling VFs
2018 May 30
8
[PATCH] virtio_pci: support enabling VFs
...pi/linux/virtio_config.h index 308e2096291f..b7c1f4e7d59e 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -49,7 +49,7 @@ * transport being used (eg. virtio_ring), the rest are per-device feature * bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 34 +#define VIRTIO_TRANSPORT_F_END 38 #ifndef VIRTIO_CONFIG_NO_LEGACY /* 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 Sin...
[PATCH] virtio_pci: support enabling VFs
2018 May 30
8
[PATCH] virtio_pci: support enabling VFs
...pi/linux/virtio_config.h index 308e2096291f..b7c1f4e7d59e 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -49,7 +49,7 @@ * transport being used (eg. virtio_ring), the rest are per-device feature * bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 34 +#define VIRTIO_TRANSPORT_F_END 38 #ifndef VIRTIO_CONFIG_NO_LEGACY /* 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 Sin...
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
2018 Jun 01
1
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
...virtio_config.h > > > > +++ b/include/uapi/linux/virtio_config.h > > > > @@ -49,7 +49,7 @@ > > > > > > There is a value in the comment directly before this that should > > > be updated as well to be consistent with the new value for > > > VIRTIO_TRANSPORT_F_END below. > > > > It hasn't been updated to 34 yet. > > I suggest a separate patch to replace the numbers with > > VIRTIO_TRANSPORT_F_START and VIRTIO_TRANSPORT_F_END > > in the comment. > > Maybe replace "e.g. virtio_ring" with "e.g. virtio_ring...
[RFC] virtio: support VIRTIO_F_IO_BARRIER
2018 May 03
6
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...pi/linux/virtio_config.h index 308e2096291f..6ca8d24bf468 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -49,7 +49,7 @@ * transport being used (eg. virtio_ring), the rest are per-device feature * bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 34 +#define VIRTIO_TRANSPORT_F_END 38 #ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,10 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * If clear - driver may use...
[RFC] virtio: support VIRTIO_F_IO_BARRIER
2018 May 03
6
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...pi/linux/virtio_config.h index 308e2096291f..6ca8d24bf468 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -49,7 +49,7 @@ * transport being used (eg. virtio_ring), the rest are per-device feature * bits. */ #define VIRTIO_TRANSPORT_F_START 28 -#define VIRTIO_TRANSPORT_F_END 34 +#define VIRTIO_TRANSPORT_F_END 38 #ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've @@ -71,4 +71,10 @@ * this is for compatibility with legacy systems. */ #define VIRTIO_F_IOMMU_PLATFORM 33 + +/* + * If clear - driver may use...
[PATCH RFC 1/2] virtio: introduce packed ring defines
2018 Feb 27
3
[PATCH RFC 1/2] virtio: introduce packed ring defines
...ex 308e2096291f..e3d077ef5207 100644 >--- a/include/uapi/linux/virtio_config.h >+++ b/include/uapi/linux/virtio_config.h >@@ -49,7 +49,7 @@ > * transport being used (eg. virtio_ring), the rest are per-device feature > * bits. */ > #define VIRTIO_TRANSPORT_F_START 28 >-#define VIRTIO_TRANSPORT_F_END 34 >+#define VIRTIO_TRANSPORT_F_END 37 > > #ifndef VIRTIO_CONFIG_NO_LEGACY > /* Do we get callbacks when the ring is completely used, even if we've >@@ -71,4 +71,20 @@ > * this is for compatibility with legacy systems. > */ > #define VIRTIO_F_IOMMU_PLATFORM 33 >+...
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
2018 May 31
0
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
...> --- a/include/uapi/linux/virtio_config.h > > > +++ b/include/uapi/linux/virtio_config.h > > > @@ -49,7 +49,7 @@ > > > > There is a value in the comment directly before this that should > > be updated as well to be consistent with the new value for > > VIRTIO_TRANSPORT_F_END below. > > It hasn't been updated to 34 yet. > I suggest a separate patch to replace the numbers with > VIRTIO_TRANSPORT_F_START and VIRTIO_TRANSPORT_F_END > in the comment. > Maybe replace "e.g. virtio_ring" with "e.g. virtio_ring, > virtio_pci etc." a...
[virtio-dev] [PATCH] virtio: update the comments for transport features
2018 Jun 01
0
[virtio-dev] [PATCH] virtio: update the comments for transport features
...0x80 > > -/* Some virtio feature bits (currently bits 28 through 32) are reserved for the > - * transport being used (eg. virtio_ring), the rest are per-device feature > - * bits. */ > +/* > + * Some virtio feature bits (currently bits VIRTIO_TRANSPORT_F_START > + * through VIRTIO_TRANSPORT_F_END) are reserved for the transport being It will always be bits up to VIRTIO_TRANSPORT_F_END, no? So you can drop the "currently"? Or reword as "Virtio feature bits VIRTIO_TRANSPORT_F_START through VIRTIO_TRANSPORT_F_END are reserved..."? > + * used (e.g. virtio_ring, virtio_...
[RFC] virtio: support VIRTIO_F_IO_BARRIER
2018 May 03
2
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...; --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > * transport being used (eg. virtio_ring), the rest are per-device feature > > * bits. */ > > #define VIRTIO_TRANSPORT_F_START 28 > > -#define VIRTIO_TRANSPORT_F_END 34 > > +#define VIRTIO_TRANSPORT_F_END 38 > > #ifndef VIRTIO_CONFIG_NO_LEGACY > > /* Do we get callbacks when the ring is completely used, even if we've > > @@ -71,4 +71,10 @@ > > * this is for compatibility with legacy systems. > > */ > >...
[RFC] virtio: support VIRTIO_F_IO_BARRIER
2018 May 03
2
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...; --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > * transport being used (eg. virtio_ring), the rest are per-device feature > > * bits. */ > > #define VIRTIO_TRANSPORT_F_START 28 > > -#define VIRTIO_TRANSPORT_F_END 34 > > +#define VIRTIO_TRANSPORT_F_END 38 > > #ifndef VIRTIO_CONFIG_NO_LEGACY > > /* Do we get callbacks when the ring is completely used, even if we've > > @@ -71,4 +71,10 @@ > > * this is for compatibility with legacy systems. > > */ > >...
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
2018 May 30
0
[virtio-dev] [PATCH] virtio_pci: support enabling VFs
...irtio_config.h > index 308e2096291f..b7c1f4e7d59e 100644 > --- a/include/uapi/linux/virtio_config.h > +++ b/include/uapi/linux/virtio_config.h > @@ -49,7 +49,7 @@ There is a value in the comment directly before this that should be updated as well to be consistent with the new value for VIRTIO_TRANSPORT_F_END below. > * transport being used (eg. virtio_ring), the rest are per-device feature > * bits. */ > #define VIRTIO_TRANSPORT_F_START 28 > -#define VIRTIO_TRANSPORT_F_END 34 > +#define VIRTIO_TRANSPORT_F_END 38 > > #ifndef VIRTIO_CONFIG_NO_LEGACY > /* Do we get callba...
[RFC] virtio: support VIRTIO_F_IO_BARRIER
2018 May 03
1
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...+++ b/include/uapi/linux/virtio_config.h > > > > @@ -49,7 +49,7 @@ > > > > * transport being used (eg. virtio_ring), the rest are per-device feature > > > > * bits. */ > > > > #define VIRTIO_TRANSPORT_F_START 28 > > > > -#define VIRTIO_TRANSPORT_F_END 34 > > > > +#define VIRTIO_TRANSPORT_F_END 38 > > > > #ifndef VIRTIO_CONFIG_NO_LEGACY > > > > /* Do we get callbacks when the ring is completely used, even if we've > > > > @@ -71,4 +71,10 @@ > > > > * this is for compatibi...