diff options
| author |   John Brooks <john@fastquake.com> | 2017-06-30 11:31:08 -0400 |
|---|---|---|
| committer |   Alex Deucher <alexander.deucher@amd.com> | 2017-07-14 11:06:33 -0400 |
| commit | 96cf8271df546d0f4cfc9ddddbc42dce633e0190 (patch) | |
| tree | 981e86f5e52091f11a03930cea2f7f5bd40ed35e /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/amdgpu: Throttle visible VRAM moves separately (diff) | |
| download | linux-rng-96cf8271df546d0f4cfc9ddddbc42dce633e0190.tar.xz linux-rng-96cf8271df546d0f4cfc9ddddbc42dce633e0190.zip | |
drm/amdgpu: Set/clear CPU_ACCESS flag on page fault and move to VRAM
When a BO is moved to VRAM, clear AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED.
This allows it to potentially later move to invisible VRAM if the CPU
does not access it again.
Setting the CPU_ACCESS flag in amdgpu_bo_fault_reserve_notify() also means
that we can remove the loop to restrict lpfn to the end of visible VRAM,
because amdgpu_ttm_placement_init() will do it for us.
v3 [Michel Dänzer]
* Use AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED instead of a new flag
(Christian König)
* Clear flag in amdgpu_bo_move instead of amdgpu_move_ram_vram
(Christian)
* Explicitly mention amdgpu_bo_fault_reserve_notify in amdgpu_bo_move
* Also clear flag in amdgpu_bo_create_restricted
Suggested-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: John Brooks <john@fastquake.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions