diff options
| author | Michel Dänzer <michel.daenzer@amd.com> | 2014-10-09 15:02:59 +0900 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2014-10-16 18:34:08 -0400 |
| commit | e300180f71037fd9ed1ca967006fd9f3ee466bcd (patch) | |
| tree | 75d6ebc93299bac9e636611d77f59e512f35f9ab /drivers/gpu/drm/radeon/dce3_1_afmt.c | |
| parent | 9ace2ef7b78e573cedead0f08052b028181e6eaf (diff) | |
| download | blackbird-op-linux-e300180f71037fd9ed1ca967006fd9f3ee466bcd.tar.gz blackbird-op-linux-e300180f71037fd9ed1ca967006fd9f3ee466bcd.zip | |
drm/ttm: Don't evict BOs outside of the requested placement range
The radeon driver uses placement range restrictions for several reasons,
in particular to make sure BOs in VRAM can be accessed by the CPU, e.g.
during a page fault.
Without this change, TTM could evict other BOs while trying to satisfy
the requested placement, even if the evicted BOs were outside of the
requested placement range. Doing so didn't free up any space in the
requested placement range, so the (potentially high) eviction cost was
incurred for no benefit.
Nominating for stable because radeon driver changes in 3.17 made this
much more noticeable than before.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=84662
Cc: stable@vger.kernel.org
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/radeon/dce3_1_afmt.c')
0 files changed, 0 insertions, 0 deletions
