Now that CONFIG_DEPT_AGGRESSIVE_TIMEOUT_WAIT was introduced, apply the
consideration to dma fence wait.

Signed-off-by: Byungchul Park <byungc...@sk.com>
---
 drivers/dma-buf/dma-fence.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
index ad2d7a94c868..ab10b228a147 100644
--- a/drivers/dma-buf/dma-fence.c
+++ b/drivers/dma-buf/dma-fence.c
@@ -783,7 +783,7 @@ dma_fence_default_wait(struct dma_fence *fence, bool intr, 
signed long timeout)
        cb.task = current;
        list_add(&cb.base.node, &fence->cb_list);
 
-       sdt_might_sleep_start(NULL);
+       sdt_might_sleep_start_timeout(NULL, timeout);
        while (!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags) && ret > 
0) {
                if (intr)
                        __set_current_state(TASK_INTERRUPTIBLE);
@@ -887,7 +887,7 @@ dma_fence_wait_any_timeout(struct dma_fence **fences, 
uint32_t count,
                }
        }
 
-       sdt_might_sleep_start(NULL);
+       sdt_might_sleep_start_timeout(NULL, timeout);
        while (ret > 0) {
                if (intr)
                        set_current_state(TASK_INTERRUPTIBLE);
-- 
2.17.1

Reply via email to