From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>,
Nayan Deshmukh <nayan26deshmukh@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/scheduler: Remove entity->rq NULL check
Date: Fri, 10 Aug 2018 15:27:50 +0200 [thread overview]
Message-ID: <5bf40a54-18f9-98fd-a3df-dd0b8da0a424@gmail.com> (raw)
In-Reply-To: <54621fc1-7246-f1bf-26bb-a16c4daf249f@amd.com>
[-- Attachment #1.1: Type: text/plain, Size: 2766 bytes --]
Crap, yeah indeed that needs to be protected by some lock.
Going to prepare a patch for that,
Christian.
Am 09.08.2018 um 21:49 schrieb Andrey Grodzovsky:
>
> Reviewed-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>
>
> But I still have questions about entity->last_user (didn't notice
> this before) -
>
> Looks to me there is a race condition with it's current usage, let's
> say process A was preempted after doing
> drm_sched_entity_flush->cmpxchg(...)
>
> now process B working on same entity (forked) is inside
> drm_sched_entity_push_job, he writes his PID to entity->last_user and also
>
> executes drm_sched_rq_add_entity. Now process A runs again and execute
> drm_sched_rq_remove_entity inadvertently causing process B removal
>
> from it's scheduler rq.
>
> Looks to me like instead we should lock together entity->last_user
> accesses and adds/removals of entity to the rq.
>
> Andrey
>
>
> On 08/06/2018 10:18 AM, Nayan Deshmukh wrote:
>> I forgot about this since we started discussing possible scenarios of
>> processes and threads.
>>
>> In any case, this check is redundant. Acked-by: Nayan Deshmukh
>> <nayan26deshmukh@gmail.com <mailto:nayan26deshmukh@gmail.com>>
>>
>> Nayan
>>
>> On Mon, Aug 6, 2018 at 7:43 PM Christian König
>> <ckoenig.leichtzumerken@gmail.com
>> <mailto:ckoenig.leichtzumerken@gmail.com>> wrote:
>>
>> Ping. Any objections to that?
>>
>> Christian.
>>
>> Am 03.08.2018 um 13:08 schrieb Christian König:
>> > That is superflous now.
>> >
>> > Signed-off-by: Christian König <christian.koenig@amd.com
>> <mailto:christian.koenig@amd.com>>
>> > ---
>> > drivers/gpu/drm/scheduler/gpu_scheduler.c | 5 -----
>> > 1 file changed, 5 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/scheduler/gpu_scheduler.c
>> b/drivers/gpu/drm/scheduler/gpu_scheduler.c
>> > index 85908c7f913e..65078dd3c82c 100644
>> > --- a/drivers/gpu/drm/scheduler/gpu_scheduler.c
>> > +++ b/drivers/gpu/drm/scheduler/gpu_scheduler.c
>> > @@ -590,11 +590,6 @@ void drm_sched_entity_push_job(struct
>> drm_sched_job *sched_job,
>> > if (first) {
>> > /* Add the entity to the run queue */
>> > spin_lock(&entity->rq_lock);
>> > - if (!entity->rq) {
>> > - DRM_ERROR("Trying to push to a killed
>> entity\n");
>> > - spin_unlock(&entity->rq_lock);
>> > - return;
>> > - }
>> > drm_sched_rq_add_entity(entity->rq, entity);
>> > spin_unlock(&entity->rq_lock);
>> > drm_sched_wakeup(entity->rq->sched);
>>
>
[-- Attachment #1.2: Type: text/html, Size: 4928 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
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:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:08 [PATCH] drm/scheduler: Remove entity->rq NULL check Christian König
2018-08-06 14:13 ` Christian König
2018-08-06 14:18 ` Nayan Deshmukh
2018-08-09 19:49 ` Andrey Grodzovsky
2018-08-10 13:27 ` Christian König [this message]
2018-08-10 13:44 ` Andrey Grodzovsky
2018-08-13 16:43 ` Andrey Grodzovsky
2018-08-14 7:05 ` Christian König
2018-08-14 15:17 ` Andrey Grodzovsky
2018-08-14 15:26 ` Christian König
2018-08-14 16:32 ` Andrey Grodzovsky
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=5bf40a54-18f9-98fd-a3df-dd0b8da0a424@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).