From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>,
christian.koenig@amd.com,
Nayan Deshmukh <nayan26deshmukh@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/scheduler: stop setting rq to NULL
Date: Fri, 10 Aug 2018 15:16:08 +0200 [thread overview]
Message-ID: <db65d94d-fa99-9cec-af89-4eaecdb9fb00@gmail.com> (raw)
In-Reply-To: <9e29e145-99f1-0723-8562-eb0522d379a4@amd.com>
Am 09.08.2018 um 19:39 schrieb Andrey Grodzovsky:
> [SNIP]
>> SIGKILL isn't processed as long as any thread of the application is
>> still inside the kernel. That's why we have wait_event_killable().
>
> Can you tell me where is this happening ? What i see is in the code is
> that
> do_group_exit calls zap_other_threads which just adds SIGKILL to
> signal sets of other threads in group and sends a wake up.
> Then do_exit will close all FDs for current thread and so .flush will
> be called, when last thread drops it's refcount for the FD .release
> will be called.
Good question, I have not the slightest idea.
Killed processes certainly doesn't die until all threads return from
kernel space, but I'm not 100% sure if that happens before or after the
flush.
Christian.
>
> Andrey
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-10 13:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 11:03 [PATCH 1/2] drm/scheduler: only kill entity if last user is killed v2 Christian König
2018-07-30 11:03 ` [PATCH 2/2] drm/scheduler: stop setting rq to NULL Christian König
2018-07-30 13:30 ` Nayan Deshmukh
2018-07-30 20:51 ` Andrey Grodzovsky
2018-07-31 6:50 ` Christian König
2018-07-31 14:16 ` Andrey Grodzovsky
2018-08-01 22:25 ` Andrey Grodzovsky
2018-08-02 6:42 ` Christian König
2018-08-02 6:47 ` Nayan Deshmukh
2018-08-02 7:26 ` Christian König
2018-08-02 14:11 ` Andrey Grodzovsky
2018-08-03 14:06 ` Christian König
2018-08-03 14:54 ` Andrey Grodzovsky
2018-08-03 16:42 ` Christian König
2018-08-03 18:41 ` Andrey Grodzovsky
2018-08-06 8:14 ` Christian König
2018-08-09 17:39 ` Andrey Grodzovsky
2018-08-10 13:16 ` Christian König [this message]
2018-08-02 6:43 ` Nayan Deshmukh
2018-08-02 14:38 ` Andrey Grodzovsky
2018-08-03 12:12 ` Nayan Deshmukh
2018-08-03 13:47 ` Andrey Grodzovsky
2018-08-03 13:58 ` Nayan Deshmukh
2018-07-30 13:34 ` [PATCH 1/2] drm/scheduler: only kill entity if last user is killed v2 Nayan Deshmukh
2018-07-30 20:42 ` Andrey Grodzovsky
2018-07-31 9:11 ` Nayan Deshmukh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db65d94d-fa99-9cec-af89-4eaecdb9fb00@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Andrey.Grodzovsky@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nayan26deshmukh@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.