> Am 07.04.19 um 13:44 schrieb 易林:
> > Hi, all:
> > when analyzing v5.1 source code, I notice that in
> > ttm_bo_add_move_fence,
> > when reservation_object_reserve_shared failed and return ENOMEM,
> > the fence's refcount increased without a pa
Hi, all:
when analyzing v5.1 source code, I notice that in ttm_bo_add_move_fence,
when reservation_object_reserve_shared failed and return ENOMEM,
the fence's refcount increased without a pair decrement even after return to
ttm_bo_add_move_fence's caller ttm_bo_mem_force_space:
static int tt
Hi, all:
when analyzing v5.1 source code, I notice that in ttm_bo_add_move_fence,
when reservation_object_reserve_shared failed and return ENOMEM,
the fence's refcount increased without a pair decrement even after return to
ttm_bo_add_move_fence's caller ttm_bo_mem_force_space:
static int tt