dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	"Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "dirk.eibach@googlemail.com" <dirk.eibach@googlemail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: PCIe P2P access to GPU memory
Date: Wed, 3 Oct 2018 15:37:42 +0200	[thread overview]
Message-ID: <8433acf4-456e-c994-4dcc-3240f3190f71@gmail.com> (raw)
In-Reply-To: <20181003090607.GA23685@phenom.ffwll.local>

Am 03.10.2018 um 11:06 schrieb Daniel Vetter:
> On Wed, Oct 03, 2018 at 08:54:44AM +0000, Koenig, Christian wrote:
>> Am 03.10.2018 um 09:14 schrieb Daniel Vetter:
>>> On Sat, Sep 29, 2018 at 9:27 AM Koenig, Christian
>>> <Christian.Koenig@amd.com> wrote:
>>>> This is work in progress.
>>>>
>>>> I published patches to enable DMA_buf P2P a few months ago, but now I'm waiting for the PCI subsystem to pick up core support for this.
>>>>
>>>> I can prepare you a branch based on current upstream kernel next week if you want to test this.
>>> Thread hijack, since I just read the lwn article on p2p for storage folks:
>>>
>>> https://lwn.net/Articles/767281/
>>>
>>> Totally doesn't match what I remember of your dma-buf p2p work. Do we
>>> need to rework, or is this some kind of higher-level interface on top
>>> of the raw p2p pci stuff? Or do I misremember.
>> The P2P from the storage folks are some mix of raw p2p capability
>> detection for PCI and higher level interface.
>>
>> I'm actually waiting for that stuff to land to extract the p2p
>> capability detection and use it for this DMA-buf stuff as well.
>>
>> Alternative would be to convince Logan to extract the capability
>> detection in his patch set as well, but so far he wasn't very keen about
>> that.
> So no plan to make dma-buf some kind of orchestrator and use the p2p
> map_sg stuff?

Not sure about that yet. Didn't had time to take a closer look.

Christian.

>   That seems to be the new/additional bits I haven't seen yet,
> and I'm wondered how we should fit dma-buf into that picture.
> -Daniel
>
>> Christian.
>>
>>> Thanks, Daniel
>>>
>>>> Regards,
>>>> Christian.
>>>>
>>>> Am 29.09.2018 09:01 schrieb Dirk Eibach <dirk.eibach@googlemail.com>:
>>>> I want to access GPU VRAM via PCIe P2P access, like DirectGMA but with
>>>> mainline drivers.
>>>> I can acquire a dmabuf from the GPU and pass it to my PCIe
>>>> framegrabber. But I don't see a way to get the PCIe bus address of the
>>>> video memory which I need for the P2P transfer. Is there already any
>>>> infrastructure in place for doing this? If not, what would be the
>>>> right way to implement this? Add another callback to the dmabuf
>>>> struct?
>>>>
>>>> Cheers
>>>> Dirk
>>>> _______________________________________________
>>>> dri-devel mailing list
>>>> dri-devel@lists.freedesktop.org
>>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>>>

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

      reply	other threads:[~2018-10-03 13:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  7:00 PCIe P2P access to GPU memory Dirk Eibach
2018-09-29  7:27 ` Koenig, Christian
2018-09-29  8:17   ` Dirk Eibach
2018-09-29  9:53     ` Dieter Nützel
2018-10-01 13:07       ` Dirk Eibach
2018-10-01 18:12         ` Christian König
2018-10-01 18:47           ` Dirk Eibach
2018-10-03  7:14   ` Daniel Vetter
2018-10-03  8:54     ` Koenig, Christian
2018-10-03  9:06       ` Daniel Vetter
2018-10-03 13:37         ` Christian König [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=8433acf4-456e-c994-4dcc-3240f3190f71@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Christian.Koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dirk.eibach@googlemail.com \
    --cc=dri-devel@lists.freedesktop.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