[PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.
oleg at redhat.com
Mon Apr 30 15:29:41 UTC 2018
On 04/30, Christian König wrote:
> Well when the process is killed we don't care about correctness any more, we
> just want to get rid of it as quickly as possible (OOM situation etc...).
> But it is perfectly possible that a process submits some render commands and
> then calls exit() or terminates because of a SIGTERM, SIGINT etc..
This doesn't differ from SIGKILL. I mean, any unhandled fatal signal translates
to SIGKILL and I think this is fine.
but this doesn't really matter,
> So what we essentially need is to distinct between a SIGKILL (which means
> stop processing as soon as possible) and any other reason because then we
> don't want to annoy the user with garbage on the screen (even if it's just
> for a few milliseconds).
OK, I see another email from Andrey, I'll reply to that email...
More information about the amd-gfx