On ti, 2016-07-26 at 09:19 +0100, Chris Wilson wrote:
> On Tue, Jul 26, 2016 at 07:59:29AM +0300, Joonas Lahtinen wrote:
> >
> > On ma, 2016-07-25 at 18:31 +0100, Chris Wilson wrote:
> >
> > >
> > > Inside the error capture itself, we refer to not only the hardware
> > > engine, its ringbuffer
On Tue, Jul 26, 2016 at 07:59:29AM +0300, Joonas Lahtinen wrote:
> On ma, 2016-07-25 at 18:31 +0100, Chris Wilson wrote:
>
> > Inside the error capture itself, we refer to not only the hardware
> > engine, its ringbuffer but also the capture state. Finding clear names
> > for each whilst avoiding
On ma, 2016-07-25 at 18:31 +0100, Chris Wilson wrote:
> Inside the error capture itself, we refer to not only the hardware
> engine, its ringbuffer but also the capture state. Finding clear names
> for each whilst avoiding mixing ring/intel_engine_cs is tricky. As a
> compromise we keep using
Inside the error capture itself, we refer to not only the hardware
engine, its ringbuffer but also the capture state. Finding clear names
for each whilst avoiding mixing ring/intel_engine_cs is tricky. As a
compromise we keep using ering for the error capture.
Signed-off-by: Chris Wilson
