From: Jason Gunthorpe <jgg@nvidia.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [PATCH v2 0/5] Update vfio_group to use the modern cdev lifecycle
Date: Fri, 15 Oct 2021 08:41:15 -0300 [thread overview]
Message-ID: <20211015114115.GE2744544@nvidia.com> (raw)
In-Reply-To: <PH0PR11MB5658A21677BA355E1A44A6C9C3B99@PH0PR11MB5658.namprd11.prod.outlook.com>
On Fri, Oct 15, 2021 at 06:03:18AM +0000, Liu, Yi L wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Wednesday, October 13, 2021 10:28 PM
> >
> > These days drivers with state should use cdev_device_add() and
> > cdev_device_del() to manage the cdev and sysfs lifetime. This simple
> > pattern ties all the state (vfio, dev, and cdev) together in one memory
> > structure and uses container_of() to navigate between the layers.
> >
> > This is a followup to the discussion here:
> >
> > https://lore.kernel.org/kvm/20210921155705.GN327412@nvidia.com/
> >
> > This builds on Christoph's work to revise how the vfio_group works and is
> > against the latest VFIO tree.
>
> Jason, do you have a github branch includes these changes and also
> Christoph's revise work. I would like to rebase the iommufd things on
> top of it. Also, want to have a try to see if any regression.
https://github.com/jgunthorpe/linux/commits/vfio_group_cdev
Jason
next prev parent reply other threads:[~2021-10-15 11:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 14:27 [PATCH v2 0/5] Update vfio_group to use the modern cdev lifecycle Jason Gunthorpe
2021-10-13 14:27 ` [PATCH v2 1/5] vfio: Delete vfio_get/put_group from vfio_iommu_group_notifier() Jason Gunthorpe
2021-10-13 16:04 ` Christoph Hellwig
2021-10-13 14:27 ` [PATCH v2 2/5] vfio: Do not open code the group list search in vfio_create_group() Jason Gunthorpe
2021-10-13 16:05 ` Christoph Hellwig
2021-10-13 14:27 ` [PATCH v2 3/5] vfio: Don't leak a group reference if the group already exists Jason Gunthorpe
2021-10-13 16:09 ` Christoph Hellwig
2021-10-13 16:18 ` Jason Gunthorpe
2021-10-14 2:08 ` Tian, Kevin
2021-10-13 14:27 ` [PATCH v2 4/5] vfio: Use a refcount_t instead of a kref in the vfio_group Jason Gunthorpe
2021-10-13 16:10 ` Christoph Hellwig
2021-10-13 14:27 ` [PATCH v2 5/5] vfio: Use cdev_device_add() instead of device_create() Jason Gunthorpe
2021-10-13 17:08 ` Christoph Hellwig
2021-10-13 17:42 ` Jason Gunthorpe
2021-10-14 21:04 ` Alex Williamson
2021-10-14 2:09 ` Tian, Kevin
2021-10-15 6:03 ` [PATCH v2 0/5] Update vfio_group to use the modern cdev lifecycle Liu, Yi L
2021-10-15 11:41 ` Jason Gunthorpe [this message]
2021-10-15 11:43 ` Liu, Yi L
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=20211015114115.GE2744544@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=hch@lst.de \
--cc=kevin.tian@intel.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