dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
	dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH 1/2] Revert "dma-buf: Report signaled links inside dma-fence-chain"
Date: Thu, 25 Jun 2020 14:43:41 +0200	[thread overview]
Message-ID: <51e00eed-c8f1-aabf-ec2c-07be0453ab3b@amd.com> (raw)
In-Reply-To: <20200625123443.19680-1-lionel.g.landwerlin@intel.com>

Am 25.06.20 um 14:34 schrieb Lionel Landwerlin:
> This reverts commit 5de376bb434f80a13138f0ebedc8351ab73d8b0d.
>
> This change breaks synchronization of a timeline.
> dma_fence_chain_find_seqno() might be a bit of a confusing name but
> this function is not trying to find a particular seqno, is supposed to
> give a fence to wait on for a particular point in the timeline.
>
> In a timeline, a particular value is reached when all the points up to
> and including that value have signaled.
>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/dma-buf/dma-fence-chain.c | 7 -------
>   1 file changed, 7 deletions(-)
>
> diff --git a/drivers/dma-buf/dma-fence-chain.c b/drivers/dma-buf/dma-fence-chain.c
> index c435bbba851c..3d123502ff12 100644
> --- a/drivers/dma-buf/dma-fence-chain.c
> +++ b/drivers/dma-buf/dma-fence-chain.c
> @@ -99,12 +99,6 @@ int dma_fence_chain_find_seqno(struct dma_fence **pfence, uint64_t seqno)
>   		return -EINVAL;
>   
>   	dma_fence_chain_for_each(*pfence, &chain->base) {
> -		if ((*pfence)->seqno < seqno) { /* already signaled */
> -			dma_fence_put(*pfence);
> -			*pfence = NULL;
> -			break;
> -		}
> -
>   		if ((*pfence)->context != chain->base.context ||
>   		    to_dma_fence_chain(*pfence)->prev_seqno < seqno)
>   			break;
> @@ -228,7 +222,6 @@ EXPORT_SYMBOL(dma_fence_chain_ops);
>    * @chain: the chain node to initialize
>    * @prev: the previous fence
>    * @fence: the current fence
> - * @seqno: the sequence number (syncpt) of the fence within the chain
>    *
>    * Initialize a new chain node and either start a new chain or add the node to
>    * the existing chain of the previous fence.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-06-25 12:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 12:34 [PATCH 1/2] Revert "dma-buf: Report signaled links inside dma-fence-chain" Lionel Landwerlin
2020-06-25 12:34 ` [PATCH 2/2] dma-buf: fix dma-fence-chain out of order test Lionel Landwerlin
2020-06-25 12:44   ` Christian König
2020-06-25 13:18   ` [Intel-gfx] " Chris Wilson
2020-06-25 13:23     ` Lionel Landwerlin
2020-06-25 13:47       ` Chris Wilson
2020-06-25 13:56         ` Lionel Landwerlin
2020-06-25 13:59       ` Daniel Vetter
2020-07-02 12:57         ` Christian König
2020-06-25 12:43 ` Christian König [this message]
2020-06-25 17:13   ` [Intel-gfx] [PATCH 1/2] Revert "dma-buf: Report signaled links inside dma-fence-chain" Dave Airlie
2020-06-25 19:27     ` Jani Nikula
2020-06-25 19:54       ` Daniel Vetter
2020-06-26  4:43         ` Sumit Semwal
2020-06-26  7:03           ` Christian König
2020-06-26 12:39             ` Daniel Vetter
2020-06-26 15:34               ` Sumit Semwal
2020-06-26  1:36       ` Dave Airlie
2020-07-02  8:26   ` Lionel Landwerlin
2020-07-02  8:28     ` Christian König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51e00eed-c8f1-aabf-ec2c-07be0453ab3b@amd.com \
    --to=christian.koenig@amd.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lionel.g.landwerlin@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).