From: "Liu, Yi L" <yi.l.liu@intel.com>
To: Auger Eric <eric.auger@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>
Cc: "david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>,
"tianyu.lan@intel.com" <tianyu.lan@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Tian, Jun J" <jun.j.tian@intel.com>,
"Sun, Yi Y" <yi.y.sun@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Yi Sun <yi.y.sun@linux.intel.com>
Subject: RE: [RFC v1 08/18] vfio/pci: add vfio bind/unbind_gpasid implementation
Date: Wed, 10 Jul 2019 12:30:33 +0000 [thread overview]
Message-ID: <A2975661238FB949B60364EF0F2C257439F2A761@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <cac2a42e-c152-e715-451f-7a19ca3e19ca@redhat.com>
> From: Auger Eric [mailto:eric.auger@redhat.com]
> Sent: Tuesday, July 9, 2019 4:38 PM
> Subject: Re: [RFC v1 08/18] vfio/pci: add vfio bind/unbind_gpasid implementation
>
> Hi Liu,
>
> On 7/5/19 1:01 PM, Liu Yi L wrote:
> > This patch adds vfio implementation PCIPASIDOps.bind_gpasid/unbind_pasid().
> > These two functions are used to propagate guest pasid bind and unbind
> > requests to host via vfio container ioctl.
> >
> > Cc: Kevin Tian <kevin.tian@intel.com>
> > Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > Cc: Peter Xu <peterx@redhat.com>
> > Cc: Eric Auger <eric.auger@redhat.com>
> > Cc: Yi Sun <yi.y.sun@linux.intel.com>
> > Cc: David Gibson <david@gibson.dropbear.id.au>
> > Signed-off-by: Liu Yi L <yi.l.liu@intel.com>
> > ---
> > hw/vfio/pci.c | 54
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 54 insertions(+)
> >
> > diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c index ab184ad..892b46c
> > 100644
> > --- a/hw/vfio/pci.c
> > +++ b/hw/vfio/pci.c
> > @@ -2744,9 +2744,63 @@ static int vfio_pci_device_request_pasid_free(PCIBus
> *bus,
> > return ret;
> > }
> >
> > +static void vfio_pci_device_bind_gpasid(PCIBus *bus, int32_t devfn,
> > + struct gpasid_bind_data
> > +*g_bind_data) {
> > + PCIDevice *pdev = bus->devices[devfn];
> > + VFIOPCIDevice *vdev = DO_UPCAST(VFIOPCIDevice, pdev, pdev);
> > + VFIOContainer *container = vdev->vbasedev.group->container;
> > + struct vfio_iommu_type1_bind *bind;
> > + struct vfio_iommu_type1_bind_guest_pasid *bind_guest_pasid;
> > + unsigned long argsz;
> > +
> > + argsz = sizeof(*bind) + sizeof(*bind_guest_pasid);
> > + bind = g_malloc0(argsz);
> > + bind->argsz = argsz;
> > + bind->bind_type = VFIO_IOMMU_BIND_GUEST_PASID;
> > + bind_guest_pasid = (struct vfio_iommu_type1_bind_guest_pasid *) &bind-
> >data;
> > + bind_guest_pasid->bind_data = *g_bind_data;
> > +
> > + rcu_read_lock();
> why do you need the rcu_read_lock?
> > + if (ioctl(container->fd, VFIO_IOMMU_BIND, bind) != 0) {
> > + error_report("vfio_pci_device_bind_gpasid:"
> > + " bind failed, contanier: %p", container);
> container
nice catch. :-)
> > + }
> > + rcu_read_unlock();
> > + g_free(bind);
> > +}
> > +
> > +static void vfio_pci_device_unbind_gpasid(PCIBus *bus, int32_t devfn,
> > + struct gpasid_bind_data
> > +*g_bind_data) {
> > + PCIDevice *pdev = bus->devices[devfn];
> > + VFIOPCIDevice *vdev = DO_UPCAST(VFIOPCIDevice, pdev, pdev);
> > + VFIOContainer *container = vdev->vbasedev.group->container;
> > + struct vfio_iommu_type1_bind *bind;
> > + struct vfio_iommu_type1_bind_guest_pasid *bind_guest_pasid;
> > + unsigned long argsz;
> > +
> > + argsz = sizeof(*bind) + sizeof(*bind_guest_pasid);
> > + bind = g_malloc0(argsz);
> > + bind->argsz = argsz;
> > + bind->bind_type = VFIO_IOMMU_BIND_GUEST_PASID;
> > + bind_guest_pasid = (struct vfio_iommu_type1_bind_guest_pasid *) &bind-
> >data;
> > + bind_guest_pasid->bind_data = *g_bind_data;
> > +
> > + rcu_read_lock();
> > + if (ioctl(container->fd, VFIO_IOMMU_UNBIND, bind) != 0) {
> > + error_report("vfio_pci_device_unbind_gpasid:"
> > + " unbind failed, contanier: %p", container);
> container
oops, Thanks,
> > + }
> > + rcu_read_unlock();
> > + g_free(bind);
> > +}
> > +
> > static PCIPASIDOps vfio_pci_pasid_ops = {
> > .alloc_pasid = vfio_pci_device_request_pasid_alloc,
> > .free_pasid = vfio_pci_device_request_pasid_free,
> > + .bind_gpasid = vfio_pci_device_bind_gpasid,
> > + .unbind_gpasid = vfio_pci_device_unbind_gpasid,
> > };
> >
> > static void vfio_realize(PCIDevice *pdev, Error **errp)
> >
>
> Thanks
>
> Eric
Yi Liu
next prev parent reply other threads:[~2019-07-10 12:30 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 11:01 [RFC v1 00/18] intel_iommu: expose Shared Virtual Addressing to VM Liu Yi L
2019-07-05 11:01 ` [RFC v1 01/18] linux-headers: import iommu.h from kernel Liu Yi L
2019-07-05 11:01 ` [RFC v1 02/18] linux-headers: import vfio.h " Liu Yi L
2019-07-09 1:58 ` Peter Xu
2019-07-09 8:37 ` Auger Eric
2019-07-10 12:31 ` Liu, Yi L
2019-07-10 12:29 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 03/18] hw/pci: introduce PCIPASIDOps to PCIDevice Liu Yi L
2019-07-09 2:12 ` Peter Xu
2019-07-09 10:41 ` Auger Eric
2019-07-10 11:08 ` Liu, Yi L
2019-07-11 3:51 ` david
2019-07-11 7:13 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 04/18] intel_iommu: add "sm_model" option Liu Yi L
2019-07-09 2:15 ` Peter Xu
2019-07-10 12:14 ` Liu, Yi L
2019-07-11 1:03 ` Peter Xu
2019-07-11 6:25 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 05/18] vfio/pci: add pasid alloc/free implementation Liu Yi L
2019-07-09 2:23 ` Peter Xu
2019-07-10 12:16 ` Liu, Yi L
2019-07-15 2:55 ` David Gibson
2019-07-16 10:25 ` Liu, Yi L
2019-07-17 3:06 ` David Gibson
2019-07-22 7:02 ` Liu, Yi L
2019-07-23 3:57 ` David Gibson
2019-07-24 4:57 ` Liu, Yi L
2019-07-24 9:33 ` Auger Eric
2019-07-25 3:40 ` David Gibson
2019-07-26 5:18 ` Liu, Yi L
2019-08-02 7:36 ` Auger Eric
2019-07-05 11:01 ` [RFC v1 06/18] intel_iommu: support virtual command emulation and pasid request Liu Yi L
2019-07-09 3:19 ` Peter Xu
2019-07-10 11:51 ` Liu, Yi L
2019-07-11 1:13 ` Peter Xu
2019-07-11 6:59 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 07/18] hw/pci: add pci_device_bind/unbind_gpasid Liu Yi L
2019-07-09 8:37 ` Auger Eric
2019-07-10 12:18 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 08/18] vfio/pci: add vfio bind/unbind_gpasid implementation Liu Yi L
2019-07-09 8:37 ` Auger Eric
2019-07-10 12:30 ` Liu, Yi L [this message]
2019-07-05 11:01 ` [RFC v1 09/18] intel_iommu: process pasid cache invalidation Liu Yi L
2019-07-09 4:47 ` Peter Xu
2019-07-11 6:22 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 10/18] intel_iommu: tag VTDAddressSpace instance with PASID Liu Yi L
2019-07-09 6:12 ` Peter Xu
2019-07-11 7:24 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 11/18] intel_iommu: create VTDAddressSpace per BDF+PASID Liu Yi L
2019-07-09 6:39 ` Peter Xu
2019-07-11 8:13 ` Liu, Yi L
2019-07-05 11:01 ` [RFC v1 12/18] intel_iommu: bind/unbind guest page table to host Liu Yi L
2019-07-05 11:01 ` [RFC v1 13/18] intel_iommu: flush pasid cache after a DSI context cache flush Liu Yi L
2019-07-05 11:01 ` [RFC v1 14/18] hw/pci: add flush_pasid_iotlb() in PCIPASIDOps Liu Yi L
2019-07-05 11:01 ` [RFC v1 15/18] vfio/pci: adds support for PASID-based iotlb flush Liu Yi L
2019-07-05 11:01 ` [RFC v1 16/18] intel_iommu: add PASID-based iotlb invalidation support Liu Yi L
2019-07-05 11:01 ` [RFC v1 17/18] intel_iommu: propagate PASID-based iotlb flush to host Liu Yi L
2019-07-05 11:01 ` [RFC v1 18/18] intel_iommu: do not passdown pasid bind for PASID #0 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=A2975661238FB949B60364EF0F2C257439F2A761@SHSMSX104.ccr.corp.intel.com \
--to=yi.l.liu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger@redhat.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jun.j.tian@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tianyu.lan@intel.com \
--cc=yi.y.sun@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 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).