-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'topic/i915-gem-next-2021-03-26' of ssh://git.freedesktop.o…
…rg/git/drm/drm into drm-next special i915-gem-next pull as requested - Conversion to dma_resv_locking, obj->mm.lock is gone (Maarten, with help from Thomas Hellström) - watchdog (Tvrtko, one patch to cancel individual request from Chris) - legacy ioctl cleanup (Jason+Ashutosh) - i915-gem TODO and RFC process doc (me) - i915_ prefix for vma_lookup (Liam Howlett) just because I spotted it and put it in here too Signed-off-by: Dave Airlie <airlied@redhat.com> From: Daniel Vetter <daniel.vetter@ffwll.ch> Link: https://patchwork.freedesktop.org/patch/msgid/YF24MHoOSjpKFEXA@phenom.ffwll.local
- Loading branch information
Showing
117 changed files
with
2,749 additions
and
2,165 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
=============== | ||
GPU RFC Section | ||
=============== | ||
|
||
For complex work, especially new uapi, it is often good to nail the high level | ||
design issues before getting lost in the code details. This section is meant to | ||
host such documentation: | ||
|
||
* Each RFC should be a section in this file, explaining the goal and main design | ||
considerations. Especially for uapi make sure you Cc: all relevant project | ||
mailing lists and involved people outside of dri-devel. | ||
|
||
* For uapi structures add a file to this directory with and then pull the | ||
kerneldoc in like with real uapi headers. | ||
|
||
* Once the code has landed move all the documentation to the right places in | ||
the main core, helper or driver sections. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
gem/gt TODO items | ||
----------------- | ||
|
||
- For discrete memory manager, merge enough dg1 to be able to refactor it to | ||
TTM. Then land pci ids (just in case that turns up an uapi problem). TTM has | ||
improved a lot the past 2 years, there's no reason anymore not to use it. | ||
|
||
- Come up with a plan what to do with drm/scheduler and how to get there. | ||
|
||
- Roll out dma_fence critical section annotations. | ||
|
||
- There's a lot of complexity added past few years to make relocations faster. | ||
That doesn't make sense given hw and gpu apis moved away from this model years | ||
ago: | ||
1. Land a modern pre-bound uapi like VM_BIND | ||
2. Any complexity added in this area past few years which can't be justified | ||
with VM_BIND using userspace should be removed. Looking at amdgpu dma_resv on | ||
the bo and vm, plus some lru locks is all that needed. No complex rcu, | ||
refcounts, caching, ... on everything. | ||
This is the matching task on the vm side compared to ttm/dma_resv on the | ||
backing storage side. | ||
|
||
- i915_sw_fence seems to be the main structure for the i915-gem dma_fence model. | ||
How-to-dma_fence is core and drivers really shouldn't build their own world | ||
here, treating everything else as a fixed platform. i915_sw_fence concepts | ||
should be moved to dma_fence, drm/scheduler or atomic commit helpers. Or | ||
removed if dri-devel consensus is that it's not a good idea. Once that's done | ||
maybe even remove it if there's nothing left. | ||
|
||
Smaller things: | ||
- i915_utils.h needs to be moved to the right places. | ||
|
||
- dma_fence_work should be in drivers/dma-buf | ||
|
||
- i915_mm.c should be moved to the right places. Some of the helpers also look a | ||
bit fishy: | ||
|
||
https://lore.kernel.org/linux-mm/20210301083320.943079-1-hch@lst.de/ | ||
|
||
- tasklet helpers in i915_gem.h also look a bit misplaced and should | ||
probably be moved to tasklet headers. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.