From: Alex Williamson <alex.williamson@redhat.com>
To: Yan Zhao <yan.y.zhao@intel.com>
Cc: cohuck@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio: add a singleton check for vfio_group_pin_pages
Date: Tue, 15 Sep 2020 13:03:01 -0600 [thread overview]
Message-ID: <20200915130301.15d95412@x1.home> (raw)
In-Reply-To: <20200915003042.14273-1-yan.y.zhao@intel.com>
On Tue, 15 Sep 2020 08:30:42 +0800
Yan Zhao <yan.y.zhao@intel.com> wrote:
> vfio_pin_pages() and vfio_group_pin_pages() are used purely to mark dirty
> pages to devices with IOMMU backend as they already have all VM pages
> pinned at VM startup.
This is wrong. The entire initial basis of mdev devices is for
non-IOMMU backed devices which provide mediation outside of the scope
of the IOMMU. That mediation includes interpreting device DMA
programming and making use of the vfio_pin_pages() interface to
translate and pin IOVA address to HPA. Marking pages dirty is a
secondary feature.
> when there're multiple devices in the vfio group, the dirty pages
> marked through pin_pages interface by one device is not useful as the
> other devices may access and dirty any VM pages.
I don't know of any cases where there are multiple devices in a group
that would make use of this interface, however, all devices within a
group necessarily share an IOMMU context and any one device dirtying a
page will dirty that page for all devices, so I don't see that this is
a valid statement either.
> So added a check such that only singleton IOMMU groups can pin pages
> in vfio_group_pin_pages. for mdevs, there's always only one dev in a
> vfio group.
> This is a fix to the commit below that added a singleton IOMMU group
> check in vfio_pin_pages.
None of the justification above is accurate, please try again. Thanks,
Alex
> Fixes: 95fc87b44104 (vfio: Selective dirty page tracking if IOMMU backed
> device pins pages)
>
> Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
> ---
> drivers/vfio/vfio.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index 5e6e0511b5aa..2f0fa272ebf2 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -2053,6 +2053,9 @@ int vfio_group_pin_pages(struct vfio_group *group,
> if (!group || !user_iova_pfn || !phys_pfn || !npage)
> return -EINVAL;
>
> + if (group->dev_counter > 1)
> + return -EINVAL;
> +
> if (npage > VFIO_PIN_PAGES_MAX_ENTRIES)
> return -E2BIG;
>
next prev parent reply other threads:[~2020-09-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 0:30 [PATCH] vfio: add a singleton check for vfio_group_pin_pages Yan Zhao
2020-09-15 19:03 ` Alex Williamson [this message]
2020-09-15 19:30 ` Alex Williamson
2020-09-16 1:30 ` Yan Zhao
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=20200915130301.15d95412@x1.home \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yan.y.zhao@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