From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder
Date: Wed, 28 Aug 2019 15:49:55 +0300 [thread overview]
Message-ID: <877e6xxxn0.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190827120615.31390-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quite rarely we see that the CS completion event fires before the
> breadcrumb is coherent, which presumably is a result of the CS_STALL not
> waiting for the post-sync operation. Try following in a DC_FLUSH into
> the following pipecontrol to see if that makes any difference.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 80a3f1dbb456..48046d445733 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -2971,6 +2971,7 @@ static u32 *gen8_emit_fini_breadcrumb_rcs(struct i915_request *request, u32 *cs)
> /* XXX flush+write+CS_STALL all in one upsets gem_concurrent_blt:kbl */
> cs = gen8_emit_pipe_control(cs,
> PIPE_CONTROL_FLUSH_ENABLE |
> + PIPE_CONTROL_DC_FLUSH_ENABLE |
> PIPE_CONTROL_CS_STALL,
> 0);
>
> --
> 2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-28 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 12:06 [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder Chris Wilson
2019-08-27 13:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-28 12:12 ` ✓ Fi.CI.IGT: " Patchwork
2019-08-28 12:49 ` Mika Kuoppala [this message]
2019-08-28 13:09 ` [PATCH] " Chris Wilson
2019-08-28 18:09 ` Chris Wilson
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=877e6xxxn0.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 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.