Re: [PATCH 2/2] drm/i915: Remove last traces of exec-id (GEM_BUSY)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Tvrtko Ursulin (2019-03-05 14:47:51)
> 
> On 02/03/2019 10:06, Chris Wilson wrote:
> > As we allow per-context engine allows the legacy concept of
> > I915_EXEC_RING no longer applies universally. We are still exposing the
> > unrelated exec-id in GEM_BUSY, so transition this ioctl (once more
> > slightly changing its ABI, but no one cares) over to only reporting the
> > uabi-class (not instance as we can not foreseeably fit those into the
> > small bitmask).
> > 
> > The only user of the extended ring information from GEM_BUSY is ddx/sna,
> > which tries to use the non-rcs business information to guide which
> > engine to use for subsequent operations on foreign bo. All that matters
> > for it is the decision between rcs and !rcs, so it is unaffected by the
> > change in higher bits.
> > 
> > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx>

I need a corresponding ack on 
https://patchwork.freedesktop.org/series/57457/
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux