On Wed, Jun 18, 2014 at 10:52:08PM +0200, Daniel Vetter wrote: > On Fri, Jun 13, 2014 at 04:38:01PM +0100, oscar.mateo@xxxxxxxxx wrote: > > From: Oscar Mateo <oscar.mateo@xxxxxxxxx> > > > > Since the ringbuffer does not belong per engine anymore, we have to > > make sure that we are always recording the correct ringbuffer. > > > > TODO: This is only a small fix to keep basic error capture working, but > > we need to add more information for it to be useful (e.g. dump the > > context being executed). > > I think we should dump the two lrc submitted to the hw port (our decoder > can deal with arbitrary amounts of rings, just name them foo1 and foo2) > and the overall execlist submission queue with a few hints what's going on > should be a useful start. The scheduler patches can then pimp this further > I guess. ofc this can be done later on, but needs to be tracked somewhere. Historically we suck badly at delivering such follow-up work. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
