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 wrote:
> > > On Thu, Jul 24, 2014 at 12:48:33PM +0100, Chris Wilson wrote:
> > >> One of the side-effects we test for are kernel oop
On Thu, Jul 24, 2014 at 02:03:01PM +0100, Thomas Wood wrote:
> On 24 July 2014 13:36, Daniel Vetter 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
On 24 July 2014 13:36, Daniel Vetter 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
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-o
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
---
lib/igt_core.c | 29
