On Thursday, April 6, 2017 3:52:06 AM PDT Chris Wilson wrote:
> On Wed, Apr 05, 2017 at 04:56:42PM -0700, Kenneth Graunke wrote:
> > On Wednesday, April 5, 2017 4:46:27 AM PDT Chris Wilson wrote:
> > > On Tue, Apr 04, 2017 at 05:10:30PM -0700, Kenneth Graunke wrote:
[snip]
> > > > + batch->reloc_
On Wed, Apr 05, 2017 at 04:56:42PM -0700, Kenneth Graunke wrote:
> On Wednesday, April 5, 2017 4:46:27 AM PDT Chris Wilson wrote:
> > On Tue, Apr 04, 2017 at 05:10:30PM -0700, Kenneth Graunke wrote:
> > > The execbuf2 kernel API requires us to construct two kinds of lists.
> > > First is a "validat
On Wednesday, April 5, 2017 4:46:27 AM PDT Chris Wilson wrote:
> On Tue, Apr 04, 2017 at 05:10:30PM -0700, Kenneth Graunke wrote:
> > The execbuf2 kernel API requires us to construct two kinds of lists.
> > First is a "validation list" (struct drm_i915_gem_exec_object2[])
> > containing each BO ref
On Tue, Apr 04, 2017 at 05:10:30PM -0700, Kenneth Graunke wrote:
> The execbuf2 kernel API requires us to construct two kinds of lists.
> First is a "validation list" (struct drm_i915_gem_exec_object2[])
> containing each BO referenced by the batch. (The batch buffer itself
> must be the last entr
The execbuf2 kernel API requires us to construct two kinds of lists.
First is a "validation list" (struct drm_i915_gem_exec_object2[])
containing each BO referenced by the batch. (The batch buffer itself
must be the last entry in this list.) Each validation list entry
contains a pointer to the se
