From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/5] drm/i915: implement SNB workaround for lazy global gtt
Date: Thu, 16 Feb 2012 00:25:42 +0100 [thread overview]
Message-ID: <20120215232542.GF26578@phenom.ffwll.local> (raw)
In-Reply-To: <e39f63$3o5bcf@fmsmga002.fm.intel.com>
On Wed, Feb 15, 2012 at 11:10:08PM +0000, Chris Wilson wrote:
> On Wed, 15 Feb 2012 23:50:23 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > + /* Sandybridge PPGTT errata: We need a global gtt mapping for MI and
> > + * pipe_control writes because the gpu doesn't properly redirect them
> > + * through the ppgtt for non_secure batchbuffers. */
> > + if (unlikely(IS_GEN6(dev) &&
> > + reloc->write_domain == I915_GEM_DOMAIN_INSTRUCTION &&
> > + !target_i915_obj->has_global_gtt_mapping)) {
> > + i915_gem_gtt_bind_object(target_i915_obj,
> > + target_i915_obj->cache_level);
> > + target_i915_obj->has_global_gtt_mapping = 1;
>
> i915_gem_gtt_bind_object() sets has_global_gtt_mapping, so no need to
> repeat ourselves here.
Indeed, that's superflous. I'll kill this line when applying it (the
machine with the patches is already down and I'm a lazy bastard ...).
> I guess that was the easy one you throw in to make sure people are
> reading your patches?
>
> A little uneasy still with that heuristic, but I have to agree that it
> is the lesser of the evils, meh.
Luckily pipe_control writes on snb are extremely broken with ppgtt, so we
should notice immediately if someone sets the wrong domain (as I did in
the broken i-g-t test).
> I'm pretty happy now with this series as I've been beating upon it ever
> since it landed in danvet/my-next, so
> Reviewed-and-tested-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks,
Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-02-15 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 22:50 [PATCH 0/5] aliasing ppgtt, advanced things Daniel Vetter
2012-02-15 22:50 ` [PATCH 1/5] drm/i915: split out dma mapping from global gtt bind/unbind functions Daniel Vetter
2012-02-15 22:50 ` [PATCH 2/5] drm/i915: bind objects to the global gtt only when needed Daniel Vetter
2012-02-15 22:50 ` [PATCH 3/5] drm/i915: implement SNB workaround for lazy global gtt Daniel Vetter
2012-02-15 23:10 ` Chris Wilson
2012-02-15 23:25 ` Daniel Vetter [this message]
2012-03-20 20:57 ` Daniel Vetter
2012-02-15 22:50 ` [PATCH 4/5] drm/i915: enable lazy global-gtt binding Daniel Vetter
2012-02-15 22:50 ` [PATCH 5/5] drm/i915: add HAS_ALIASING_PPGTT parameter for userspace Daniel Vetter
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=20120215232542.GF26578@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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