In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the same vm kill the somewhat dangerous
vma_create function and inline it into lookup_or_create.
This is just a safety measure to
On Wed, Aug 14, 2013 at 11:59:09AM +0200, Daniel Vetter wrote:
In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the same vm kill the somewhat dangerous
vma_create function and inline
On Wed, Aug 14, 2013 at 12:49:04PM +0100, Chris Wilson wrote:
On Wed, Aug 14, 2013 at 11:59:09AM +0200, Daniel Vetter wrote:
In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the
In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the same vm kill the somewhat dangerous
vma_create function and inline it into lookup_or_create.
This is just a safety measure to
On Wed, Aug 14, 2013 at 11:59:09AM +0200, Daniel Vetter wrote:
In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the same vm kill the somewhat dangerous
vma_create function and inline
On Wed, Aug 14, 2013 at 06:47:00PM +0200, Daniel Vetter wrote:
On Wed, Aug 14, 2013 at 11:59:09AM +0200, Daniel Vetter wrote:
In the execbuf code we don't clean up any vmas which ended up not
getting bound for code simplicity. To make sure that we don't end up
creating multiple vma for the
