qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: pbonzini@redhat.com, kraxel@redhat.com, cjia@nvidia.com,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, kevin.tian@intel.com,
	jike.song@intel.com, bjsdjshi@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v9 06/12] vfio_pci: Update vfio_pci to use vfio_info_add_capability()
Date: Mon, 24 Oct 2016 15:37:15 -0600	[thread overview]
Message-ID: <20161024153715.57f1cde7@t450s.home> (raw)
In-Reply-To: <77c0e8bf-1a61-c009-ab18-a62d9fe2f8a0@nvidia.com>

On Tue, 25 Oct 2016 02:52:39 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:

> On 10/21/2016 12:54 AM, Alex Williamson wrote:
> > On Tue, 18 Oct 2016 02:52:06 +0530
> > Kirti Wankhede <kwankhede@nvidia.com> wrote:
> >   
> >> Update msix_sparse_mmap_cap() to use vfio_info_add_capability()
> >> Update region type capability to use vfio_info_add_capability()
> >> Can't split this commit for MSIx and region_type cap since there is a
> >> common code which need to be updated for both the cases.
> >>
> >> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> >> Signed-off-by: Neo Jia <cjia@nvidia.com>
> >> Change-Id: I52bb28c7875a6da5a79ddad1843e6088aff58a45
> >> ---
> >>  drivers/vfio/pci/vfio_pci.c | 72 +++++++++++++++++----------------------------
> >>  1 file changed, 27 insertions(+), 45 deletions(-)
> >>
> >> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> >> index d624a527777f..1ec0565b48ea 100644
> >> --- a/drivers/vfio/pci/vfio_pci.c
> >> +++ b/drivers/vfio/pci/vfio_pci.c
> >> @@ -556,12 +556,12 @@ static int vfio_pci_for_each_slot_or_bus(struct pci_dev *pdev,
> >>  }
> >>  
> >>  static int msix_sparse_mmap_cap(struct vfio_pci_device *vdev,
> >> +				struct vfio_region_info *info,
> >>  				struct vfio_info_cap *caps)
> >>  {
> >> -	struct vfio_info_cap_header *header;
> >>  	struct vfio_region_info_cap_sparse_mmap *sparse;
> >>  	size_t end, size;
> >> -	int nr_areas = 2, i = 0;
> >> +	int nr_areas = 2, i = 0, ret;
> >>  
> >>  	end = pci_resource_len(vdev->pdev, vdev->msix_bar);
> >>  
> >> @@ -572,13 +572,10 @@ static int msix_sparse_mmap_cap(struct vfio_pci_device *vdev,
> >>  
> >>  	size = sizeof(*sparse) + (nr_areas * sizeof(*sparse->areas));
> >>  
> >> -	header = vfio_info_cap_add(caps, size,
> >> -				   VFIO_REGION_INFO_CAP_SPARSE_MMAP, 1);
> >> -	if (IS_ERR(header))
> >> -		return PTR_ERR(header);
> >> +	sparse = kzalloc(size, GFP_KERNEL);
> >> +	if (!sparse)
> >> +		return -ENOMEM;
> >>  
> >> -	sparse = container_of(header,
> >> -			      struct vfio_region_info_cap_sparse_mmap, header);
> >>  	sparse->nr_areas = nr_areas;
> >>  
> >>  	if (vdev->msix_offset & PAGE_MASK) {
> >> @@ -594,26 +591,11 @@ static int msix_sparse_mmap_cap(struct vfio_pci_device *vdev,
> >>  		i++;
> >>  	}
> >>  
> >> -	return 0;
> >> -}
> >> -
> >> -static int region_type_cap(struct vfio_pci_device *vdev,
> >> -			   struct vfio_info_cap *caps,
> >> -			   unsigned int type, unsigned int subtype)
> >> -{
> >> -	struct vfio_info_cap_header *header;
> >> -	struct vfio_region_info_cap_type *cap;
> >> -
> >> -	header = vfio_info_cap_add(caps, sizeof(*cap),
> >> -				   VFIO_REGION_INFO_CAP_TYPE, 1);
> >> -	if (IS_ERR(header))
> >> -		return PTR_ERR(header);
> >> +	ret = vfio_info_add_capability(info, caps,
> >> +				      VFIO_REGION_INFO_CAP_SPARSE_MMAP, sparse);
> >> +	kfree(sparse);
> >>  
> >> -	cap = container_of(header, struct vfio_region_info_cap_type, header);
> >> -	cap->type = type;
> >> -	cap->subtype = subtype;
> >> -
> >> -	return 0;
> >> +	return ret;
> >>  }
> >>  
> >>  int vfio_pci_register_dev_region(struct vfio_pci_device *vdev,
> >> @@ -704,7 +686,8 @@ static long vfio_pci_ioctl(void *device_data,
> >>  			if (vdev->bar_mmap_supported[info.index]) {
> >>  				info.flags |= VFIO_REGION_INFO_FLAG_MMAP;
> >>  				if (info.index == vdev->msix_bar) {
> >> -					ret = msix_sparse_mmap_cap(vdev, &caps);
> >> +					ret = msix_sparse_mmap_cap(vdev, &info,
> >> +								   &caps);
> >>  					if (ret)
> >>  						return ret;
> >>  				}
> >> @@ -752,6 +735,9 @@ static long vfio_pci_ioctl(void *device_data,
> >>  
> >>  			break;
> >>  		default:
> >> +		{
> >> +			struct vfio_region_info_cap_type cap_type;
> >> +
> >>  			if (info.index >=
> >>  			    VFIO_PCI_NUM_REGIONS + vdev->num_regions)
> >>  				return -EINVAL;
> >> @@ -762,27 +748,23 @@ static long vfio_pci_ioctl(void *device_data,
> >>  			info.size = vdev->region[i].size;
> >>  			info.flags = vdev->region[i].flags;
> >>  
> >> -			ret = region_type_cap(vdev, &caps,
> >> -					      vdev->region[i].type,
> >> -					      vdev->region[i].subtype);
> >> +			cap_type.type = vdev->region[i].type;
> >> +			cap_type.subtype = vdev->region[i].subtype;
> >> +
> >> +			ret = vfio_info_add_capability(&info, &caps,
> >> +						      VFIO_REGION_INFO_CAP_TYPE,
> >> +						      &cap_type);
> >>  			if (ret)
> >>  				return ret;
> >> +
> >> +		}
> >>  		}
> >>  
> >> -		if (caps.size) {
> >> -			info.flags |= VFIO_REGION_INFO_FLAG_CAPS;
> >> -			if (info.argsz < sizeof(info) + caps.size) {
> >> -				info.argsz = sizeof(info) + caps.size;
> >> -				info.cap_offset = 0;
> >> -			} else {
> >> -				vfio_info_cap_shift(&caps, sizeof(info));
> >> -				if (copy_to_user((void __user *)arg +
> >> -						  sizeof(info), caps.buf,
> >> -						  caps.size)) {
> >> -					kfree(caps.buf);
> >> -					return -EFAULT;
> >> -				}
> >> -				info.cap_offset = sizeof(info);  
> > 
> > I prefer the case above, I'm fine with breaking out helpers to build a
> > buffer containing the capability chain, but I would rather have the
> > caller manage placing that back into the return structure.  That also
> > allows the helper to be independent of the structure we're operating
> > on, it could be a region_info, irq_info, device_info, etc.  It only
> > needs to know the layout of the capability type we're trying to add,
> > not the info structure itself.  Thanks,
> >   
> 
> The capability feature is for region_info (VFIO_REGION_INFO_FLAG_CAPS),
> then structure we are operating couldn't be irq_info or device_info, right?

My point was that I prefer the caller managing region_info.flags and
region_info.cap_offset, the helper only managing creating the
capability chain within the buffer.  There is a namespace conflict for
the various capabilities though, each foo_info has their own space,
which can conflict, which make make a common helper impractical.
Thanks,

Alex

  reply	other threads:[~2016-10-24 21:37 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 21:22 [Qemu-devel] [PATCH v9 00/12] Add Mediated device support Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 01/12] vfio: Mediated device Core driver Kirti Wankhede
2016-10-18 23:16   ` Alex Williamson
2016-10-19 19:16     ` Kirti Wankhede
2016-10-19 22:20       ` Alex Williamson
2016-10-20  7:23   ` Jike Song
2016-10-20 17:12     ` Alex Williamson
2016-10-21  2:41       ` Jike Song
2016-10-27  5:56       ` Jike Song
2016-10-26  6:52   ` Tian, Kevin
2016-10-26 14:58     ` Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 02/12] vfio: VFIO based driver for Mediated devices Kirti Wankhede
2016-10-26  6:57   ` Tian, Kevin
2016-10-26 15:01     ` Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 03/12] vfio: Rearrange functions to get vfio_group from dev Kirti Wankhede
2016-10-19 17:26   ` Alex Williamson
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 04/12] vfio iommu: Add support for mediated devices Kirti Wankhede
2016-10-19 21:02   ` Alex Williamson
2016-10-20 20:17     ` Kirti Wankhede
2016-10-24  2:32       ` Alex Williamson
2016-10-26  7:19         ` Tian, Kevin
2016-10-26 15:06           ` Kirti Wankhede
2016-10-26  7:53     ` Tian, Kevin
2016-10-26 15:16       ` Alex Williamson
2016-10-26  7:54     ` Tian, Kevin
2016-10-26 15:19       ` Alex Williamson
2016-10-21  7:49   ` Jike Song
2016-10-21 14:36     ` Alex Williamson
2016-10-24 10:35       ` Kirti Wankhede
2016-10-27  7:20   ` Alexey Kardashevskiy
2016-10-27 12:31     ` Kirti Wankhede
2016-10-27 14:30       ` Alex Williamson
2016-10-27 15:59         ` Kirti Wankhede
2016-10-28  2:18       ` Alexey Kardashevskiy
2016-11-01 14:01         ` Kirti Wankhede
2016-11-02  1:24           ` Alexey Kardashevskiy
2016-11-02  3:29             ` Kirti Wankhede
2016-11-02  4:09               ` Alexey Kardashevskiy
2016-11-02 12:21                 ` Jike Song
2016-11-02 12:41                   ` Kirti Wankhede
2016-11-02 13:00                     ` Jike Song
2016-11-02 13:18                       ` Kirti Wankhede
2016-11-02 13:35                         ` Jike Song
2016-11-03  4:29                         ` Alexey Kardashevskiy
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 05/12] vfio: Introduce common function to add capabilities Kirti Wankhede
2016-10-20 19:24   ` Alex Williamson
2016-10-24 21:27     ` Kirti Wankhede
2016-10-24 21:39       ` Alex Williamson
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 06/12] vfio_pci: Update vfio_pci to use vfio_info_add_capability() Kirti Wankhede
2016-10-20 19:24   ` Alex Williamson
2016-10-24 21:22     ` Kirti Wankhede
2016-10-24 21:37       ` Alex Williamson [this message]
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 07/12] vfio: Introduce vfio_set_irqs_validate_and_prepare() Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 08/12] vfio_pci: Updated to use vfio_set_irqs_validate_and_prepare() Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 09/12] vfio_platform: " Kirti Wankhede
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 10/12] vfio: Add function to get device_api string from vfio_device_info.flags Kirti Wankhede
2016-10-20 19:34   ` Alex Williamson
2016-10-20 20:29     ` Kirti Wankhede
2016-10-20 21:05       ` Alex Williamson
2016-10-20 21:14         ` Kirti Wankhede
2016-10-20 21:22           ` Alex Williamson
2016-10-21  3:00             ` Kirti Wankhede
2016-10-21  3:20               ` Alex Williamson
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 11/12] docs: Add Documentation for Mediated devices Kirti Wankhede
2016-10-25 16:17   ` Alex Williamson
2016-10-17 21:22 ` [Qemu-devel] [PATCH v9 12/12] docs: Sample driver to demonstrate how to use Mediated device framework Kirti Wankhede
2016-10-18  2:54   ` Dong Jia Shi
2016-10-18 17:17     ` Alex Williamson
2016-10-19 19:19       ` Kirti Wankhede
2016-10-17 21:41 ` [Qemu-devel] [PATCH v9 00/12] Add Mediated device support Alex Williamson
2016-10-24  7:07 ` Jike Song
2016-12-05 17:44   ` Gerd Hoffmann
2016-12-06  2:24     ` Jike Song
2016-12-07 14:40       ` Gerd Hoffmann

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=20161024153715.57f1cde7@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=cjia@nvidia.com \
    --cc=jike.song@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).