From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org,
daniel@ffwll.ch
Subject: RFC: Unpinned DMA-buf handling
Date: Mon, 17 Feb 2020 16:45:04 +0100 [thread overview]
Message-ID: <20200217154509.2265-1-christian.koenig@amd.com> (raw)
Hi everyone,
hopefully the last iteration of those patches.
For now I've addressed the issue of unmapping imported BOs from the amdgpu page tables immediately by locking the page tables in place.
For HMM handling we are getting the ability to invalidate BOs without locking the VM anyway, so this last TODO will probably go away rather soon.
Place comment,
Christian.
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org,
daniel@ffwll.ch
Subject: RFC: Unpinned DMA-buf handling
Date: Mon, 17 Feb 2020 16:45:04 +0100 [thread overview]
Message-ID: <20200217154509.2265-1-christian.koenig@amd.com> (raw)
Hi everyone,
hopefully the last iteration of those patches.
For now I've addressed the issue of unmapping imported BOs from the amdgpu page tables immediately by locking the page tables in place.
For HMM handling we are getting the ability to invalidate BOs without locking the VM anyway, so this last TODO will probably go away rather soon.
Place comment,
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, linaro-mm-sig@lists.linaro.org,
linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org,
daniel@ffwll.ch
Subject: [Intel-gfx] RFC: Unpinned DMA-buf handling
Date: Mon, 17 Feb 2020 16:45:04 +0100 [thread overview]
Message-ID: <20200217154509.2265-1-christian.koenig@amd.com> (raw)
Hi everyone,
hopefully the last iteration of those patches.
For now I've addressed the issue of unmapping imported BOs from the amdgpu page tables immediately by locking the page tables in place.
For HMM handling we are getting the ability to invalidate BOs without locking the VM anyway, so this last TODO will probably go away rather soon.
Place comment,
Christian.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-02-17 15:45 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 15:45 Christian König [this message]
2020-02-17 15:45 ` [Intel-gfx] RFC: Unpinned DMA-buf handling Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 15:45 ` [PATCH 1/5] dma-buf: add dynamic DMA-buf handling v14 Christian König
2020-02-17 15:45 ` [Intel-gfx] " Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 15:50 ` Christian König
2020-02-17 15:50 ` [Intel-gfx] " Christian König
2020-02-17 15:50 ` Christian König
2020-02-17 15:45 ` [PATCH 2/5] drm/ttm: remove the backing store if no placement is given Christian König
2020-02-17 15:45 ` [Intel-gfx] " Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 15:45 ` [PATCH 3/5] drm/amdgpu: use allowed_domains for exported DMA-bufs Christian König
2020-02-17 15:45 ` [Intel-gfx] " Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 15:45 ` [PATCH 4/5] drm/amdgpu: add amdgpu_dma_buf_pin/unpin v2 Christian König
2020-02-17 15:45 ` [Intel-gfx] " Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 15:45 ` [PATCH 5/5] drm/amdgpu: implement amdgpu_gem_prime_move_notify v2 Christian König
2020-02-17 15:45 ` [Intel-gfx] " Christian König
2020-02-17 15:45 ` Christian König
2020-02-17 17:55 ` Daniel Vetter
2020-02-17 17:55 ` [Intel-gfx] " Daniel Vetter
2020-02-17 17:55 ` Daniel Vetter
2020-02-17 18:58 ` Christian König
2020-02-17 18:58 ` [Intel-gfx] " Christian König
2020-02-17 18:58 ` Christian König
2020-02-17 19:38 ` Daniel Vetter
2020-02-17 19:38 ` [Intel-gfx] " Daniel Vetter
2020-02-17 19:38 ` Daniel Vetter
2020-02-18 10:42 ` Christian König
2020-02-18 10:42 ` [Intel-gfx] " Christian König
2020-02-18 20:17 ` Thomas Hellström (VMware)
2020-02-18 20:17 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-18 20:17 ` Thomas Hellström (VMware)
2020-02-18 21:01 ` Daniel Vetter
2020-02-18 21:01 ` [Intel-gfx] " Daniel Vetter
2020-02-18 21:01 ` Daniel Vetter
2020-02-19 6:42 ` Thomas Hellström (VMware)
2020-02-19 6:42 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-19 6:42 ` Thomas Hellström (VMware)
2020-02-20 9:39 ` Thomas Hellström (VMware)
2020-02-20 9:39 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-20 9:39 ` Thomas Hellström (VMware)
2020-02-20 18:04 ` Daniel Vetter
2020-02-20 18:04 ` [Intel-gfx] " Daniel Vetter
2020-02-20 18:04 ` Daniel Vetter
2020-02-20 19:46 ` Thomas Hellström (VMware)
2020-02-20 19:46 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-20 19:46 ` Thomas Hellström (VMware)
2020-02-20 20:08 ` Daniel Vetter
2020-02-20 20:08 ` [Intel-gfx] " Daniel Vetter
2020-02-20 20:08 ` Daniel Vetter
2020-02-20 22:51 ` Thomas Hellström (VMware)
2020-02-20 22:51 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-20 22:51 ` Thomas Hellström (VMware)
2020-02-21 17:12 ` Daniel Vetter
2020-02-21 17:12 ` [Intel-gfx] " Daniel Vetter
2020-02-21 17:12 ` Daniel Vetter
2020-02-21 19:45 ` Thomas Hellström (VMware)
2020-02-21 19:45 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-21 19:45 ` Thomas Hellström (VMware)
2020-02-23 15:45 ` Christian König
2020-02-23 15:45 ` [Intel-gfx] " Christian König
2020-02-23 15:45 ` Christian König
2020-02-23 16:54 ` Thomas Hellström (VMware)
2020-02-23 16:54 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-23 16:54 ` Thomas Hellström (VMware)
2020-02-24 18:46 ` Christian König
2020-02-24 18:46 ` [Intel-gfx] " Christian König
2020-02-24 18:46 ` Christian König
2020-02-24 21:11 ` Thomas Hellström (VMware)
2020-02-24 21:11 ` [Intel-gfx] " Thomas Hellström (VMware)
2020-02-24 21:11 ` Thomas Hellström (VMware)
2020-02-25 17:16 ` Daniel Vetter
2020-02-25 17:16 ` [Intel-gfx] " Daniel Vetter
2020-02-25 17:16 ` Daniel Vetter
2020-02-26 16:32 ` Daniel Vetter
2020-02-26 16:32 ` [Intel-gfx] " Daniel Vetter
2020-02-26 16:32 ` Daniel Vetter
2020-02-27 9:20 ` Christian König
2020-02-27 9:20 ` [Intel-gfx] " Christian König
2020-02-27 9:20 ` Christian König
2020-02-27 9:38 ` Daniel Vetter
2020-02-27 9:38 ` [Intel-gfx] " Daniel Vetter
2020-02-27 9:38 ` Daniel Vetter
2020-02-18 23:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] dma-buf: add dynamic DMA-buf handling v14 Patchwork
2020-02-19 0:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-20 11:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 10:40 RFC: Unpinned DMA-buf handling Christian König
2019-10-29 10:40 ` Christian König
2019-11-05 13:46 ` Daniel Vetter
2019-11-05 13:46 ` Daniel Vetter
2019-11-05 13:46 ` Daniel Vetter
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=20200217154509.2265-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--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 \
/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.