2017-04-26 Christian König <deathsimple(a)vodafone.de>:
> Am 26.04.2017 um 16:46 schrieb Andres Rodriguez:
> > When a timeout of zero is specified, the caller is only interested in
> > the fence status.
> >
> > In the current implementation, dma_fence_default_wait will always call
> > schedule_timeout() at least once for an unsignaled fence. This adds a
> > significant overhead to a fence status query.
> >
> > Avoid this overhead by returning early if a zero timeout is specified.
> >
> > v2: move early return after enable_signaling
> >
> > Signed-off-by: Andres Rodriguez <andresx7(a)gmail.com>
>
> Reviewed-by: Christian König <christian.koenig(a)amd.com>
pushed to drm-misc-next. Thanks all.
Gustavo
From: Markus Elfring <elfring(a)users.sourceforge.net>
Date: Mon, 8 May 2017 11:05:05 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Combine two function calls into one in dma_buf_debug_show()
Improve a size determination in dma_buf_attach()
Adjust a null pointer check in dma_buf_attach()
Use seq_putc() in two functions
drivers/dma-buf/dma-buf.c | 8 +++-----
drivers/dma-buf/sync_debug.c | 6 +++---
2 files changed, 6 insertions(+), 8 deletions(-)
--
2.12.2