mirror of
https://github.com/torvalds/linux
synced 2024-10-25 04:37:40 +00:00
dfadbbdb57
Sometimes we want to know whether a buffer is busy and wait for it (bo_wait). However, sometimes it would be more useful to be able to query whether a buffer is busy and being either read or written, and wait until it's stopped being either read or written. The point of this is to be able to avoid unnecessary waiting, e.g. if a GPU has written something to a buffer and is now reading that buffer, and a CPU wants to map that buffer for read, it needs to only wait for the last write. If there were no write, there wouldn't be any waiting needed. This, or course, requires user space drivers to send read/write flags with each relocation (like we have read/write domains in radeon, so we can actually use those for something useful now). Now how this patch works: The read/write flags should passed to ttm_validate_buffer. TTM maintains separate sync objects of the last read and write for each buffer, in addition to the sync object of the last use of a buffer. ttm_bo_wait then operates with one the sync objects. Signed-off-by: Marek Olšák <maraeo@gmail.com> Reviewed-by: Jerome Glisse <jglisse@redhat.com> Signed-off-by: Dave Airlie <airlied@redhat.com> |
||
|---|---|---|
| .. | ||
| Makefile | ||
| ttm_agp_backend.c | ||
| ttm_bo.c | ||
| ttm_bo_manager.c | ||
| ttm_bo_util.c | ||
| ttm_bo_vm.c | ||
| ttm_execbuf_util.c | ||
| ttm_lock.c | ||
| ttm_memory.c | ||
| ttm_module.c | ||
| ttm_object.c | ||
| ttm_page_alloc.c | ||
| ttm_tt.c | ||