* [PATCH] vfio/type1: Fix migration info capability ID
@ 2020-06-18 19:12 Alex Williamson
2020-06-19 12:59 ` Kirti Wankhede
0 siblings, 1 reply; 2+ messages in thread
From: Alex Williamson @ 2020-06-18 19:12 UTC (permalink / raw)
To: alex.williamson; +Cc: Liu Yi L, Kirti Wankhede, linux-kernel, kvm
ID 1 is already used by the IOVA range capability, use ID 2.
Reported-by: Liu Yi L <yi.l.liu@intel.com>
Cc: Kirti Wankhede <kwankhede@nvidia.com>
Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported features")
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
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;
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] vfio/type1: Fix migration info capability ID
2020-06-18 19:12 [PATCH] vfio/type1: Fix migration info capability ID Alex Williamson
@ 2020-06-19 12:59 ` Kirti Wankhede
0 siblings, 0 replies; 2+ messages in thread
From: Kirti Wankhede @ 2020-06-19 12:59 UTC (permalink / raw)
To: Alex Williamson; +Cc: Liu Yi L, linux-kernel, kvm
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@nvidia.com>
> Reported-by: Liu Yi L <yi.l.liu@intel.com>
> Cc: Kirti Wankhede <kwankhede@nvidia.com>
> Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported features")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> 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;
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-06-19 12:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-18 19:12 [PATCH] vfio/type1: Fix migration info capability ID Alex Williamson
2020-06-19 12:59 ` Kirti Wankhede
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®