diff options
author | Daniel Vetter <[email protected]> | 2010-08-26 21:44:17 +0200 |
---|---|---|
committer | Dave Airlie <[email protected]> | 2010-08-27 09:10:16 +1000 |
commit | 7521473305f1379403b893a30ac09a2132dc1e25 (patch) | |
tree | 594d1c7f2807da61abb20aa3febe0ca159c3bdeb /tools/perf/util/trace-event-scripting.c | |
parent | 5afda9e9a4625d771795a5f540fb202eec08a49c (diff) |
drm: mm: fix range restricted allocations
With the code cleanup in
7a6b2896f261894dde287d3faefa4b432cddca53 is the first bad commit
commit 7a6b2896f261894dde287d3faefa4b432cddca53
Author: Daniel Vetter <[email protected]>
Date: Fri Jul 2 15:02:15 2010 +0100
drm_mm: extract check_free_mm_node
I've botched up the range-restriction checks. The result is usually
an X server dying with SIGBUS in libpixman (software fallback rendering).
Change the code to adjust the start and end for range restricted
allocations. IMHO this even makes the code a bit clearer.
Fixes regression bug: https://bugs.freedesktop.org/show_bug.cgi?id=29738
Reported-by-Tested-by: Till MAtthiesen <[email protected]>
Acked-by: Alex Deucher <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Signed-off-by: Dave Airlie <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions