Userspace knows if the device can be resumed or not by checking this feature bit. It's only exposed if the vdpa driver backend implements the resume() operation callback. Userspace trying to negotiate this feature when it hasn't been exposed will result in an error.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -163,5 +163,7 @@ struct vhost_vdpa_iova_range { · 162 unmodified lines | |||
| 163 | #define VHOST_BACKEND_F_IOTLB_ASID 0x3 | 163 | #define VHOST_BACKEND_F_IOTLB_ASID 0x3 |
| 164 | /* Device can be suspended */ | 164 | /* Device can be suspended */ |
| 165 | #define VHOST_BACKEND_F_SUSPEND 0x4 | 165 | #define VHOST_BACKEND_F_SUSPEND 0x4 |
| 166 | /* Device can be resumed */ | ||
| 167 | #define VHOST_BACKEND_F_RESUME 0x5 | ||
| 166 | 168 | ||
| 167 | #endif | 169 | #endif |