From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Dirk Eibach <dirk.eibach@googlemail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: PCIe P2P access to GPU memory
Date: Sat, 29 Sep 2018 07:27:03 +0000 [thread overview]
Message-ID: <fd8be09e-37c8-4f47-a5dc-10fbccf15ed6@email.android.com> (raw)
In-Reply-To: <CANVMifLiGbBKVpvb96AhoniNjyjW+h0AwtYRKy19xuc=H1r8BQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 812 bytes --]
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.
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
[-- Attachment #1.2: Type: text/html, Size: 1586 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-29 7:27 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 [this message]
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
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=fd8be09e-37c8-4f47-a5dc-10fbccf15ed6@email.android.com \
--to=christian.koenig@amd.com \
--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