[PATCH v4 3/4] drm/ttm: convert to unified vma offset manager

2013-07-24 Thread Daniel Vetter
On Tue, Jul 23, 2013 at 02:47:15PM +0200, David Herrmann wrote: > Use the new vma-manager infrastructure. This doesn't change any > implementation details as the vma-offset-manager is nearly copied 1-to-1 > from TTM. > > The vm_lock is moved into the offset manager so we can drop it from TTM. > Du

Re: [PATCH v4 3/4] drm/ttm: convert to unified vma offset manager

2013-07-24 Thread Daniel Vetter
On Tue, Jul 23, 2013 at 02:47:15PM +0200, David Herrmann wrote: > Use the new vma-manager infrastructure. This doesn't change any > implementation details as the vma-offset-manager is nearly copied 1-to-1 > from TTM. > > The vm_lock is moved into the offset manager so we can drop it from TTM. > Du

[PATCH v4 3/4] drm/ttm: convert to unified vma offset manager

2013-07-23 Thread David Herrmann
Use the new vma-manager infrastructure. This doesn't change any implementation details as the vma-offset-manager is nearly copied 1-to-1 from TTM. The vm_lock is moved into the offset manager so we can drop it from TTM. During lookup, we use the vma locking helpers to take a reference to the found

[PATCH v4 3/4] drm/ttm: convert to unified vma offset manager

2013-07-23 Thread David Herrmann
Use the new vma-manager infrastructure. This doesn't change any implementation details as the vma-offset-manager is nearly copied 1-to-1 from TTM. The vm_lock is moved into the offset manager so we can drop it from TTM. During lookup, we use the vma locking helpers to take a reference to the found