Re: [PATCH] vfio/type1: Fix migration info capability ID

[Kirti Wankhede]

On 6/19/2020 12:42 AM, Alex Williamson wrote:
> ID 1 is already used by the IOVA range capability, use ID 2.

Ops.
Thanks for Fixing it.

Reviewed-by: Kirti Wankhede <kwankhede@xxxxxxxxxx>

> Reported-by: Liu Yi L <yi.l.liu@xxxxxxxxx>
> Cc: Kirti Wankhede <kwankhede@xxxxxxxxxx>
> Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported features")
> Signed-off-by: Alex Williamson <alex.williamson@xxxxxxxxxx>
> ---
>   include/uapi/linux/vfio.h |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index eca6692667a3..920470502329 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -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
>    * 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_info_cap_header header;