All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 01/20] RFT drm/i915/execlists: Flush memory before signaling ELSQ
Date: Wed, 31 Oct 2018 09:05:50 +0000	[thread overview]
Message-ID: <20181031090609.16324-1-chris@chris-wilson.co.uk> (raw)

We observe that the ordering of writes for a CS event is not as strong
from the GPU as we would like, and that on occasions we see the
ringbuffer tail updated before the event is written into the ringbuffer,
leading us to reuse the stale data.

Through around a big hammer to try and batter ELSQ into submission with
the presumption that perhaps the UC mmio write is not flushing our
writes into the context images.

References: https://bugs.freedesktop.org/show_bug.cgi?id=108315
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/intel_lrc.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index 22b57b8926fc..ba61849fbb9b 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -454,8 +454,10 @@ static void execlists_submit_ports(struct intel_engine_cs *engine)
 	}
 
 	/* we need to manually load the submit queue */
-	if (execlists->ctrl_reg)
+	if (execlists->ctrl_reg) {
+		wmb(); /* XXX Big hammer or paper? XXX */
 		writel(EL_CTRL_LOAD, execlists->ctrl_reg);
+	}
 
 	execlists_clear_active(execlists, EXECLISTS_ACTIVE_HWACK);
 }
-- 
2.19.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-10-31  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  9:05 Chris Wilson [this message]
2018-10-31  9:05 ` [PATCH 02/20] drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start Chris Wilson
2018-10-31  9:05 ` [PATCH 03/20] drm/i915: Prevent machine hang from Broxton's vtd w/a and error capture Chris Wilson
2018-10-31  9:05 ` [PATCH 04/20] drm/i915: Always try to reset the GPU on takeover Chris Wilson
2018-10-31  9:05 ` [PATCH 05/20] drm/i915: Cache the error string Chris Wilson
2018-10-31  9:05 ` [PATCH 06/20] drm/i915: Report the number of closed vma held by each context in debugfs Chris Wilson
2018-10-31  9:05 ` [PATCH 07/20] drm/i915: Remove debugfs/i915_ppgtt_info Chris Wilson
2018-10-31  9:05 ` [PATCH 08/20] drm/i915: Track all held rpm wakerefs Chris Wilson
2018-10-31  9:05 ` [PATCH 09/20] drm/i915: Markup paired operations on wakerefs Chris Wilson
2018-10-31  9:05 ` [PATCH 10/20] drm/i915: Syntatic sugar for using intel_runtime_pm Chris Wilson
2018-10-31  9:06 ` [PATCH 11/20] drm/i915: Markup paired operations on display power domains Chris Wilson
2018-10-31  9:06 ` [PATCH 12/20] drm/i915: Track the wakeref used to initialise " Chris Wilson
2018-10-31  9:06 ` [PATCH 13/20] drm/i915: Combined gt.awake/gt.power wakerefs Chris Wilson
2018-10-31  9:06 ` [PATCH 14/20] drm/i915/dp: Markup pps lock power well Chris Wilson
2018-10-31  9:06 ` [PATCH 15/20] drm/i915: Complain if hsw_get_pipe_config acquires the same power well twice Chris Wilson
2018-10-31  9:06 ` [PATCH 16/20] drm/i915: Mark up Ironlake ips with rpm wakerefs Chris Wilson
2018-10-31  9:06 ` [PATCH 17/20] drm/i915: Serialise concurrent calls to i915_gem_set_wedged() Chris Wilson
2018-10-31  9:06 ` [PATCH 18/20] drm/i915: Differentiate between ggtt->mutex and ppgtt->mutex Chris Wilson
2018-10-31  9:06 ` [PATCH 19/20] drm/i915: Pull all the reset functionality together into i915_reset.c Chris Wilson
2018-10-31  9:06 ` [PATCH 20/20] drm/i915: Make all GPU resets atomic Chris Wilson
2018-10-31 12:10 ` ✗ Fi.CI.BAT: failure for series starting with [01/20] RFT drm/i915/execlists: Flush memory before signaling ELSQ 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=20181031090609.16324-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.