All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: christian.koenig@amd.com
Cc: David1.Zhou@amd.com, hch@infradead.org, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH 4/6] drm/amdgpu: add checks if DMA-buf P2P is supported
Date: Wed, 11 Mar 2020 11:38:35 -0300	[thread overview]
Message-ID: <20200311143835.GD31668@ziepe.ca> (raw)
In-Reply-To: <848c2f50-1529-f036-69cd-5104b7ebe27b@gmail.com>

On Wed, Mar 11, 2020 at 03:33:01PM +0100, Christian König wrote:
> Am 11.03.20 um 15:04 schrieb Jason Gunthorpe:
> > On Wed, Mar 11, 2020 at 02:51:56PM +0100, Christian König wrote:
> > > Check if we can do peer2peer on the PCIe bus.
> > > 
> > > Signed-off-by: Christian König <christian.koenig@amd.com>
> > >   drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 4 ++++
> > >   1 file changed, 4 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
> > > index aef12ee2f1e3..bbf67800c8a6 100644
> > > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
> > > @@ -38,6 +38,7 @@
> > >   #include <drm/amdgpu_drm.h>
> > >   #include <linux/dma-buf.h>
> > >   #include <linux/dma-fence-array.h>
> > > +#include <linux/pci-p2pdma.h>
> > >   /**
> > >    * amdgpu_gem_prime_vmap - &dma_buf_ops.vmap implementation
> > > @@ -179,6 +180,9 @@ static int amdgpu_dma_buf_attach(struct dma_buf *dmabuf,
> > >   	struct amdgpu_device *adev = amdgpu_ttm_adev(bo->tbo.bdev);
> > >   	int r;
> > > +	if (pci_p2pdma_distance_many(adev->pdev, &attach->dev, 1, true) < 0)
> > > +		attach->peer2peer = false;
> > > +
> > Are there other related patches than this series?
> > 
> > p2p dma mapping needs to be done in common code, in p2pdma.c - ie this
> > open coding is missing the bus_offset stuff, at least.
> 
> Yeah, I'm aware of this. But I couldn't find a better way for now.

Well, it isn't optional :)
 
> > I really do not want to see drivers open code this stuff.
> > 
> > We already have a p2pdma API for handling the struct page case, so I
> > suggest adding some new p2pdma API to handle this for non-struct page
> > cases.
> > 
> > ie some thing like:
> > 
> > int 'p2pdma map bar'(
> >     struct pci_device *source,
> >     unsigned int source_bar_number,
> >     struct pci_device *dest,
> >     physaddr&len *array_of_offsets & length pairs into source bar,
> >     struct scatterlist *output_sgl)
> 
> Well that's exactly what I have to avoid since I don't have the array of
> offsets around and want to avoid constructing it.

Maybe it doesn't need an array of offsets - just a single offset and
callers can iterate the API?

> Similar problem for dma_map_resource(). My example does this on demand, but
> essentially we also have use cases where this is done only once.

I'm not sure if this is portable. Does any IOMMU HW need to know P2P
is happening to setup successfully? We currently support such a narrow
scope of HW for P2P..

> Ideally we would have some function to create an sgl based on some arbitrary
> collection of offsets and length inside a BAR.

Isn't that what I just proposed above ?

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: christian.koenig@amd.com
Cc: Logan Gunthorpe <logang@deltatee.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	hch@infradead.org, linaro-mm-sig@lists.linaro.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 4/6] drm/amdgpu: add checks if DMA-buf P2P is supported
Date: Wed, 11 Mar 2020 11:38:35 -0300	[thread overview]
Message-ID: <20200311143835.GD31668@ziepe.ca> (raw)
In-Reply-To: <848c2f50-1529-f036-69cd-5104b7ebe27b@gmail.com>

On Wed, Mar 11, 2020 at 03:33:01PM +0100, Christian König wrote:
> Am 11.03.20 um 15:04 schrieb Jason Gunthorpe:
> > On Wed, Mar 11, 2020 at 02:51:56PM +0100, Christian König wrote:
> > > Check if we can do peer2peer on the PCIe bus.
> > > 
> > > Signed-off-by: Christian König <christian.koenig@amd.com>
> > >   drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 4 ++++
> > >   1 file changed, 4 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
> > > index aef12ee2f1e3..bbf67800c8a6 100644
> > > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
> > > @@ -38,6 +38,7 @@
> > >   #include <drm/amdgpu_drm.h>
> > >   #include <linux/dma-buf.h>
> > >   #include <linux/dma-fence-array.h>
> > > +#include <linux/pci-p2pdma.h>
> > >   /**
> > >    * amdgpu_gem_prime_vmap - &dma_buf_ops.vmap implementation
> > > @@ -179,6 +180,9 @@ static int amdgpu_dma_buf_attach(struct dma_buf *dmabuf,
> > >   	struct amdgpu_device *adev = amdgpu_ttm_adev(bo->tbo.bdev);
> > >   	int r;
> > > +	if (pci_p2pdma_distance_many(adev->pdev, &attach->dev, 1, true) < 0)
> > > +		attach->peer2peer = false;
> > > +
> > Are there other related patches than this series?
> > 
> > p2p dma mapping needs to be done in common code, in p2pdma.c - ie this
> > open coding is missing the bus_offset stuff, at least.
> 
> Yeah, I'm aware of this. But I couldn't find a better way for now.

Well, it isn't optional :)
 
> > I really do not want to see drivers open code this stuff.
> > 
> > We already have a p2pdma API for handling the struct page case, so I
> > suggest adding some new p2pdma API to handle this for non-struct page
> > cases.
> > 
> > ie some thing like:
> > 
> > int 'p2pdma map bar'(
> >     struct pci_device *source,
> >     unsigned int source_bar_number,
> >     struct pci_device *dest,
> >     physaddr&len *array_of_offsets & length pairs into source bar,
> >     struct scatterlist *output_sgl)
> 
> Well that's exactly what I have to avoid since I don't have the array of
> offsets around and want to avoid constructing it.

Maybe it doesn't need an array of offsets - just a single offset and
callers can iterate the API?

> Similar problem for dma_map_resource(). My example does this on demand, but
> essentially we also have use cases where this is done only once.

I'm not sure if this is portable. Does any IOMMU HW need to know P2P
is happening to setup successfully? We currently support such a narrow
scope of HW for P2P..

> Ideally we would have some function to create an sgl based on some arbitrary
> collection of offsets and length inside a BAR.

Isn't that what I just proposed above ?

Jason
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-11 14:38 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 13:51 P2P for DMA-buf Christian König
2020-03-11 13:51 ` [Intel-gfx] " Christian König
2020-03-11 13:51 ` Christian König
2020-03-11 13:51 ` [PATCH 1/6] lib/scatterlist: add sg_set_dma_addr() function Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 15:28   ` Christoph Hellwig
2020-03-11 15:28     ` [Intel-gfx] " Christoph Hellwig
2020-03-12 10:14     ` Christian König
2020-03-12 10:14       ` [Intel-gfx] " Christian König
2020-03-12 10:14       ` Christian König
2020-03-12 10:19       ` Christoph Hellwig
2020-03-12 10:19         ` [Intel-gfx] " Christoph Hellwig
2020-03-12 10:31         ` Christian König
2020-03-12 10:31           ` [Intel-gfx] " Christian König
2020-03-12 10:31           ` Christian König
2020-03-12 10:47           ` Christoph Hellwig
2020-03-12 10:47             ` [Intel-gfx] " Christoph Hellwig
2020-03-12 11:02             ` Christian König
2020-03-12 11:02               ` [Intel-gfx] " Christian König
2020-03-12 11:02               ` Christian König
2020-03-12 14:19             ` Jason Gunthorpe
2020-03-12 14:19               ` Jason Gunthorpe
2020-03-12 15:39               ` Christian König
2020-03-12 15:39                 ` [Intel-gfx] " Christian König
2020-03-12 15:39                 ` Christian König
2020-03-12 16:19                 ` Jason Gunthorpe
2020-03-12 16:19                   ` Jason Gunthorpe
2020-03-12 16:13               ` Logan Gunthorpe
2020-03-12 16:13                 ` [Intel-gfx] " Logan Gunthorpe
2020-03-12 16:13                 ` Logan Gunthorpe
2020-03-13 11:21               ` Christoph Hellwig
2020-03-13 11:21                 ` [Intel-gfx] " Christoph Hellwig
2020-03-13 12:17                 ` Jason Gunthorpe
2020-03-13 12:17                   ` Jason Gunthorpe
2020-03-16  8:56                   ` Christoph Hellwig
2020-03-16  8:56                     ` [Intel-gfx] " Christoph Hellwig
2020-03-16  9:41                     ` Christian König
2020-03-16  9:41                       ` [Intel-gfx] " Christian König
2020-03-16  9:41                       ` Christian König
2020-03-16  9:52                       ` Christoph Hellwig
2020-03-16  9:52                         ` [Intel-gfx] " Christoph Hellwig
2020-03-16 12:37                         ` Jason Gunthorpe
2020-03-16 12:37                           ` Jason Gunthorpe
2020-03-13 13:33                 ` Christian König
2020-03-13 13:33                   ` [Intel-gfx] " Christian König
2020-03-13 13:33                   ` Christian König
2020-03-11 13:51 ` [PATCH 2/6] dma-buf: add peer2peer flag Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 13:51 ` [PATCH 3/6] drm/amdgpu: note that we can handle peer2peer DMA-buf Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 13:51 ` [PATCH 4/6] drm/amdgpu: add checks if DMA-buf P2P is supported Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 14:04   ` Jason Gunthorpe
2020-03-11 14:04     ` Jason Gunthorpe
2020-03-11 14:33     ` Christian König
2020-03-11 14:33       ` [Intel-gfx] " Christian König
2020-03-11 14:33       ` Christian König
2020-03-11 14:38       ` Jason Gunthorpe [this message]
2020-03-11 14:38         ` Jason Gunthorpe
2020-03-11 14:43         ` Christian König
2020-03-11 14:43           ` [Intel-gfx] " Christian König
2020-03-11 14:43           ` Christian König
2020-03-11 14:48           ` Jason Gunthorpe
2020-03-11 14:48             ` Jason Gunthorpe
2020-03-11 13:51 ` [PATCH 5/6] drm/amdgpu: add support for exporting VRAM using DMA-buf v2 Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 14:33   ` Jason Gunthorpe
2020-03-11 14:33     ` Jason Gunthorpe
2020-03-11 14:39   ` Jason Gunthorpe
2020-03-11 14:39     ` Jason Gunthorpe
2020-03-11 15:08   ` Alex Deucher
2020-03-11 15:08     ` [Intel-gfx] " Alex Deucher
2020-03-11 15:08     ` Alex Deucher
2020-03-11 13:51 ` [PATCH 6/6] drm/amdgpu: improve amdgpu_gem_info debugfs file Christian König
2020-03-11 13:51   ` [Intel-gfx] " Christian König
2020-03-11 13:51   ` Christian König
2020-03-11 18:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] lib/scatterlist: add sg_set_dma_addr() function Patchwork
2020-03-11 18:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-30 13:55 [PATCH 1/6] dma-buf: add peer2peer flag Christian König
2020-03-30 13:55 ` [PATCH 4/6] drm/amdgpu: add checks if DMA-buf P2P is supported Christian König
2020-03-30 13:55   ` Christian König

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=20200311143835.GD31668@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=David1.Zhou@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hch@infradead.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=logang@deltatee.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.