+ Petri for the fact that igt_fork is actually igt_forkoontula and
messes up set up signal handlers when transitioning to child.

Quoting Chris Wilson (2019-02-08 11:01:55)
> Quoting Joonas Lahtinen (2019-02-08 08:59:53)
> > Quoting Chris Wilson (2019-02-07 23:03:08)
> > > Make sure that the SIGARLM handler is captured so that we don't
> > > accidentally shoot ourselves in the foot instead of merely waking up the
> > > execbuf.
> > > 
> > > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
> > 
> > Warming up the context ahead of time is reasonable for super low SKUs.
> > 
> > But the SIGALRM handler should be inherted, so that's a red herring.
> 
> It wasn't.
> 
>         child 0 died with signal 14, Alarm clock

Ugh, I'm just running a miniature version locally and it *does* get
inherited here.

Add a big fat "/* FIXME: IGT should not mess the SIGALRM handler */"
above the line, and keep the R-b, then.

Regards, Joonas

> 
> -> hit SIG_DFL
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to