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

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

drm: implement helper functions for scanning lru list

2010-07-07T02:29:51+00:00

These helper functions can be used to efficiently scan lru list
for eviction. Eviction becomes a three stage process:
1. Scanning through the lru list until a suitable hole has been found.
2. Scan backwards to restore drm_mm consistency and find out which
   objects fall into the hole.
3. Evict the objects that fall into the hole.

These helper functions don't allocate any memory (at the price of
not allowing any other concurrent operations). Hence this can also be
used for ttm (which does lru scanning under a spinlock).

Evicting objects in this fashion should be more fair than the current
approach by i915 (scan the lru for a object large enough to contain
the new object). It's also more efficient than the current approach used
by ttm (uncoditionally evict objects from the lru until there's enough
free space).

Signed-Off-by: Daniel Vetter 
Acked-by: Thomas Hellstrom 
Signed-off-by: Chris Wilson 
Signed-off-by: Dave Airlie