From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, sumit.semwal@linaro.org,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
intel-gfx@lists.freedesktop.org
Subject: RFC: Unpinned DMA-buf handling
Date: Tue, 29 Oct 2019 11:40:44 +0100 [thread overview]
Message-ID: <20191029104049.9011-1-christian.koenig@amd.com> (raw)
The basic idea stayed the same since the last version of those patches. The exporter can provide explicit pin/unpin functions and the importer a move_notify callback. This allows us to avoid pinning buffers while importers have a mapping for them.
In difference to the last version the locking changes were separated from this patchset and committed to drm-misc-next.
This allows drivers to implement the new locking semantics without the extra unpinned handling, but of course the changed locking semantics is still a prerequisite to the unpinned handling.
The last time this set was send out the discussion ended by questioning if the move_notify callback was really the right approach of notifying the importers that a buffer is about to change its placement. A possible alternative would be to add a special crafted fence object instead.
Let's discuss on the different approaches once more,
Christian.
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, sumit.semwal@linaro.org,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
intel-gfx@lists.freedesktop.org
Subject: RFC: Unpinned DMA-buf handling
Date: Tue, 29 Oct 2019 11:40:44 +0100 [thread overview]
Message-ID: <20191029104049.9011-1-christian.koenig@amd.com> (raw)
The basic idea stayed the same since the last version of those patches. The exporter can provide explicit pin/unpin functions and the importer a move_notify callback. This allows us to avoid pinning buffers while importers have a mapping for them.
In difference to the last version the locking changes were separated from this patchset and committed to drm-misc-next.
This allows drivers to implement the new locking semantics without the extra unpinned handling, but of course the changed locking semantics is still a prerequisite to the unpinned handling.
The last time this set was send out the discussion ended by questioning if the move_notify callback was really the right approach of notifying the importers that a buffer is about to change its placement. A possible alternative would be to add a special crafted fence object instead.
Let's discuss on the different approaches once more,
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, sumit.semwal@linaro.org,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] RFC: Unpinned DMA-buf handling
Date: Tue, 29 Oct 2019 11:40:44 +0100 [thread overview]
Message-ID: <20191029104049.9011-1-christian.koenig@amd.com> (raw)
Message-ID: <20191029104044.vuIIoFJOCsEfW4TH1sk3f94GWcRfjn5nhkqvif7MFAk@z> (raw)
The basic idea stayed the same since the last version of those patches. The exporter can provide explicit pin/unpin functions and the importer a move_notify callback. This allows us to avoid pinning buffers while importers have a mapping for them.
In difference to the last version the locking changes were separated from this patchset and committed to drm-misc-next.
This allows drivers to implement the new locking semantics without the extra unpinned handling, but of course the changed locking semantics is still a prerequisite to the unpinned handling.
The last time this set was send out the discussion ended by questioning if the move_notify callback was really the right approach of notifying the importers that a buffer is about to change its placement. A possible alternative would be to add a special crafted fence object instead.
Let's discuss on the different approaches once more,
Christian.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-10-29 10:40 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 10:40 Christian König [this message]
2019-10-29 10:40 ` [Intel-gfx] RFC: Unpinned DMA-buf handling Christian König
2019-10-29 10:40 ` Christian König
2019-10-29 10:40 ` [PATCH 1/5] dma-buf: add dynamic DMA-buf handling v14 Christian König
2019-10-29 10:40 ` [Intel-gfx] " Christian König
2019-10-29 10:40 ` Christian König
2019-11-05 10:20 ` Daniel Vetter
2019-11-05 10:20 ` [Intel-gfx] " Daniel Vetter
2019-11-05 10:20 ` Daniel Vetter
2020-02-18 13:20 ` Christian König
2020-02-18 13:20 ` [Intel-gfx] " Christian König
2020-02-18 13:20 ` Christian König
2020-02-18 14:14 ` Daniel Vetter
2020-02-18 14:14 ` [Intel-gfx] " Daniel Vetter
2020-02-18 14:14 ` Daniel Vetter
2019-10-29 10:40 ` [PATCH 2/5] drm/ttm: remove the backing store if no placement is given Christian König
2019-10-29 10:40 ` [Intel-gfx] " Christian König
2019-10-29 10:40 ` Christian König
2019-10-29 10:40 ` [PATCH 3/5] drm/amdgpu: use allowed_domains for exported DMA-bufs Christian König
2019-10-29 10:40 ` [Intel-gfx] " Christian König
2019-10-29 10:40 ` Christian König
2019-10-29 10:40 ` [PATCH 4/5] drm/amdgpu: add amdgpu_dma_buf_pin/unpin Christian König
2019-10-29 10:40 ` [Intel-gfx] " Christian König
2019-10-29 10:40 ` Christian König
2019-10-29 10:40 ` [PATCH 5/5] drm/amdgpu: implement amdgpu_gem_prime_move_notify Christian König
2019-10-29 10:40 ` [Intel-gfx] " Christian König
2019-10-29 10:40 ` Christian König
2019-11-05 10:52 ` Daniel Vetter
2019-11-05 10:52 ` [Intel-gfx] " Daniel Vetter
2019-11-05 10:52 ` Daniel Vetter
2019-11-05 13:39 ` Christian König
2019-11-05 13:39 ` [Intel-gfx] " Christian König
2019-11-05 13:39 ` Christian König
2019-11-05 13:50 ` Daniel Vetter
2019-11-05 13:50 ` [Intel-gfx] " Daniel Vetter
2019-11-05 13:50 ` Daniel Vetter
2019-11-05 13:50 ` Daniel Vetter
2019-11-05 15:20 ` Koenig, Christian
2019-11-05 15:20 ` [Intel-gfx] " Koenig, Christian
2019-11-05 15:20 ` Koenig, Christian
2019-11-05 15:20 ` Koenig, Christian
2019-11-05 15:23 ` Daniel Vetter
2019-11-05 15:23 ` [Intel-gfx] " Daniel Vetter
2019-11-05 15:23 ` Daniel Vetter
2019-11-05 15:23 ` Daniel Vetter
2019-10-29 17:38 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] dma-buf: add dynamic DMA-buf handling v14 Patchwork
2019-10-29 17:38 ` [Intel-gfx] " Patchwork
2019-10-29 18:09 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-10-29 18:09 ` [Intel-gfx] " Patchwork
2019-11-05 13:46 ` RFC: Unpinned DMA-buf handling Daniel Vetter
2019-11-05 13:46 ` [Intel-gfx] " Daniel Vetter
2019-11-05 13:46 ` Daniel Vetter
2019-11-05 13:46 ` Daniel Vetter
2020-02-17 15:45 Christian König
2020-02-17 15:45 ` 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=20191029104049.9011-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.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 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.