From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: <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>, <cohuck@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 v10 Kernel 2/5] vfio iommu: Adds flag to indicate dirty pages tracking capability support
Date: Mon, 16 Dec 2019 16:16:52 -0700 [thread overview]
Message-ID: <20191216161652.30681b05@x1.home> (raw)
In-Reply-To: <1576527700-21805-3-git-send-email-kwankhede@nvidia.com>
On Tue, 17 Dec 2019 01:51:37 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:
> Flag VFIO_IOMMU_INFO_DIRTY_PGS in VFIO_IOMMU_GET_INFO indicates that driver
> support dirty pages tracking.
>
> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> Reviewed-by: Neo Jia <cjia@nvidia.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 3 ++-
> include/uapi/linux/vfio.h | 5 +++--
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 2ada8e6cdb88..3f6b04f2334f 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -2234,7 +2234,8 @@ static long vfio_iommu_type1_ioctl(void *iommu_data,
> info.cap_offset = 0; /* output, no-recopy necessary */
> }
>
> - info.flags = VFIO_IOMMU_INFO_PGSIZES;
> + info.flags = VFIO_IOMMU_INFO_PGSIZES |
> + VFIO_IOMMU_INFO_DIRTY_PGS;
Type1 shouldn't advertise it until it's supported though, right?
Thanks,
Alex
>
> info.iova_pgsizes = vfio_pgsize_bitmap(iommu);
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index a0817ba267c1..81847ed54eb7 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -900,8 +900,9 @@ struct vfio_device_ioeventfd {
> struct vfio_iommu_type1_info {
> __u32 argsz;
> __u32 flags;
> -#define VFIO_IOMMU_INFO_PGSIZES (1 << 0) /* supported page sizes info */
> -#define VFIO_IOMMU_INFO_CAPS (1 << 1) /* Info supports caps */
> +#define VFIO_IOMMU_INFO_PGSIZES (1 << 0) /* supported page sizes info */
> +#define VFIO_IOMMU_INFO_CAPS (1 << 1) /* Info supports caps */
> +#define VFIO_IOMMU_INFO_DIRTY_PGS (1 << 2) /* supports dirty page tracking */
> __u64 iova_pgsizes; /* Bitmap of supported page sizes */
> __u32 cap_offset; /* Offset within info struct of first cap */
> };
next prev parent reply other threads:[~2019-12-16 23:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 20:21 [PATCH v10 Kernel 0/5] KABIs to support migration for VFIO devices Kirti Wankhede
2019-12-16 20:21 ` [PATCH v10 Kernel 1/5] vfio: KABI for migration interface for device state Kirti Wankhede
2019-12-16 22:44 ` Alex Williamson
2019-12-17 6:28 ` Kirti Wankhede
2019-12-17 7:12 ` Yan Zhao
2019-12-17 18:43 ` Alex Williamson
2019-12-19 16:08 ` Kirti Wankhede
2019-12-19 17:27 ` Alex Williamson
2019-12-19 20:10 ` Kirti Wankhede
2019-12-19 21:09 ` Alex Williamson
2020-01-02 18:25 ` Dr. David Alan Gilbert
2020-01-06 23:18 ` Alex Williamson
2020-01-07 7:28 ` Kirti Wankhede
2020-01-07 17:09 ` Alex Williamson
2020-01-07 17:53 ` Kirti Wankhede
2020-01-07 18:56 ` Alex Williamson
2020-01-08 14:59 ` Cornelia Huck
2020-01-08 18:31 ` Alex Williamson
2020-01-08 20:41 ` Kirti Wankhede
2020-01-08 22:44 ` Alex Williamson
2020-01-10 14:21 ` Cornelia Huck
2020-01-07 9:57 ` Dr. David Alan Gilbert
2020-01-07 16:54 ` Alex Williamson
2020-01-07 17:50 ` Dr. David Alan Gilbert
2019-12-16 20:21 ` [PATCH v10 Kernel 2/5] vfio iommu: Adds flag to indicate dirty pages tracking capability support Kirti Wankhede
2019-12-16 23:16 ` Alex Williamson [this message]
2019-12-17 6:32 ` Kirti Wankhede
2019-12-16 20:21 ` [PATCH v10 Kernel 3/5] vfio iommu: Add ioctl defination for dirty pages tracking Kirti Wankhede
2019-12-16 20:21 ` [PATCH v10 Kernel 4/5] vfio iommu: Implementation of ioctl to " Kirti Wankhede
2019-12-17 5:15 ` Yan Zhao
2019-12-17 9:24 ` Kirti Wankhede
2019-12-17 9:51 ` Yan Zhao
2019-12-17 11:47 ` Kirti Wankhede
2019-12-18 1:04 ` Yan Zhao
2019-12-18 20:05 ` Dr. David Alan Gilbert
2019-12-19 0:57 ` Yan Zhao
2019-12-19 16:21 ` Kirti Wankhede
2019-12-20 0:58 ` Yan Zhao
2020-01-03 19:44 ` Dr. David Alan Gilbert
2020-01-04 3:53 ` Yan Zhao
2019-12-18 21:39 ` Alex Williamson
2019-12-19 18:42 ` Kirti Wankhede
2019-12-19 18:56 ` Alex Williamson
2019-12-16 20:21 ` [PATCH v10 Kernel 5/5] vfio iommu: Update UNMAP_DMA ioctl to get dirty bitmap before unmap 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=20191216161652.30681b05@x1.home \
--to=alex.williamson@redhat.com \
--cc=Ken.Xue@amd.com \
--cc=Zhengxiao.zx@Alibaba-inc.com \
--cc=aik@ozlabs.ru \
--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=kwankhede@nvidia.com \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).