Re: [PATCH 1/2] drm/amd/amdgpu: lock reservation object while creating shadow bo

2017-01-11 Thread Christian König
Am 11.01.2017 um 15:09 schrieb Nicolai Hähnle: On 11.01.2017 12:56, Christian König wrote: Am 11.01.2017 um 08:31 schrieb Nicolai Hähnle: From: Nicolai Hähnle ttm_bo_init checks that the reservation object is locked. This is the caller's responsibility when resv !=

Re: [PATCH 1/2] drm/amd/amdgpu: lock reservation object while creating shadow bo

2017-01-11 Thread Nicolai Hähnle
On 11.01.2017 12:56, Christian König wrote: Am 11.01.2017 um 08:31 schrieb Nicolai Hähnle: From: Nicolai Hähnle ttm_bo_init checks that the reservation object is locked. This is the caller's responsibility when resv != NULL. Otherwise, the inline reservation object of

Re: [PATCH 1/2] drm/amd/amdgpu: lock reservation object while creating shadow bo

2017-01-11 Thread Nicolai Hähnle
On 11.01.2017 12:56, Christian König wrote: Am 11.01.2017 um 08:31 schrieb Nicolai Hähnle: From: Nicolai Hähnle ttm_bo_init checks that the reservation object is locked. This is the caller's responsibility when resv != NULL. Otherwise, the inline reservation object of

Re: [PATCH 1/2] drm/amd/amdgpu: lock reservation object while creating shadow bo

2017-01-11 Thread Christian König
Am 11.01.2017 um 08:31 schrieb Nicolai Hähnle: From: Nicolai Hähnle ttm_bo_init checks that the reservation object is locked. This is the caller's responsibility when resv != NULL. Otherwise, the inline reservation object of the newly allocated buffer is used and must

[PATCH 1/2] drm/amd/amdgpu: lock reservation object while creating shadow bo

2017-01-10 Thread Nicolai Hähnle
From: Nicolai Hähnle ttm_bo_init checks that the reservation object is locked. This is the caller's responsibility when resv != NULL. Otherwise, the inline reservation object of the newly allocated buffer is used and must explicitly be locked. Using a trylock is fine,