From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Simona Vetter <simona.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
DMA BUFFER SHARING FRAMEWORK <linaro-mm-sig@lists.linaro.org>
Subject: Re: [Linaro-mm-sig] Re: Sharing dma-bufs using a driver-private interconnect
Date: Fri, 16 May 2025 10:53:27 +0200 [thread overview]
Message-ID: <ce7159c2d2dc6f425be48085a93aabf0cbe9f20c.camel@linux.intel.com> (raw)
In-Reply-To: <0a890d19-27a1-4525-83e6-cfc082dfab37@amd.com>
On Fri, 2025-05-16 at 10:44 +0200, Christian König wrote:
> Hi Thomas,
>
> On 5/16/25 10:33, Thomas Hellström wrote:
> > Hi!
> >
> > I previously discussed this with Simona on IRC but would like to
> > get
> > some feedback also from a wider audience:
> >
> > We're planning to share dma-bufs using a fast interconnect in a way
> > similar to pcie-p2p:
> >
> > The rough plan is to identify dma-bufs capable of sharing this way
> > by
> > looking at the address of either the dma-buf ops and / or the
> > importer_ops to conclude it's a device using the same driver (or
> > possibly child driver) and then take special action when the dma-
> > addresses are obtained. Nothing visible outside of the xe driver or
> > its
> > child driver.
>
> As far as I can see that should work and we have recommended doing
> exactly that to multiple people in the past.
>
> > Are there any absolute "DON'T"s or recommendations to keep in mind
> > WRT
> > to this approach?
>
> My only requirement is that you write up some documentation
> (preferable either in drivers/dma-buf/dma-buf.c or
> Documentation/driver-api/dma-buf.rst) how drivers should do this,
> what the implications with the rest of the DMA-buf interface is
> etc... etc...
>
> The goal is to nail down how to do driver private interfaces without
> breaking interoperability with drivers who don't participate in that.
Ok, Will ensure that we adhere to this.
Thanks,
Thomas
>
> Regards,
> Christian.
>
> >
> > Thanks,
> > Thomas
> >
> )
> _______________________________________________
> Linaro-mm-sig mailing list -- linaro-mm-sig@lists.linaro.org
> To unsubscribe send an email to linaro-mm-sig-leave@lists.linaro.org
prev parent reply other threads:[~2025-05-16 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 8:33 Sharing dma-bufs using a driver-private interconnect Thomas Hellström
2025-05-16 8:44 ` Christian König
2025-05-16 8:53 ` Thomas Hellström [this message]
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=ce7159c2d2dc6f425be48085a93aabf0cbe9f20c.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=simona.vetter@ffwll.ch \
/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.