From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <cohuck@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <peterx@redhat.com>
Subject: Re: [PATCH 1/3] vfio: Introduce vma ops registration and notifier
Date: Wed, 17 Feb 2021 21:12:09 -0400 [thread overview]
Message-ID: <20210218011209.GB4247@nvidia.com> (raw)
In-Reply-To: <20210212212057.GW4247@nvidia.com>
On Fri, Feb 12, 2021 at 05:20:57PM -0400, Jason Gunthorpe wrote:
> On Fri, Feb 12, 2021 at 12:27:39PM -0700, Alex Williamson wrote:
> > Create an interface through vfio-core where a vfio bus driver (ex.
> > vfio-pci) can register the vm_operations_struct it uses to map device
> > memory, along with a set of registration callbacks. This allows
> > vfio-core to expose interfaces for IOMMU backends to match a
> > vm_area_struct to a bus driver and register a notifier for relavant
> > changes to the device mapping. For now we define only a notifier
> > action for closing the device.
> >
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > drivers/vfio/vfio.c | 120 ++++++++++++++++++++++++++++++++++++++++++++++++++
> > include/linux/vfio.h | 20 ++++++++
> > 2 files changed, 140 insertions(+)
> >
> > diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> > index 38779e6fd80c..568f5e37a95f 100644
> > +++ b/drivers/vfio/vfio.c
> > @@ -47,6 +47,8 @@ static struct vfio {
> > struct cdev group_cdev;
> > dev_t group_devt;
> > wait_queue_head_t release_q;
> > + struct list_head vm_ops_list;
> > + struct mutex vm_ops_lock;
> > } vfio;
> >
> > struct vfio_iommu_driver {
> > @@ -2354,6 +2356,121 @@ struct iommu_domain *vfio_group_iommu_domain(struct vfio_group *group)
> > }
> > EXPORT_SYMBOL_GPL(vfio_group_iommu_domain);
> >
> > +struct vfio_vma_ops {
> > + const struct vm_operations_struct *vm_ops;
> > + vfio_register_vma_nb_t *reg_fn;
> > + vfio_unregister_vma_nb_t *unreg_fn;
> > + struct list_head next;
> > +};
> > +
> > +int vfio_register_vma_ops(const struct vm_operations_struct *vm_ops,
> > + vfio_register_vma_nb_t *reg_fn,
> > + vfio_unregister_vma_nb_t *unreg_fn)
>
> This just feels a little bit too complicated
>
> I've recently learned from Daniel that we can use the address_space
> machinery to drive the zap_vma_ptes() via unmap_mapping_range(). This
> technique replaces all the open, close and vma_list logic in vfio_pci
Here is my effort to make rdma use this, it removes a lot of ugly code:
https://github.com/jgunthorpe/linux/commits/rdma_addr_space
Still needs some more detailed testing.
This gives an option to detect vfio VMAs by checking
if (vma->vm_file &&
file_inode(vma->vm_file) &&
file_inode(vma->vm_file)->i_sb->s_type == vfio_fs_type)
And all vfio VMA's can have some consistent vm_private_data, or at
worst a consistent extended vm operations struct.
Jason
next prev parent reply other threads:[~2021-02-18 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 19:27 [PATCH 0/3] vfio: Device memory DMA mapping improvements Alex Williamson
2021-02-12 19:27 ` [PATCH 1/3] vfio: Introduce vma ops registration and notifier Alex Williamson
2021-02-12 21:20 ` Jason Gunthorpe
2021-02-18 1:12 ` Jason Gunthorpe [this message]
2021-02-18 21:56 ` Alex Williamson
2021-02-18 23:04 ` Jason Gunthorpe
2021-02-19 22:02 ` Alex Williamson
2021-02-12 19:27 ` [PATCH 2/3] vfio/pci: Implement vm_ops registration Alex Williamson
2021-02-12 19:28 ` [PATCH 3/3] vfio/type1: Implement vma registration and restriction Alex Williamson
2021-02-12 22:47 ` kernel test robot
2021-02-12 20:57 ` [PATCH 0/3] vfio: Device memory DMA mapping improvements Jason Gunthorpe
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=20210218011209.GB4247@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.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