From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kvm@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Tony Krowiak <akrowiak@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] vfio: Replace the DMA unmapping notifier with a callback
Date: Tue, 7 Jun 2022 19:40:05 -0300 [thread overview]
Message-ID: <20220607224005.GA805783@nvidia.com> (raw)
In-Reply-To: <20220607115752.GG1343366@nvidia.com>
On Tue, Jun 07, 2022 at 08:57:52AM -0300, Jason Gunthorpe wrote:
> On Tue, Jun 07, 2022 at 07:39:55AM +0200, Christoph Hellwig wrote:
>
> > > +static int vfio_iommu_notifier(struct notifier_block *nb, unsigned long action,
> > > + void *data)
> > > +{
> > > + struct vfio_device *vfio_device =
> > > + container_of(nb, struct vfio_device, iommu_nb);
> > > + struct vfio_iommu_type1_dma_unmap *unmap = data;
> >
> > Using the iommu type 1 UAPI structure in the core vfio code for a
> > subset of its field is kinda weird. But we can fix this later.
>
> Ah, I did type this in at one point.. It was small lets include it in
> this patch
Oh I got this explanation mixed up - forgot about this vesitgual bit
The patch is split in two: this patch removes the
vfio_iommu_type1_dma_unmap from all the drivers but leaves the type1
code as-is and bridges it here, the next patch changes the type1 code
to direcly call the op and deletes this function. So this weirdness is
fully deleted by the end of the series.
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
David Airlie <airlied@linux.ie>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Eric Farman <farman@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Jason Herne <jjherne@linux.ibm.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sven Schnelle <svens@linux.ibm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: [PATCH 1/2] vfio: Replace the DMA unmapping notifier with a callback
Date: Tue, 7 Jun 2022 19:40:05 -0300 [thread overview]
Message-ID: <20220607224005.GA805783@nvidia.com> (raw)
In-Reply-To: <20220607115752.GG1343366@nvidia.com>
On Tue, Jun 07, 2022 at 08:57:52AM -0300, Jason Gunthorpe wrote:
> On Tue, Jun 07, 2022 at 07:39:55AM +0200, Christoph Hellwig wrote:
>
> > > +static int vfio_iommu_notifier(struct notifier_block *nb, unsigned long action,
> > > + void *data)
> > > +{
> > > + struct vfio_device *vfio_device =
> > > + container_of(nb, struct vfio_device, iommu_nb);
> > > + struct vfio_iommu_type1_dma_unmap *unmap = data;
> >
> > Using the iommu type 1 UAPI structure in the core vfio code for a
> > subset of its field is kinda weird. But we can fix this later.
>
> Ah, I did type this in at one point.. It was small lets include it in
> this patch
Oh I got this explanation mixed up - forgot about this vesitgual bit
The patch is split in two: this patch removes the
vfio_iommu_type1_dma_unmap from all the drivers but leaves the type1
code as-is and bridges it here, the next patch changes the type1 code
to direcly call the op and deletes this function. So this weirdness is
fully deleted by the end of the series.
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kvm@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>,
Jason Herne <jjherne@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Tony Krowiak <akrowiak@linux.ibm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH 1/2] vfio: Replace the DMA unmapping notifier with a callback
Date: Tue, 7 Jun 2022 19:40:05 -0300 [thread overview]
Message-ID: <20220607224005.GA805783@nvidia.com> (raw)
In-Reply-To: <20220607115752.GG1343366@nvidia.com>
On Tue, Jun 07, 2022 at 08:57:52AM -0300, Jason Gunthorpe wrote:
> On Tue, Jun 07, 2022 at 07:39:55AM +0200, Christoph Hellwig wrote:
>
> > > +static int vfio_iommu_notifier(struct notifier_block *nb, unsigned long action,
> > > + void *data)
> > > +{
> > > + struct vfio_device *vfio_device =
> > > + container_of(nb, struct vfio_device, iommu_nb);
> > > + struct vfio_iommu_type1_dma_unmap *unmap = data;
> >
> > Using the iommu type 1 UAPI structure in the core vfio code for a
> > subset of its field is kinda weird. But we can fix this later.
>
> Ah, I did type this in at one point.. It was small lets include it in
> this patch
Oh I got this explanation mixed up - forgot about this vesitgual bit
The patch is split in two: this patch removes the
vfio_iommu_type1_dma_unmap from all the drivers but leaves the type1
code as-is and bridges it here, the next patch changes the type1 code
to direcly call the op and deletes this function. So this weirdness is
fully deleted by the end of the series.
Jason
next prev parent reply other threads:[~2022-06-07 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 0:34 [Intel-gfx] [PATCH 0/2] Remove the VFIO_IOMMU_NOTIFY_DMA_UNMAP notifier Jason Gunthorpe
2022-06-07 0:34 ` Jason Gunthorpe
2022-06-07 0:34 ` [Intel-gfx] [PATCH 1/2] vfio: Replace the DMA unmapping notifier with a callback Jason Gunthorpe
2022-06-07 0:34 ` Jason Gunthorpe
2022-06-07 5:39 ` [Intel-gfx] " Christoph Hellwig
2022-06-07 5:39 ` Christoph Hellwig
2022-06-07 11:57 ` [Intel-gfx] " Jason Gunthorpe
2022-06-07 11:57 ` Jason Gunthorpe
2022-06-07 11:57 ` Jason Gunthorpe
2022-06-07 22:40 ` Jason Gunthorpe [this message]
2022-06-07 22:40 ` Jason Gunthorpe
2022-06-07 22:40 ` Jason Gunthorpe
2022-06-07 0:34 ` [Intel-gfx] [PATCH 2/2] vfio: Replace the iommu notifier with a device list Jason Gunthorpe
2022-06-07 0:34 ` Jason Gunthorpe
2022-06-07 5:44 ` [Intel-gfx] " Christoph Hellwig
2022-06-07 5:44 ` Christoph Hellwig
2022-06-07 11:57 ` [Intel-gfx] " Jason Gunthorpe
2022-06-07 11:57 ` Jason Gunthorpe
2022-06-07 11:57 ` Jason Gunthorpe
2022-06-07 1:06 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Remove the VFIO_IOMMU_NOTIFY_DMA_UNMAP notifier Patchwork
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=20220607224005.GA805783@nvidia.com \
--to=jgg@nvidia.com \
--cc=agordeev@linux.ibm.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=rodrigo.vivi@intel.com \
--cc=svens@linux.ibm.com \
--cc=vneethv@linux.ibm.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.