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 !=
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
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
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
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,