From afd264b3f4aedca15e415a7999c13240b159000f Mon Sep 17 00:00:00 2001 From: Dariusz Stojaczyk Date: Fri, 30 Mar 2018 19:35:47 +0200 Subject: [PATCH] include/linux: update virtio_config.h Updated to Linux 4.9.0. This introduces e.g. VIRTIO_CONFIG_S_NEEDS_RESET flag that's required for the next patch. Change-Id: I562d0b9d9a3cb18fd484dda52fb447087062da47 Signed-off-by: Dariusz Stojaczyk Reviewed-on: https://review.gerrithub.io/405916 Reviewed-by: Daniel Verkamp Tested-by: SPDK Automated Test System Reviewed-by: Jim Harris --- include/linux/virtio_config.h | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/include/linux/virtio_config.h b/include/linux/virtio_config.h index a11101e03..648b688fc 100644 --- a/include/linux/virtio_config.h +++ b/include/linux/virtio_config.h @@ -40,6 +40,8 @@ #define VIRTIO_CONFIG_S_DRIVER_OK 4 /* Driver has finished configuring features */ #define VIRTIO_CONFIG_S_FEATURES_OK 8 +/* Device entered invalid state, driver must reset it */ +#define VIRTIO_CONFIG_S_NEEDS_RESET 0x40 /* We've given up on this device. */ #define VIRTIO_CONFIG_S_FAILED 0x80 @@ -47,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 33 +#define VIRTIO_TRANSPORT_F_END 34 #ifndef VIRTIO_CONFIG_NO_LEGACY /* Do we get callbacks when the ring is completely used, even if we've @@ -61,4 +63,12 @@ /* v1.0 compliant. */ #define VIRTIO_F_VERSION_1 32 +/* + * If clear - device has the IOMMU bypass quirk feature. + * If set - use platform tools to detect the IOMMU. + * + * Note the reverse polarity (compared to most other features), + * this is for compatibility with legacy systems. + */ +#define VIRTIO_F_IOMMU_PLATFORM 33 #endif /* _LINUX_VIRTIO_CONFIG_H */