Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH 1/7] drm/i915/gem: Remove redundant exec_fence
Date: Wed, 13 May 2020 20:45:51 +0300	[thread overview]
Message-ID: <877dxfvicw.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200513165937.9508-1-chris@chris-wilson.co.uk>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> Since there can only be one of in_fence/exec_fence, just use the single
> in_fence local.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  .../gpu/drm/i915/gem/i915_gem_execbuffer.c    | 24 ++++++++-----------
>  1 file changed, 10 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> index d54a4933cc05..824a2b76947a 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> @@ -2622,7 +2622,6 @@ i915_gem_do_execbuffer(struct drm_device *dev,
>  	struct drm_i915_private *i915 = to_i915(dev);
>  	struct i915_execbuffer eb;
>  	struct dma_fence *in_fence = NULL;
> -	struct dma_fence *exec_fence = NULL;
>  	struct sync_file *out_fence = NULL;
>  	struct i915_vma *batch;
>  	int out_fence_fd = -1;
> @@ -2677,8 +2676,8 @@ i915_gem_do_execbuffer(struct drm_device *dev,
>  			goto err_in_fence;
>  		}
>  
> -		exec_fence = sync_file_get_fence(lower_32_bits(args->rsvd2));
> -		if (!exec_fence) {
> +		in_fence = sync_file_get_fence(lower_32_bits(args->rsvd2));
> +		if (!in_fence) {

This looks wrong. Seems you can return straight from here.
-Mika


>  			err = -EINVAL;
>  			goto err_in_fence;
>  		}
> @@ -2688,7 +2687,7 @@ i915_gem_do_execbuffer(struct drm_device *dev,
>  		out_fence_fd = get_unused_fd_flags(O_CLOEXEC);
>  		if (out_fence_fd < 0) {
>  			err = out_fence_fd;
> -			goto err_exec_fence;
> +			goto err_in_fence;
>  		}
>  	}
>  
> @@ -2779,14 +2778,13 @@ i915_gem_do_execbuffer(struct drm_device *dev,
>  	}
>  
>  	if (in_fence) {
> -		err = i915_request_await_dma_fence(eb.request, in_fence);
> -		if (err < 0)
> -			goto err_request;
> -	}
> -
> -	if (exec_fence) {
> -		err = i915_request_await_execution(eb.request, exec_fence,
> -						   eb.engine->bond_execute);
> +		if (args->flags & I915_EXEC_FENCE_SUBMIT)
> +			err = i915_request_await_execution(eb.request,
> +							   in_fence,
> +							   eb.engine->bond_execute);
> +		else
> +			err = i915_request_await_dma_fence(eb.request,
> +							   in_fence);
>  		if (err < 0)
>  			goto err_request;
>  	}
> @@ -2855,8 +2853,6 @@ i915_gem_do_execbuffer(struct drm_device *dev,
>  err_out_fence:
>  	if (out_fence_fd != -1)
>  		put_unused_fd(out_fence_fd);
> -err_exec_fence:
> -	dma_fence_put(exec_fence);
>  err_in_fence:
>  	dma_fence_put(in_fence);
>  	return err;
> -- 
> 2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-05-13 17:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 16:59 [Intel-gfx] [PATCH 1/7] drm/i915/gem: Remove redundant exec_fence Chris Wilson
2020-05-13 16:59 ` [Intel-gfx] [PATCH 2/7] drm/i915: Mark the addition of the initial-breadcrumb in the request Chris Wilson
2020-05-13 18:09   ` Mika Kuoppala
2020-05-13 16:59 ` [Intel-gfx] [PATCH 3/7] dma-buf: Proxy fence, an unsignaled fence placeholder Chris Wilson
2020-05-13 16:59 ` [Intel-gfx] [PATCH 4/7] drm/syncobj: Allow use of dma-fence-proxy Chris Wilson
2020-05-13 16:59 ` [Intel-gfx] [PATCH 5/7] drm/i915/gem: Teach execbuf how to wait on future syncobj Chris Wilson
2020-05-13 16:59 ` [Intel-gfx] [PATCH 6/7] drm/i915/gem: Allow combining submit-fences with syncobj Chris Wilson
2020-05-13 16:59 ` [Intel-gfx] [PATCH 7/7] drm/i915/gt: Declare when we enabled timeslicing Chris Wilson
2020-05-13 17:45 ` Mika Kuoppala [this message]
2020-05-13 17:56 ` [Intel-gfx] [PATCH v2] drm/i915/gem: Remove redundant exec_fence Chris Wilson
2020-05-13 18:01   ` Mika Kuoppala
2020-05-13 17:56 ` Chris Wilson
2020-05-13 18:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2] drm/i915/gem: Remove redundant exec_fence (rev3) Patchwork
2020-05-13 19:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-13 23:16 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=877dxfvicw.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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