From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH v2] vfio: Remove vfio_group dev_counter
Date: Fri, 2 Sep 2022 12:42:35 -0600 [thread overview]
Message-ID: <20220902124235.46794868.alex.williamson@redhat.com> (raw)
In-Reply-To: <0-v2-d4374a7bf0c9+c4-vfio_dev_counter_jgg@nvidia.com>
On Tue, 16 Aug 2022 16:13:04 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> This counts the number of devices attached to a vfio_group, ie the number
> of items in the group->device_list.
>
> It is only read in vfio_pin_pages(), as some kind of protection against
> limitations in type1.
>
> However, with all the code cleanups in this area, now that
> vfio_pin_pages() accepts a vfio_device directly it is redundant. All
> drivers are already calling vfio_register_emulated_iommu_dev() which
> directly creates a group specifically for the device and thus it is
> guaranteed that there is a singleton group.
>
> Leave a note in the comment about this requirement and remove the logic.
>
> Reviewed-by: Yi Liu <yi.l.liu@intel.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
> drivers/vfio/vfio_main.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
Applied to vfio next branch for v6.1. Thanks,
Alex
prev parent reply other threads:[~2022-09-02 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 19:13 [PATCH v2] vfio: Remove vfio_group dev_counter Jason Gunthorpe
2022-08-22 4:39 ` Tian, Kevin
2022-08-22 18:35 ` Alex Williamson
2022-08-23 1:31 ` Tian, Kevin
2022-08-24 0:38 ` Jason Gunthorpe
2022-08-24 22:02 ` Alex Williamson
2022-08-25 0:43 ` Jason Gunthorpe
2022-09-06 9:21 ` Tian, Kevin
2022-09-06 13:59 ` Jason Gunthorpe
2022-08-29 2:02 ` Tian, Kevin
2022-09-02 18:42 ` Alex Williamson [this message]
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=20220902124235.46794868.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=yi.l.liu@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