On Thu, Jul 24, 2014 at 02:58:08PM +0100, Chris Wilson wrote: > On Thu, Jul 24, 2014 at 02:03:01PM +0100, Thomas Wood wrote: > > On 24 July 2014 13:36, Daniel Vetter <daniel@xxxxxxxx> wrote: > > > On Thu, Jul 24, 2014 at 12:48:33PM +0100, Chris Wilson wrote: > > >> One of the side-effects we test for are kernel oops and knowing the > > >> guilty subtest can help speed up debugging. We can write to /dev/kmsg to > > >> inject messages into dmesg, so let's do so before the start of every > > >> test. > > >> > > >> Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > > > > Should we change proc->comm too? Would help with the oops printing ... Ack > > > on the patch itself. > > > > It should also make sure that the log level is appropriate so that the > > Piglit dmesg capture isn't triggered accidentally. > > I found out how to set the log-level, so choose KERN_INFO which should be > sufficient. > > > Would it be useful to include this in simple tests (tests without > > subtests) as well? > > Definitely. Is there a way to do that automatically or do we need to > adjust the tests themselves? I was thinkg we could add a kmsg() to > common_init() to capture those. common_init kmsg'ing the test binary should be good. That should help in lining up any test setup work that's done before the first test starts, too. So useful even with subtests. -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
