Re: [PATCH 01/15] drm/i915: Add i915_gem_object_write() to i915_gem.c

From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/15] drm/i915: Add i915_gem_object_write() to i915_gem.c
Date: Thu, 18 Jun 2015 13:10:34 +0100	[thread overview]
Message-ID: <20150618121034.GL24012@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <5582B063.6060700@intel.com>

On Thu, Jun 18, 2015 at 12:49:55PM +0100, Dave Gordon wrote:
> On 17/06/15 13:02, Daniel Vetter wrote:
> > Domain handling is required for all gem objects, and the resulting bugs if
> > you don't for one-off objects are absolutely no fun to track down.
> 
> Is it not the case that the new object returned by
> i915_gem_alloc_object() is
> (a) of a type that can be mapped into the GTT, and
> (b) initially in the CPU domain for both reading and writing?
> 
> So AFAICS the allocate-and-fill function I'm describing (to appear in
> next patch series respin) doesn't need any further domain handling.

A i915_gem_object_create_from_data() is a reasonable addition, and I
suspect it will make the code a bit more succinct.

Whilst your statement is true today, calling set_domain is then a no-op,
and helps document how you use the object and so reduces the likelihood
of us introducing bugs in the future.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx