From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
Jingwen Chen <Jingwen.Chen2@amd.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
"monk.liu" <monk.liu@amd.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH v2] Revert "drm/scheduler: Avoid accessing freed bad job."
Date: Wed, 18 Aug 2021 10:26:25 -0400 [thread overview]
Message-ID: <69cbf5bd-42c2-be55-a604-43f4ebba159d@amd.com> (raw)
In-Reply-To: <CADnq5_OApvH1Jo2VzJBHewHB_LXgg1WzUHvTBvrNYnbYdFAWhQ@mail.gmail.com>
On 2021-08-18 10:02 a.m., Alex Deucher wrote:
> + dri-devel
>
> Since scheduler is a shared component, please add dri-devel on all
> scheduler patches.
>
> On Wed, Aug 18, 2021 at 7:21 AM Jingwen Chen <Jingwen.Chen2@amd.com> wrote:
>> [Why]
>> for bailing job, this commit will delete it from pending list thus the
>> bailing job will never have a chance to be resubmitted even in advance
>> tdr mode.
>>
>> [How]
>> after embeded hw_fence into amdgpu_job is done, the race condition that
>> this commit tries to work around is completely solved.So revert this
>> commit.
>> This reverts commit 135517d3565b48f4def3b1b82008bc17eb5d1c90.
>> v2:
>> add dma_fence_get/put() around timedout_job to avoid concurrent delete
>> during processing timedout_job
>>
>> Signed-off-by: Jingwen Chen <Jingwen.Chen2@amd.com>
>> ---
>> drivers/gpu/drm/scheduler/sched_main.c | 23 +++++------------------
>> 1 file changed, 5 insertions(+), 18 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
>> index a2a953693b45..f9b9b3aefc4a 100644
>> --- a/drivers/gpu/drm/scheduler/sched_main.c
>> +++ b/drivers/gpu/drm/scheduler/sched_main.c
>> @@ -314,6 +314,7 @@ static void drm_sched_job_timedout(struct work_struct *work)
>> {
>> struct drm_gpu_scheduler *sched;
>> struct drm_sched_job *job;
>> + struct dma_fence *fence;
>> enum drm_gpu_sched_stat status = DRM_GPU_SCHED_STAT_NOMINAL;
>>
>> sched = container_of(work, struct drm_gpu_scheduler, work_tdr.work);
>> @@ -325,11 +326,10 @@ static void drm_sched_job_timedout(struct work_struct *work)
>>
>> if (job) {
>> /*
>> - * Remove the bad job so it cannot be freed by concurrent
>> - * drm_sched_cleanup_jobs. It will be reinserted back after sched->thread
>> - * is parked at which point it's safe.
>> + * Get job->s_fence->parent here to avoid concurrent delete during
>> + * processing timedout_job
>> */
>> - list_del_init(&job->list);
>> + fence = dma_fence_get(job->s_fence->parent);
While this is true for amdgpu, it has no meaning for other drivers for
whom we haven't
done the refactoring of embedding HW fence (parent) into the job
structure. In fact thinking
about it, unless you do the HW fence embedding for all the drivers using
the scheduler you cannot
revert this patch or you will just break them.
Andrey
>> spin_unlock(&sched->job_list_lock);
>>
>> status = job->sched->ops->timedout_job(job);
>> @@ -342,6 +342,7 @@ static void drm_sched_job_timedout(struct work_struct *work)
>> job->sched->ops->free_job(job);
>> sched->free_guilty = false;
>> }
>> + dma_fence_put(fence);
>> } else {
>> spin_unlock(&sched->job_list_lock);
>> }
>> @@ -392,20 +393,6 @@ void drm_sched_stop(struct drm_gpu_scheduler *sched, struct drm_sched_job *bad)
>>
>> kthread_park(sched->thread);
>>
>> - /*
>> - * Reinsert back the bad job here - now it's safe as
>> - * drm_sched_get_cleanup_job cannot race against us and release the
>> - * bad job at this point - we parked (waited for) any in progress
>> - * (earlier) cleanups and drm_sched_get_cleanup_job will not be called
>> - * now until the scheduler thread is unparked.
>> - */
>> - if (bad && bad->sched == sched)
>> - /*
>> - * Add at the head of the queue to reflect it was the earliest
>> - * job extracted.
>> - */
>> - list_add(&bad->list, &sched->pending_list);
>> -
>> /*
>> * Iterate the job list from later to earlier one and either deactive
>> * their HW callbacks or remove them from pending list if they already
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2021-08-18 14:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 11:21 [PATCH v2] Revert "drm/scheduler: Avoid accessing freed bad job." Jingwen Chen
2021-08-18 14:02 ` Alex Deucher
2021-08-18 14:26 ` Andrey Grodzovsky [this message]
2021-08-18 14:32 ` Daniel Vetter
2021-08-18 14:36 ` Andrey Grodzovsky
2021-08-18 14:42 ` Daniel Vetter
2021-08-18 14:51 ` Andrey Grodzovsky
2021-08-19 9:30 ` Daniel Vetter
2021-08-19 10:25 ` Liu, Monk
2021-08-20 7:12 ` Liu, Monk
2021-08-20 7:20 ` Christian König
2021-08-20 8:09 ` Jingwen Chen
2021-08-20 13:49 ` Andrey Grodzovsky
2021-08-26 8:59 ` Daniel Vetter
2021-08-20 14:07 ` Andrey Grodzovsky
2021-08-24 7:24 ` Liu, Monk
2021-08-24 14:23 ` Andrey Grodzovsky
2023-06-08 16:40 ` Lucas Stach
2021-08-19 15:25 ` Andrey Grodzovsky
2021-08-26 9:04 ` Daniel Vetter
2021-08-31 13:11 ` Daniel Vetter
2021-08-31 18:24 ` Andrey Grodzovsky
2021-09-02 14:28 ` Daniel Vetter
2021-09-02 15:36 ` Andrey Grodzovsky
2021-09-07 8:47 ` Daniel Vetter
2021-09-07 9:25 ` Christian König
2021-08-19 3:01 ` Liu, Monk
2021-08-19 9:24 ` Daniel Vetter
2021-08-18 14:29 ` Daniel Vetter
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=69cbf5bd-42c2-be55-a604-43f4ebba159d@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=Jingwen.Chen2@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=monk.liu@amd.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