vfio/type1: Fix migration info capability ID
ID 1 is already used by the IOVA range capability, use ID 2.
Reported-by: Liu Yi L <yi.l.liu@intel.com>
Fixes: ad721705d0 ("vfio iommu: Add migration capability to report supported features")
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
This commit is contained in:
@@ -1030,7 +1030,7 @@ struct vfio_iommu_type1_info_cap_iova_range {
|
|||||||
* size in bytes that can be used by user applications when getting the dirty
|
* size in bytes that can be used by user applications when getting the dirty
|
||||||
* bitmap.
|
* bitmap.
|
||||||
*/
|
*/
|
||||||
#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 1
|
#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 2
|
||||||
|
|
||||||
struct vfio_iommu_type1_info_cap_migration {
|
struct vfio_iommu_type1_info_cap_migration {
|
||||||
struct vfio_info_cap_header header;
|
struct vfio_info_cap_header header;
|
||||||
|
|||||||
Reference in New Issue
Block a user