All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i915/tgl: Advanced preparser support for GPU relocs
Date: Fri, 23 Aug 2019 08:27:25 +0100	[thread overview]
Message-ID: <156654524525.27716.6405573408447860616@skylake-alporthouse-com> (raw)
In-Reply-To: <20190823020909.6029-1-daniele.ceraolospurio@intel.com>

Quoting Daniele Ceraolo Spurio (2019-08-23 03:09:09)
> TGL has an improved CS pre-parser that can now pre-fetch commands across
> batch boundaries. This improves performances when lots of small batches
> are used, but has an impact on self-modifying code. If we want to modify
> the content of a batch from another ring/batch, we need to either
> guarantee that the memory location is updated before the pre-parser gets
> to it or we need to turn the pre-parser off around the modification.
> In i915, we use self-modifying code only for GPU relocations.
> 
> The pre-parser fetches across memory synchronization commands as well,
> so the only way to guarantee that the writes land before the parser gets
> to it is to have more instructions between the sync and the destination
> than the parser FIFO depth, which is not an optimal solution.

Well, our ABI is that memory is coherent before the breadcrumb of *each*
batch. That is a fundamental requirement for our signaling to userspace.
Please tell me that there is a context flag to turn this off, or we else
we need to emit 32x flushes or whatever it takes.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-08-23  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23  2:09 [RFC] drm/i915/tgl: Advanced preparser support for GPU relocs Daniele Ceraolo Spurio
2019-08-23  2:39 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-23  3:41 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-23  7:27 ` Chris Wilson [this message]
2019-08-23 14:26   ` [RFC] " Chris Wilson
2019-08-23 15:05     ` Daniele Ceraolo Spurio
2019-08-23 15:10       ` Chris Wilson
2019-08-23 15:28         ` Chris Wilson
2019-08-23 15:39           ` Daniele Ceraolo Spurio
2019-08-23 15:52             ` Chris Wilson
2019-08-23 15:56               ` Daniele Ceraolo Spurio
2019-08-23 16:31                 ` Chris Wilson
2019-08-23 17:01                   ` Daniele Ceraolo Spurio
2019-08-23 17:28                     ` 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=156654524525.27716.6405573408447860616@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniele.ceraolospurio@intel.com \
    --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.