From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] [PATCH 1/9] drm/i915: Ignore submit-fences on the same timeline
Date: Fri, 8 May 2020 10:29:25 +0100 [thread overview]
Message-ID: <20200508092933.738-1-chris@chris-wilson.co.uk> (raw)
While we ordinarily do not skip submit-fences due to the accompanying
hook that we want to callback on execution, a submit-fence on the same
timeline is meaningless.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_request.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
index 589739bfee25..be2ce9065a29 100644
--- a/drivers/gpu/drm/i915/i915_request.c
+++ b/drivers/gpu/drm/i915/i915_request.c
@@ -1242,6 +1242,9 @@ i915_request_await_execution(struct i915_request *rq,
continue;
}
+ if (fence->context == rq->fence.context)
+ continue;
+
/*
* We don't squash repeated fence dependencies here as we
* want to run our callback in all cases.
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-05-08 9:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 9:29 Chris Wilson [this message]
2020-05-08 9:29 ` [Intel-gfx] [PATCH 2/9] drm/i915: Pull waiting on an external dma-fence into its routine Chris Wilson
2020-05-08 10:19 ` Mika Kuoppala
2020-05-08 10:26 ` Chris Wilson
2020-05-08 10:27 ` Chris Wilson
2020-05-08 11:08 ` Mika Kuoppala
2020-05-08 9:29 ` [Intel-gfx] [PATCH 3/9] drm/i915: Prevent using semaphores to chain up to external fences Chris Wilson
2020-05-08 15:37 ` Mika Kuoppala
2020-05-08 15:43 ` Chris Wilson
2020-05-08 15:44 ` Mika Kuoppala
2020-05-08 15:56 ` Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 4/9] drm/i915: Tidy awaiting on dma-fences Chris Wilson
2020-05-08 15:50 ` Mika Kuoppala
2020-05-08 15:58 ` Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 5/9] dma-buf: Proxy fence, an unsignaled fence placeholder Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 6/9] drm/syncobj: Allow use of dma-fence-proxy Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 7/9] drm/i915/gem: Teach execbuf how to wait on future syncobj Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 8/9] drm/i915/gem: Allow combining submit-fences with syncobj Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 9/9] drm/i915/gt: Declare when we enabled timeslicing Chris Wilson
2020-05-08 9:57 ` [Intel-gfx] [PATCH 1/9] drm/i915: Ignore submit-fences on the same timeline Mika Kuoppala
2020-05-08 10:09 ` Chris Wilson
2020-05-08 11:11 ` Mika Kuoppala
2020-05-08 10:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] " Patchwork
2020-05-08 10:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-08 12:27 ` [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=20200508092933.738-1-chris@chris-wilson.co.uk \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.