[PATCH] ttm: don't destroy old mm_node on memcpy failure

2013-01-16 Thread Dave Airlie
When we are using memcpy to move objects around, and we fail to memcpy due to lack of memory to populate or failure to finish the copy, we don't want to destroy the mm_node that has been copied into old_copy. While working on a new kms driver that uses memcpy, if I overallocated bo's up to the mem

[PATCH] ttm: don't destroy old mm_node on memcpy failure

2013-01-16 Thread Jerome Glisse
On Tue, Jan 15, 2013 at 11:28 PM, Dave Airlie wrote: > When we are using memcpy to move objects around, and we fail to memcpy > due to lack of memory to populate or failure to finish the copy, we don't > want to destroy the mm_node that has been copied into old_copy. > > While working on a new kms

Re: [PATCH] ttm: don't destroy old mm_node on memcpy failure

2013-01-16 Thread Jerome Glisse
On Tue, Jan 15, 2013 at 11:28 PM, Dave Airlie wrote: > When we are using memcpy to move objects around, and we fail to memcpy > due to lack of memory to populate or failure to finish the copy, we don't > want to destroy the mm_node that has been copied into old_copy. > > While working on a new kms

[PATCH] ttm: don't destroy old mm_node on memcpy failure

2013-01-15 Thread Dave Airlie
When we are using memcpy to move objects around, and we fail to memcpy due to lack of memory to populate or failure to finish the copy, we don't want to destroy the mm_node that has been copied into old_copy. While working on a new kms driver that uses memcpy, if I overallocated bo's up to the mem