All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH v2] drm/i915: Drop ORIGIN_GTT for untracked GTT writes
Date: Thu, 18 Aug 2016 17:56:50 +0300	[thread overview]
Message-ID: <1471532210.3659.12.camel@linux.intel.com> (raw)
In-Reply-To: <20160818142621.2639-1-chris@chris-wilson.co.uk>

On to, 2016-08-18 at 15:26 +0100, Chris Wilson wrote:
> If FBC is set on a framebuffer that is unmapped, all GTT faults will be
> from a partial mapping. Writes by the user through the partial VMA are
> then untracked by the FBC and so we must use the ORIGIN_CPU when flushing
> the I915_GEM_DOMAIN_GTT.
> 
> v2: Keep ORIGIN_CPU for set-to-domain(.write=CPU)
> 

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-08-18 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  8:20 [PATCH] drm/i915: Drop ORIGIN_GTT for untracked GTT writes Chris Wilson
2016-08-18  8:30 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-18 14:26 ` [PATCH v2] " Chris Wilson
2016-08-18 14:56   ` Joonas Lahtinen [this message]
2016-08-18 14:30 ` ✗ Ro.CI.BAT: failure for drm/i915: Drop ORIGIN_GTT for untracked GTT writes (rev2) 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=1471532210.3659.12.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    /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.