On Fri, Feb 21, 2014 at 06:13:51PM +0200, Mika Kuoppala wrote: > Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> writes: > > > ville.syrjala@xxxxxxxxxxxxxxx writes: > > > >> From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > >> > >> If we've explicitly stopped the rings for testing purposes, don't ban > >> the default context. Fixes kms_flip hang tests. > >> > > > > To keep logs clean from 'unnecessary' hang messages we set stop_rings also on > > all the gem_reset_stats hanging tests. I think this breaks all the ban > > tests on gem_reset_stats. > > > > So we have dig this nice hole, for avoiding dmesg output on cases > > where dmesg output should be valid and justificed. > > I think the correct solution is to have white lists for dmesg output > in piglit test runner, so that we can remove this overloading of > stop_rings. > > Injecting proper hang should output a proper log message and this > should be testable. The important part is that tests dont hit a DRM_ERROR, since that will both upset piglit and also QA's testing infrastructure. Ville's patch seems to dtrt by using DRM_DEBUG for non-default context banning. Also with hw contexts and the reset stats stuff we expect some userspace apps to hang the gpu often (malicious webgl shaders with inifite loops), so debug level is the right thing anyway - usespace should not be allowed to spam dmesg. Queued for -next, thanks for the patch. -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
