linux-toradex.git/drivers/gpu/drm/drm_mm.c, branch v3.4.66

drm/mm: fix dump table BUG

2013-05-19T17:54:41+00:00

commit 3a359f0b21ab218c1bf7a6a1b638b6fd143d0b99 upstream.

In

commit 9e8944ab564f2e3dde90a518cd32048c58918608
Author: Chris Wilson 
Date:   Thu Nov 15 11:32:17 2012 +0000

    drm: Introduce an iterator over holes in the drm_mm range manager

helpers and iterators for hole handling have been introduced with some
debug BUG_ONs sprinkled over. Unfortunately this broke the mm dumper
which unconditionally tried to compute the size of the very first
hole.

While at it unify the code a bit with the hole dumping in the loop.

v2: Extract a hole dump helper.

Reported-by: Christopher Harvey 
Cc: Christopher Harvey 
Cc: Dave Airlie 
Cc: Chris Wilson 
Acked-by: Dave Airlie 
Signed-off-by: Daniel Vetter 
Signed-off-by: Greg Kroah-Hartman

gpu: Add export.h as required to drivers/gpu files.

2011-10-31T23:32:03+00:00

They need this to get all the EXPORT_SYMBOL variants and THIS_MODULE

Signed-off-by: Paul Gortmaker

drm: mm: fix debug output

2011-05-08T23:14:45+00:00

The looping helper didn't do anything due to a superficial
semicolon. Furthermore one of the two dump functions suffered
from copy&paste fail.

While staring at the code I've also noticed that the replace
helper (currently unused) is a bit broken.

Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

Fix common misspellings

2011-03-31T14:26:23+00:00

Fixes generated by 'codespell' and manually reviewed.

Signed-off-by: Lucas De Marchi

drm: mm: add helper to unwind scan state

2011-02-23T00:32:57+00:00

With the switch to implicit free space accounting one pointer
got unused when scanning. Use it to create a single-linked list
to ensure correct unwinding of the scan state.

Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm: mm: add api for embedding struct drm_mm_node

2011-02-23T00:32:51+00:00

The old api has a two-step process: First search for a suitable
free hole, then allocate from that specific hole. No user used
this to do anything clever. So drop it for the embeddable variant
of the drm_mm api (the old one retains this ability, for the time
being).

With struct drm_mm_node embedded, we cannot track allocations
anymore by checking for a NULL pointer. So keep track of this
and add a small helper drm_mm_node_allocated.

Also add a function to move allocations between different struct
drm_mm_node.

v2: Implement suggestions by Chris Wilson.

Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm: mm: extract node insert helper functions

2011-02-23T00:32:43+00:00

Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm: mm: track free areas implicitly

2011-02-23T00:32:34+00:00

The idea is to track free holes implicitly by marking the allocation
immediatly preceeding a hole.

To avoid an ugly corner case add a dummy head_node to struct drm_mm
to track the hole that spans to complete allocation area when the
memory manager is empty.

To guarantee that there's always a preceeding/following node (that might
be marked as hole_follows == 1), move the mm->node_list list_head to the
head_node.

The main allocator and fair-lru scan code actually becomes simpler.
Only the debug code slightly suffers because free areas are no longer
explicit.

Also add drm_mm_for_each_node (which will be much more useful when
struct drm_mm_node is embeddable).

Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm_mm: add support for range-restricted fair-lru scans

2010-10-27T22:31:04+00:00

Signed-off-by: Daniel Vetter 
Signed-off-by: Chris Wilson

drm: mm: fix range restricted allocations

2010-08-26T23:10:16+00:00

With the code cleanup in

7a6b2896f261894dde287d3faefa4b432cddca53 is the first bad commit
commit 7a6b2896f261894dde287d3faefa4b432cddca53
Author: Daniel Vetter 
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 
Acked-by: Alex Deucher 
Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie