Re: [PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout v2

Am Mittwoch, dem 29.01.2025 um 11:58 +0100 schrieb Christian König: > Even the kerneldoc says that with a zero timeout the function should not > wait for anything, but still return 1 to indicate that the fences are > signaled now. > > Unfortunately that isn't what was implemented, instead of only

[PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout v2

Even the kerneldoc says that with a zero timeout the function should not wait for anything, but still return 1 to indicate that the fences are signaled now. Unfortunately that isn't what was implemented, instead of only returning 1 we also waited for at least one jiffies. Fix that by adjusting th

Re: [PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout

Am 28.01.25 um 15:41 schrieb Lucas Stach: Am Dienstag, dem 28.01.2025 um 15:28 +0100 schrieb Christian König: Am 28.01.25 um 11:48 schrieb Lucas Stach: Hi Christian, Am Dienstag, dem 28.01.2025 um 11:08 +0100 schrieb Christian König: Even the kerneldoc says that with a zero timeout the functi

Re: [PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout

Am 28.01.25 um 11:48 schrieb Lucas Stach: Hi Christian, Am Dienstag, dem 28.01.2025 um 11:08 +0100 schrieb Christian König: Even the kerneldoc says that with a zero timeout the function should not wait for anything, but still return 1 to indicate that the fences are signaled now. Unfortunately

Re: [PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout

Am Dienstag, dem 28.01.2025 um 15:28 +0100 schrieb Christian König: > Am 28.01.25 um 11:48 schrieb Lucas Stach: > > Hi Christian, > > > > Am Dienstag, dem 28.01.2025 um 11:08 +0100 schrieb Christian König: > > > Even the kerneldoc says that with a zero timeout the function should not > > > wait fo

Re: [PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout

Hi Christian, Am Dienstag, dem 28.01.2025 um 11:08 +0100 schrieb Christian König: > Even the kerneldoc says that with a zero timeout the function should not > wait for anything, but still return 1 to indicate that the fences are > signaled now. > > Unfortunately that isn't what was implemented, i

[PATCH] dma-buf: fix timeout handling in dma_resv_wait_timeout

Even the kerneldoc says that with a zero timeout the function should not wait for anything, but still return 1 to indicate that the fences are signaled now. Unfortunately that isn't what was implemented, instead of only returning 1 we also waited for at least one jiffies. Fix that by adjusting th