All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Liu, Yi L" <yi.l.liu@intel.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"cohuck@redhat.com" <cohuck@redhat.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"yi.y.sun@linux.intel.com" <yi.y.sun@linux.intel.com>,
	"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
	"mjrosato@linux.ibm.com" <mjrosato@linux.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [RFC v2 03/11] vfio: Set device->group in helper function
Date: Tue, 29 Nov 2022 09:27:28 -0400	[thread overview]
Message-ID: <Y4YIwH5TT88D3vIQ@nvidia.com> (raw)
In-Reply-To: <BL1PR11MB5271B4790C8C90FDFF813DF08C129@BL1PR11MB5271.namprd11.prod.outlook.com>

On Tue, Nov 29, 2022 at 02:04:01AM +0000, Tian, Kevin wrote:
> > From: Liu, Yi L <yi.l.liu@intel.com>
> > Sent: Monday, November 28, 2022 5:17 PM
> > 
> > 
> > >> +static int vfio_device_set_group(struct vfio_device *device,
> > >> +				 enum vfio_group_type type)
> > >>   {
> > >> -	int ret;
> > >> +	struct vfio_group *group;
> > >> +
> > >> +	if (type == VFIO_IOMMU)
> > >> +		group = vfio_group_find_or_alloc(device->dev);
> > >> +	else
> > >> +		group = vfio_noiommu_group_alloc(device->dev, type);
> > >
> > > Do we need a WARN_ON(type == VFIO_NO_IOMMU)?
> > 
> > do you mean a heads-up to user? if so, there is already a warn in
> > vfio_group_find_or_alloc() and vfio_group_ioctl_get_device_fd()
> > 
> 
> I meant that VFIO_NO_IOMMU is not expected as a passed in type.
> It's implicitly handled by vfio_group_find_or_alloc() which calls
> vfio_noiommu_group_alloc() plus kernel taint.

The code is simple enough to check the two callers, I don't know if we
need a WARN_ON - and it isn't actually wrong to call
vfio_noiommu_group_alloc() for a VFIO_NO_IOMMU..

Jason

  reply	other threads:[~2022-11-29 13:27 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 [this message]
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
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=Y4YIwH5TT88D3vIQ@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.