[PATCH 3/6] drm/ttm: call ttm_bo_cleanup_refs with reservation and lru lock held, v3

2012-11-29 Thread Thomas Hellstrom
On 11/29/2012 12:36 PM, Maarten Lankhorst wrote: > By removing the unlocking of lru and retaking it immediately, a race is > removed where the bo is taken off the swap list or the lru list between > the unlock and relock. As such the cleanup_refs code can be simplified, > it will attempt to call tt

Re: [PATCH 3/6] drm/ttm: call ttm_bo_cleanup_refs with reservation and lru lock held, v3

2012-11-29 Thread Thomas Hellstrom
On 11/29/2012 12:36 PM, Maarten Lankhorst wrote: By removing the unlocking of lru and retaking it immediately, a race is removed where the bo is taken off the swap list or the lru list between the unlock and relock. As such the cleanup_refs code can be simplified, it will attempt to call ttm_bo_w

[PATCH 3/6] drm/ttm: call ttm_bo_cleanup_refs with reservation and lru lock held, v3

2012-11-29 Thread Maarten Lankhorst
By removing the unlocking of lru and retaking it immediately, a race is removed where the bo is taken off the swap list or the lru list between the unlock and relock. As such the cleanup_refs code can be simplified, it will attempt to call ttm_bo_wait non-blockingly, and if it fails it will drop th

[PATCH 3/6] drm/ttm: call ttm_bo_cleanup_refs with reservation and lru lock held, v3

2012-11-29 Thread Maarten Lankhorst
By removing the unlocking of lru and retaking it immediately, a race is removed where the bo is taken off the swap list or the lru list between the unlock and relock. As such the cleanup_refs code can be simplified, it will attempt to call ttm_bo_wait non-blockingly, and if it fails it will drop th