All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: alex.williamson@redhat.com, kevin.tian@intel.com,
	cohuck@redhat.com, eric.auger@redhat.com, nicolinc@nvidia.com,
	kvm@vger.kernel.org, mjrosato@linux.ibm.com,
	chao.p.peng@linux.intel.com, yi.y.sun@linux.intel.com
Subject: Re: [PATCH 00/10] Move group specific code into group.c
Date: Fri, 2 Dec 2022 10:44:30 -0400	[thread overview]
Message-ID: <Y4oPTjCTlQ/ozjoZ@nvidia.com> (raw)
In-Reply-To: <86c4f504-a0b2-969c-c2c6-5fd43deb6627@intel.com>

On Fri, Dec 02, 2022 at 09:57:45PM +0800, Yi Liu wrote:
> On 2022/12/2 04:39, Jason Gunthorpe wrote:
> > On Thu, Dec 01, 2022 at 06:55:25AM -0800, Yi Liu wrote:
> > > With the introduction of iommufd[1], VFIO is towarding to provide device
> > > centric uAPI after adapting to iommufd. With this trend, existing VFIO
> > > group infrastructure is optional once VFIO converted to device centric.
> > > 
> > > This series moves the group specific code out of vfio_main.c, prepares
> > > for compiling group infrastructure out after adding vfio device cdev[2]
> > > 
> > > Complete code in below branch:
> > > 
> > > https://github.com/yiliu1765/iommufd/commits/vfio_group_split_v1
> > > 
> > > This is based on Jason's "Connect VFIO to IOMMUFD"[3] and my "Make mdev driver
> > > dma_unmap callback tolerant to unmaps come before device open"[4]
> > > 
> > > [1] https://lore.kernel.org/all/0-v5-4001c2997bd0+30c-iommufd_jgg@nvidia.com/
> > > [2] https://github.com/yiliu1765/iommufd/tree/wip/vfio_device_cdev
> > > [3] https://lore.kernel.org/kvm/0-v4-42cd2eb0e3eb+335a-vfio_iommufd_jgg@nvidia.com/
> > > [4] https://lore.kernel.org/kvm/20221129105831.466954-1-yi.l.liu@intel.com/
> > 
> > This looks good to me, and it applies OK to my branch here:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git/
> > 
> > Alex, if you ack this in the next few days I can include it in the
> > iommufd PR, otherwise it can go into the vfio tree in January
> > 
> > Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> > 
> 
> thanks. btw. I've updated my github to incorporate Kevin's nit and also
> r-b from you and Kevin.

Please rebase it on the above branch also

Thanks,
Jason

  reply	other threads:[~2022-12-02 14:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 14:55 [PATCH 00/10] Move group specific code into group.c Yi Liu
2022-12-01 14:55 ` [PATCH 01/10] vfio: Simplify vfio_create_group() Yi Liu
2022-12-01 14:55 ` [PATCH 02/10] vfio: Move the sanity check of the group to vfio_create_group() Yi Liu
2022-12-01 14:55 ` [PATCH 03/10] vfio: Create wrappers for group register/unregister Yi Liu
2022-12-01 14:55 ` [PATCH 04/10] vfio: Set device->group in helper function Yi Liu
2022-12-02  5:34   ` Tian, Kevin
2022-12-01 14:55 ` [PATCH 05/10] vfio: Swap order of vfio_device_container_register() and open_device() Yi Liu
2022-12-01 14:55 ` [PATCH 06/10] vfio: Move device open/close code to be helpfers Yi Liu
2022-12-02  5:44   ` Tian, Kevin
2022-12-02  6:37     ` Yi Liu
2022-12-01 14:55 ` [PATCH 07/10] vfio: Refactor vfio_device open and close Yi Liu
2022-12-02  6:15   ` Tian, Kevin
2022-12-02  6:37     ` Yi Liu
2022-12-02 15:07       ` Jason Gunthorpe
2022-12-02 21:58   ` Alex Williamson
2022-12-03 13:46     ` Yi Liu
2022-12-01 14:55 ` [PATCH 08/10] vfio: Wrap vfio group module init/clean code into helpers Yi Liu
2022-12-01 14:55 ` [PATCH 09/10] vfio: Refactor dma APIs for emulated devices Yi Liu
2022-12-01 14:55 ` [PATCH 10/10] vfio: Move vfio group specific code into group.c Yi Liu
2022-12-02  6:26   ` Tian, Kevin
2022-12-01 20:39 ` [PATCH 00/10] Move " Jason Gunthorpe
2022-12-02 13:57   ` Yi Liu
2022-12-02 14:44     ` Jason Gunthorpe [this message]
2022-12-02 23:12       ` Alex Williamson
2022-12-03 13:53         ` Yi Liu
2022-12-05 13:43           ` Jason Gunthorpe
2022-12-06  7:31           ` Yang, Lixiao
2022-12-07  4:12             ` He, Yu

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=Y4oPTjCTlQ/ozjoZ@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --cc=yi.y.sun@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.