From: Kirti Wankhede <kwankhede@nvidia.com> To: Cornelia Huck <cohuck@redhat.com> Cc: <alex.williamson@redhat.com>, <cjia@nvidia.com>, <kevin.tian@intel.com>, <ziye.yang@intel.com>, <changpeng.liu@intel.com>, <yi.l.liu@intel.com>, <mlevitsk@redhat.com>, <eskultet@redhat.com>, <dgilbert@redhat.com>, <jonathan.davies@nutanix.com>, <eauger@redhat.com>, <aik@ozlabs.ru>, <pasic@linux.ibm.com>, <felipe@nutanix.com>, <Zhengxiao.zx@Alibaba-inc.com>, <shuangtai.tst@alibaba-inc.com>, <Ken.Xue@amd.com>, <zhi.a.wang@intel.com>, <yan.y.zhao@intel.com>, <qemu-devel@nongnu.org>, <kvm@vger.kernel.org> Subject: Re: [PATCH Kernel v22 7/8] vfio iommu: Add migration capability to report supported features Date: Wed, 20 May 2020 20:53:13 +0530 [thread overview] Message-ID: <58ec5324-43e5-29cb-73b1-3675444cf89b@nvidia.com> (raw) In-Reply-To: <20200520124200.0b4f3562.cohuck@redhat.com> On 5/20/2020 4:12 PM, Cornelia Huck wrote: > On Mon, 18 May 2020 11:26:36 +0530 > Kirti Wankhede <kwankhede@nvidia.com> wrote: > >> Added migration capability in IOMMU info chain. >> User application should check IOMMU info chain for migration capability >> to use dirty page tracking feature provided by kernel module. >> User application must check page sizes supported and maximum dirty >> bitmap size returned by this capability structure for ioctls used to get >> dirty bitmap. >> >> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com> >> --- >> drivers/vfio/vfio_iommu_type1.c | 23 ++++++++++++++++++++++- >> include/uapi/linux/vfio.h | 22 ++++++++++++++++++++++ >> 2 files changed, 44 insertions(+), 1 deletion(-) > > (...) > >> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h >> index a1dd2150971e..aa8aa9dcf02a 100644 >> --- a/include/uapi/linux/vfio.h >> +++ b/include/uapi/linux/vfio.h >> @@ -1013,6 +1013,28 @@ struct vfio_iommu_type1_info_cap_iova_range { >> struct vfio_iova_range iova_ranges[]; >> }; >> >> +/* >> + * The migration capability allows to report supported features for migration. >> + * >> + * The structures below define version 1 of this capability. >> + * >> + * The existence of this capability indicates IOMMU kernel driver supports > > s/indicates/indicates that/ > >> + * dirty page tracking. >> + * >> + * pgsize_bitmap: Kernel driver returns supported page sizes bitmap for dirty >> + * page tracking. > > "bitmap of supported page sizes for dirty page tracking" ? > >> + * max_dirty_bitmap_size: Kernel driver returns maximum supported dirty bitmap >> + * size in bytes to be used by user application for ioctls to get dirty bitmap. > > "maximum supported dirty bitmap size in bytes that can be used by user > applications when getting the dirty bitmap" ? > Done. >> + */ >> +#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 1 >> + >> +struct vfio_iommu_type1_info_cap_migration { >> + struct vfio_info_cap_header header; >> + __u32 flags; >> + __u64 pgsize_bitmap; >> + __u64 max_dirty_bitmap_size; /* in bytes */ >> +}; >> + >> #define VFIO_IOMMU_GET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12) >> >> /** > > Reviewed-by: Cornelia Huck <cohuck@redhat.com> > Thanks. Kirti
WARNING: multiple messages have this Message-ID (diff)
From: Kirti Wankhede <kwankhede@nvidia.com> To: Cornelia Huck <cohuck@redhat.com> Cc: kevin.tian@intel.com, yi.l.liu@intel.com, cjia@nvidia.com, kvm@vger.kernel.org, eskultet@redhat.com, ziye.yang@intel.com, qemu-devel@nongnu.org, Zhengxiao.zx@Alibaba-inc.com, shuangtai.tst@alibaba-inc.com, dgilbert@redhat.com, zhi.a.wang@intel.com, mlevitsk@redhat.com, pasic@linux.ibm.com, aik@ozlabs.ru, alex.williamson@redhat.com, eauger@redhat.com, felipe@nutanix.com, jonathan.davies@nutanix.com, yan.y.zhao@intel.com, changpeng.liu@intel.com, Ken.Xue@amd.com Subject: Re: [PATCH Kernel v22 7/8] vfio iommu: Add migration capability to report supported features Date: Wed, 20 May 2020 20:53:13 +0530 [thread overview] Message-ID: <58ec5324-43e5-29cb-73b1-3675444cf89b@nvidia.com> (raw) In-Reply-To: <20200520124200.0b4f3562.cohuck@redhat.com> On 5/20/2020 4:12 PM, Cornelia Huck wrote: > On Mon, 18 May 2020 11:26:36 +0530 > Kirti Wankhede <kwankhede@nvidia.com> wrote: > >> Added migration capability in IOMMU info chain. >> User application should check IOMMU info chain for migration capability >> to use dirty page tracking feature provided by kernel module. >> User application must check page sizes supported and maximum dirty >> bitmap size returned by this capability structure for ioctls used to get >> dirty bitmap. >> >> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com> >> --- >> drivers/vfio/vfio_iommu_type1.c | 23 ++++++++++++++++++++++- >> include/uapi/linux/vfio.h | 22 ++++++++++++++++++++++ >> 2 files changed, 44 insertions(+), 1 deletion(-) > > (...) > >> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h >> index a1dd2150971e..aa8aa9dcf02a 100644 >> --- a/include/uapi/linux/vfio.h >> +++ b/include/uapi/linux/vfio.h >> @@ -1013,6 +1013,28 @@ struct vfio_iommu_type1_info_cap_iova_range { >> struct vfio_iova_range iova_ranges[]; >> }; >> >> +/* >> + * The migration capability allows to report supported features for migration. >> + * >> + * The structures below define version 1 of this capability. >> + * >> + * The existence of this capability indicates IOMMU kernel driver supports > > s/indicates/indicates that/ > >> + * dirty page tracking. >> + * >> + * pgsize_bitmap: Kernel driver returns supported page sizes bitmap for dirty >> + * page tracking. > > "bitmap of supported page sizes for dirty page tracking" ? > >> + * max_dirty_bitmap_size: Kernel driver returns maximum supported dirty bitmap >> + * size in bytes to be used by user application for ioctls to get dirty bitmap. > > "maximum supported dirty bitmap size in bytes that can be used by user > applications when getting the dirty bitmap" ? > Done. >> + */ >> +#define VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION 1 >> + >> +struct vfio_iommu_type1_info_cap_migration { >> + struct vfio_info_cap_header header; >> + __u32 flags; >> + __u64 pgsize_bitmap; >> + __u64 max_dirty_bitmap_size; /* in bytes */ >> +}; >> + >> #define VFIO_IOMMU_GET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12) >> >> /** > > Reviewed-by: Cornelia Huck <cohuck@redhat.com> > Thanks. Kirti
next prev parent reply other threads:[~2020-05-20 15:23 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-18 5:56 [PATCH Kernel v22 0/8] Add UAPIs to support migration for VFIO devices Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 1/8] vfio: UAPI for migration interface for device state Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 2/8] vfio iommu: Remove atomicity of ref_count of pinned pages Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 3/8] vfio iommu: Cache pgsize_bitmap in struct vfio_iommu Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-20 10:08 ` Cornelia Huck 2020-05-20 10:08 ` Cornelia Huck 2020-05-20 14:46 ` Kirti Wankhede 2020-05-20 14:46 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 4/8] vfio iommu: Add ioctl definition for dirty pages tracking Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 5/8] vfio iommu: Implementation of ioctl " Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-18 21:53 ` Alex Williamson 2020-05-18 21:53 ` Alex Williamson 2020-05-19 7:11 ` Kirti Wankhede 2020-05-19 7:11 ` Kirti Wankhede 2020-05-19 6:52 ` Kirti Wankhede 2020-05-19 6:52 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 6/8] vfio iommu: Update UNMAP_DMA ioctl to get dirty bitmap before unmap Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-19 6:54 ` Kirti Wankhede 2020-05-19 6:54 ` Kirti Wankhede 2020-05-20 10:27 ` Cornelia Huck 2020-05-20 10:27 ` Cornelia Huck 2020-05-20 15:16 ` Kirti Wankhede 2020-05-20 15:16 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 7/8] vfio iommu: Add migration capability to report supported features Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-20 10:42 ` Cornelia Huck 2020-05-20 10:42 ` Cornelia Huck 2020-05-20 15:23 ` Kirti Wankhede [this message] 2020-05-20 15:23 ` Kirti Wankhede 2020-05-18 5:56 ` [PATCH Kernel v22 8/8] vfio: Selective dirty page tracking if IOMMU backed device pins pages Kirti Wankhede 2020-05-18 5:56 ` Kirti Wankhede 2020-05-19 6:54 ` Kirti Wankhede 2020-05-19 6:54 ` Kirti Wankhede 2020-05-19 16:58 ` [PATCH Kernel v22 0/8] Add UAPIs to support migration for VFIO devices Alex Williamson 2020-05-19 16:58 ` Alex Williamson 2020-05-20 2:55 ` Yan Zhao 2020-05-20 2:55 ` Yan Zhao 2020-05-20 13:40 ` Kirti Wankhede 2020-05-20 13:40 ` Kirti Wankhede 2020-05-20 16:46 ` Alex Williamson 2020-05-20 16:46 ` Alex Williamson 2020-05-21 5:08 ` Yan Zhao 2020-05-21 5:08 ` Yan Zhao 2020-05-21 7:09 ` Kirti Wankhede 2020-05-21 7:09 ` Kirti Wankhede 2020-05-21 7:04 ` Yan Zhao 2020-05-21 7:04 ` Yan Zhao 2020-05-21 7:28 ` Kirti Wankhede 2020-05-21 7:28 ` Kirti Wankhede 2020-05-21 7:32 ` Kirti Wankhede 2020-05-21 7:32 ` Kirti Wankhede 2020-05-25 6:59 ` Yan Zhao 2020-05-25 6:59 ` Yan Zhao 2020-05-25 13:20 ` Kirti Wankhede 2020-05-25 13:20 ` Kirti Wankhede 2020-05-26 20:19 ` Alex Williamson 2020-05-26 20:19 ` Alex Williamson 2020-05-27 6:23 ` Yan Zhao 2020-05-27 6:23 ` Yan Zhao 2020-05-27 8:48 ` Dr. David Alan Gilbert 2020-05-27 8:48 ` Dr. David Alan Gilbert 2020-05-28 8:01 ` Yan Zhao 2020-05-28 8:01 ` Yan Zhao 2020-05-28 22:53 ` Alex Williamson 2020-05-28 22:53 ` Alex Williamson 2020-05-29 11:12 ` Dr. David Alan Gilbert 2020-05-29 11:12 ` Dr. David Alan Gilbert 2020-05-28 22:59 ` Alex Williamson 2020-05-28 22:59 ` Alex Williamson 2020-05-29 4:15 ` Yan Zhao 2020-05-29 4:15 ` Yan Zhao 2020-05-29 17:57 ` Kirti Wankhede 2020-05-29 17:57 ` Kirti Wankhede
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=58ec5324-43e5-29cb-73b1-3675444cf89b@nvidia.com \ --to=kwankhede@nvidia.com \ --cc=Ken.Xue@amd.com \ --cc=Zhengxiao.zx@Alibaba-inc.com \ --cc=aik@ozlabs.ru \ --cc=alex.williamson@redhat.com \ --cc=changpeng.liu@intel.com \ --cc=cjia@nvidia.com \ --cc=cohuck@redhat.com \ --cc=dgilbert@redhat.com \ --cc=eauger@redhat.com \ --cc=eskultet@redhat.com \ --cc=felipe@nutanix.com \ --cc=jonathan.davies@nutanix.com \ --cc=kevin.tian@intel.com \ --cc=kvm@vger.kernel.org \ --cc=mlevitsk@redhat.com \ --cc=pasic@linux.ibm.com \ --cc=qemu-devel@nongnu.org \ --cc=shuangtai.tst@alibaba-inc.com \ --cc=yan.y.zhao@intel.com \ --cc=yi.l.liu@intel.com \ --cc=zhi.a.wang@intel.com \ --cc=ziye.yang@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.