Am 10.09.2017 um 09:30 schrieb Maarten Lankhorst: > Op 04-09-17 om 21:02 schreef Christian König: >> From: Christian König <christian.koenig at amd.com> >> >> Stop requiring that the src reservation object is locked for this operation. >> >> Signed-off-by: Christian König <christian.koenig at amd.com> >> --- >> drivers/dma-buf/reservation.c | 56 ++++++++++++++++++++++++++++++++----------- >> 1 file changed, 42 insertions(+), 14 deletions(-) >> >> diff --git a/drivers/dma-buf/reservation.c b/drivers/dma-buf/reservation.c >> index dec3a81..b44d9d7 100644 >> --- a/drivers/dma-buf/reservation.c >> +++ b/drivers/dma-buf/reservation.c >> @@ -266,8 +266,7 @@ EXPORT_SYMBOL(reservation_object_add_excl_fence); >> * @dst: the destination reservation object >> * @src: the source reservation object >> * >> -* Copy all fences from src to dst. Both src->lock as well as dst-lock must be >> -* held. >> +* Copy all fences from src to dst. dst-lock must be held. >> */ >> int reservation_object_copy_fences(struct reservation_object *dst, >> struct reservation_object *src) > Could this be implemented using reservation_object_get_fences_rcu? You're essentially duplicating its functionality. I've considered this as well, but reservation_object_get_fences_rcu() returns an array and here we need an reservation_object_list. Regards, Christian. > > Cheers, > Maarten > _______________________________________________ > amd-gfx mailing list > amd-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
