Patch "dma-buf/dma-fence: Extract __dma_fence_is_later()" has been added to the 4.9-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
dma-buf/dma-fence: Extract __dma_fence_is_later()
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
dma-buf-dma-fence-extract-__dma_fence_is_later.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
8111477663813caa1a4469cfe6afaae36cd04513Mon Sep 17 00:00:00 2001
From: Chris Wilson <[email protected]>
Date: Thu, 29 Jun 2017 13:59:24 +0100
Subject: dma-buf/dma-fence: Extract __dma_fence_is_later()
From: Chris Wilson <[email protected]>
commit 8111477663813caa1a4469cfe6afaae36cd04513 upstream.
Often we have the task of comparing two seqno known to be on the same context, so provide a common __dma_fence_is_later().
--- include/linux/fence.h | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
include/linux/fence.h +14 -1
@@ -281,6 +281,19 @@ fence_is_signaled(struct fence *fence) }/** +* __fence_is_later - return if f1 is chronologically later than f2 +* @f1: [in] the first fence's seqno +* @f2: [in] the second fence's seqno from the same context +* +* Returns true if f1 is chronologically later than f2. Both fences must be +* from the same context, since a seqno is not common across contexts. +*/ +static inline bool __fence_is_later (u32 f1,u32 f2) +{ +return (int )(f1 - f2) >0 ; +} + +/** * fence_is_later - return if f1 is chronologically later than f2 * @f1: [in] the first fence from the same context * @f2: [in] the second fence from the same context
@@ -293,7 +306,7 @@ static inline bool fence_is_later(structif (WARN_ON (f1->context != f2->context))return false; -return (int )(f1->seqno - f2->seqno) >0 ; +return __fence_is_later (f1->seqno, f2->seqno); }/**
Patches currently in stable-queue which might be from [email protected] are
queue-4.9/dma-buf-sw-sync-fix-the-is-signaled-test-to-handle-u32-wraparound.patch queue-4.9/dma-fence-clear-fence-status-during-dma_fence_init.patch queue-4.9/dma-buf-sw-sync-fix-locking-around-sync_timeline-lists.patch queue-4.9/dma-fence-wrap-querying-the-fence-status.patch queue-4.9/dma-buf-sw_sync-clean-up-list-before-signaling-the-fence.patch queue-4.9/dma-buf-sw-sync-reduce-irqsave-irqrestore-from-known-context.patch queue-4.9/dma-buf-sw_sync-move-timeline_fence_ops-around.patch queue-4.9/dma-buf-sw-sync-prevent-user-overflow-on-timeline-advance.patch queue-4.9/dma-fence-introduce-drm_fence_set_error-helper.patch queue-4.9/dma-buf-sw_sync-force-signal-all-unsignaled-fences-on-dying-timeline.patch queue-4.9/dma-buf-sw-sync-use-an-rbtree-to-sort-fences-in-the-timeline.patch queue-4.9/dma-buf-sw-sync-sync_pt-is-private-and-of-fixed-size.patch queue-4.9/dma-buf-dma-fence-extract-__dma_fence_is_later.patch