linux-toradex.git/include/drm/ttm, branch v2.6.38-rc5

drm/ttm: Fix up io_mem_reserve / io_mem_free calling

2010-11-22T03:25:22+00:00

This patch attempts to fix up shortcomings with the current calling
sequences.

1) There's a fastpath where no locking occurs and only io_mem_reserved is
   called to obtain needed info for mapping. The fastpath is set per
   memory type manager.
2) If the fastpath is disabled, io_mem_reserve and io_mem_free will be exactly
   balanced and not called recursively for the same struct ttm_mem_reg.
3) Optionally the driver can choose to enable a per memory type manager LRU
   eviction mechanism that, when io_mem_reserve returns -EAGAIN will attempt
   to kill user-space mappings of memory in that manager to free up needed
   resources

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Ben Skeggs 
Signed-off-by: Dave Airlie

drm/ttm/vmwgfx: Have TTM manage the validation sequence.

2010-11-22T03:25:21+00:00

Rather than having the driver supply the validation sequence, leave that
responsibility to TTM. This saves some confusion and a function argument.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: Improved fencing of buffer object lists

2010-11-22T03:25:20+00:00

Drastically reduce the number of spin lock / unlock operations by performing
unreserving and fencing under global locks.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jerome Glisse 
Signed-off-by: Dave Airlie

drm/ttm/radeon/nouveau: Kill the bo lock in favour of a bo device fence_lock

2010-11-22T03:25:18+00:00

The bo lock used only to protect the bo sync object members, and since it
is a per bo lock, fencing a buffer list will see a lot of locks and unlocks.
Replace it with a per-device lock that protects the sync object members on
*all* bos. Reading and setting these members will always be very quick, so
the risc of heavy lock contention is microscopic. Note that waiting for
sync objects will always take place outside of this lock.

The bo device fence lock will eventually be replaced with a seqlock /
rcu mechanism so we can determine that a bo is idle under a
rcu / read seqlock.

However this change will allow us to batch fencing and unreserving of
buffers with a minimal amount of locking.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jerome Glisse 
Signed-off-by: Dave Airlie

drm/ttm: Don't deadlock on recursive multi-bo reservations

2010-11-22T03:25:17+00:00

Add an aid for the driver to detect deadlocks on multi-bo reservations
Update documentation.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jerome Glisse 
Signed-off-by: Dave Airlie

drm/ttm: Add a bo list reserve fastpath (v2)

2010-11-22T03:24:40+00:00

Makes it possible to reserve a list of buffer objects with a single
spin lock / unlock if there is no contention.
Should improve cpu usage on SMP kernels.

v2: Initialize private list members on reserve and don't call
ttm_bo_list_ref_sub() with zero put_count.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: Be consistent on ttm_bo_init() failures

2010-11-10T01:52:19+00:00

Call destroy() on _all_ ttm_bo_init() failures, and make sure that
behavior is documented in the function description.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: Documentation update

2010-11-09T03:33:15+00:00

Remove an obsolete comment about mm nodes.
Document the new bo range manager interface.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: Avoid using the ttm_mem_type_manager::put_locked function

2010-10-21T01:53:24+00:00

Release the lru spinlock early.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: add unlocked variant of new manager put node.

2010-10-18T23:49:42+00:00

We need the unlocked variant for the new codepath introduced to fix the
race condition in master recently.

Signed-off-by: Dave Airlie