All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <alex.williamson@redhat.com>, <kevin.tian@intel.com>,
	<eric.auger@redhat.com>, <cohuck@redhat.com>,
	<nicolinc@nvidia.com>, <yi.y.sun@linux.intel.com>,
	<chao.p.peng@linux.intel.com>, <mjrosato@linux.ibm.com>,
	<kvm@vger.kernel.org>
Subject: Re: [RFC v2 11/11] vfio: Move vfio group specific code into group.c
Date: Fri, 25 Nov 2022 16:45:07 +0800	[thread overview]
Message-ID: <e4f8c00f-809c-01d8-c104-06bf84041116@intel.com> (raw)
In-Reply-To: <Y3+BXHd7dEL7FYqz@nvidia.com>

On 2022/11/24 22:36, Jason Gunthorpe wrote:
> On Thu, Nov 24, 2022 at 04:27:02AM -0800, Yi Liu wrote:
>> This prepares for compiling out vfio group after vfio device cdev is
>> added. No vfio_group decode code should be in vfio_main.c.
>>
>> No functional change is intended.
>>
>> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
>> ---
>>   drivers/vfio/Makefile    |   1 +
>>   drivers/vfio/group.c     | 842 +++++++++++++++++++++++++++++++++++++++
>>   drivers/vfio/vfio.h      |  17 +
>>   drivers/vfio/vfio_main.c | 830 +-------------------------------------
>>   4 files changed, 863 insertions(+), 827 deletions(-)
>>   create mode 100644 drivers/vfio/group.c
> 
> vfio_device_open_file() should be moved into group.c as well and
> export vfio_device_open/close() instead

also need export vfio_device_ops as well:-)

-- 
Regards,
Yi Liu

  reply	other threads:[~2022-11-25  8:45 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 12:26 [RFC v2 00/11] Move group specific code into group.c Yi Liu
2022-11-24 12:26 ` [RFC v2 01/11] vfio: Simplify vfio_create_group() Yi Liu
2022-11-28  7:57   ` Tian, Kevin
2022-11-24 12:26 ` [RFC v2 02/11] vfio: Move the sanity check of the group to vfio_create_group() Yi Liu
2022-11-28  8:05   ` Tian, Kevin
2022-11-24 12:26 ` [RFC v2 03/11] vfio: Set device->group in helper function Yi Liu
2022-11-24 13:17   ` Jason Gunthorpe
2022-11-24 13:50     ` Yi Liu
2022-11-28  8:08   ` Tian, Kevin
2022-11-28  9:17     ` Yi Liu
2022-11-29  2:04       ` Tian, Kevin
2022-11-29 13:27         ` Jason Gunthorpe
2022-11-30  7:09           ` Yi Liu
2022-11-24 12:26 ` [RFC v2 04/11] vfio: Wrap group codes to be helpers for __vfio_register_dev() and unregister Yi Liu
2022-11-28  8:11   ` Tian, Kevin
2022-11-28  9:17     ` Yi Liu
2022-11-24 12:26 ` [RFC v2 05/11] vfio: Make vfio_device_open() group agnostic Yi Liu
2022-11-28  8:17   ` Tian, Kevin
2022-11-28  9:19     ` Yi Liu
2022-12-01  7:08       ` Yi Liu
2022-12-01 12:48         ` Jason Gunthorpe
2022-11-24 12:26 ` [RFC v2 06/11] vfio: Move device open/close code to be helpfers Yi Liu
2022-11-28  8:21   ` Tian, Kevin
2022-11-28  9:27     ` Yi Liu
2022-11-24 12:26 ` [RFC v2 07/11] vfio: Swap order of vfio_device_container_register() and open_device() Yi Liu
2022-11-28  8:27   ` Tian, Kevin
2022-11-28  9:28     ` Yi Liu
2022-11-24 12:26 ` [RFC v2 08/11] vfio: Refactor vfio_device_first_open() and _last_close() Yi Liu
2022-11-24 14:56   ` Jason Gunthorpe
2022-11-25  8:57     ` Yi Liu
2022-11-25 12:37       ` Jason Gunthorpe
2022-11-25 14:06         ` Yi Liu
2022-11-25 14:15           ` Jason Gunthorpe
2022-11-25 14:33             ` Yi Liu
2022-11-28  8:31   ` Tian, Kevin
2022-11-24 12:27 ` [RFC v2 09/11] vfio: Wrap vfio group module init/clean code into helpers Yi Liu
2022-11-28  8:36   ` Tian, Kevin
2022-11-24 12:27 ` [RFC v2 10/11] vfio: Refactor dma APIs for emulated devices Yi Liu
2022-11-24 22:05   ` kernel test robot
2022-11-28  8:42   ` Tian, Kevin
2022-11-24 12:27 ` [RFC v2 11/11] vfio: Move vfio group specific code into group.c Yi Liu
2022-11-24 14:36   ` Jason Gunthorpe
2022-11-25  8:45     ` Yi Liu [this message]
2022-11-28 21:21   ` kernel test robot

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=e4f8c00f-809c-01d8-c104-06bf84041116@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.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.