<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/scheduler, branch linux-5.3.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.3.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.3.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2019-11-12T18:28:11Z</updated>
<entry>
<title>drm/sched: Set error to s_fence if HW job submission failed.</title>
<updated>2019-11-12T18:28:11Z</updated>
<author>
<name>Andrey Grodzovsky</name>
</author>
<published>2019-10-24T19:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e8dc41bdb82911e657277cb8f7c1ea933b9fef70'/>
<id>urn:sha1:e8dc41bdb82911e657277cb8f7c1ea933b9fef70</id>
<content type='text'>
[ Upstream commit 167bf96014a095753053595f3224fcdeb49ac3c8 ]

Problem:
When run_job fails and HW fence returned is NULL we still signal
the s_fence to avoid hangs but the user has no way of knowing if
the actual HW job was ran and finished.

Fix:
Allow .run_job implementations to return ERR_PTR in the fence pointer
returned and then set this error for s_fence-&gt;finished fence so whoever
wait on this fence can inspect the signaled fence for an error.

Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>drm/scheduler: use job count instead of peek</title>
<updated>2019-08-14T20:45:53Z</updated>
<author>
<name>Christian König</name>
</author>
<published>2019-08-09T15:27:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e1b4ce25dbc93ab0cb8ed0f236a3b9ff7b03802c'/>
<id>urn:sha1:e1b4ce25dbc93ab0cb8ed0f236a3b9ff7b03802c</id>
<content type='text'>
The spsc_queue_peek function is accessing queue-&gt;head which belongs to
the consumer thread and shouldn't be accessed by the producer

This is fixing a rare race condition when destroying entities.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Acked-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Reviewed-by: Monk.liu@amd.com
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/sched: Fix make htmldocs warnings.</title>
<updated>2019-05-29T16:49:51Z</updated>
<author>
<name>Andrey Grodzovsky</name>
</author>
<published>2019-05-29T14:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d0f29d4980cdf18295e34d0a57788ad6663cbf88'/>
<id>urn:sha1:d0f29d4980cdf18295e34d0a57788ad6663cbf88</id>
<content type='text'>
Document the missing parameters.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/1559140180-6762-1-git-send-email-andrey.grodzovsky@amd.com
</content>
</entry>
<entry>
<title>drm/sched: Fix static checker warning for potential NULL ptr</title>
<updated>2019-05-24T18:21:06Z</updated>
<author>
<name>Andrey Grodzovsky</name>
</author>
<published>2019-05-22T13:57:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b576ff902f8a050eb5b5ba9a016cb9212f730b05'/>
<id>urn:sha1:b576ff902f8a050eb5b5ba9a016cb9212f730b05</id>
<content type='text'>
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/1558533443-7795-1-git-send-email-andrey.grodzovsky@amd.com
</content>
</entry>
<entry>
<title>Merge drm/drm-next into drm-misc-next</title>
<updated>2019-05-22T20:08:21Z</updated>
<author>
<name>Sean Paul</name>
</author>
<published>2019-05-22T20:08:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=374ed5429346a021c8e2d26fafce14c5b15dedd0'/>
<id>urn:sha1:374ed5429346a021c8e2d26fafce14c5b15dedd0</id>
<content type='text'>
Backmerging 5.2-rc1 to -misc-next for robher

Signed-off-by: Sean Paul &lt;seanpaul@chromium.org&gt;
</content>
</entry>
<entry>
<title>drm/scheduler: Fix job cleanup without timeout handler</title>
<updated>2019-05-22T06:42:50Z</updated>
<author>
<name>Erico Nunes</name>
</author>
<published>2019-05-20T23:16:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=794c686eb7830b12e27999fd776f6d021ce22658'/>
<id>urn:sha1:794c686eb7830b12e27999fd776f6d021ce22658</id>
<content type='text'>
After "5918045c4ed4 drm/scheduler: rework job destruction", jobs are
only deleted when the timeout handler is able to be cancelled
successfully.

In case no timeout handler is running (timeout == MAX_SCHEDULE_TIMEOUT),
job cleanup would be skipped which may result in memory leaks.

Add the handling for the (timeout == MAX_SCHEDULE_TIMEOUT) case in
drm_sched_cleanup_jobs.

Signed-off-by: Erico Nunes &lt;nunes.erico@gmail.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/306025/?series=60878&amp;rev=2
</content>
</entry>
<entry>
<title>drm/scheduler: Add flag to hint the release of guilty job.</title>
<updated>2019-05-02T20:50:55Z</updated>
<author>
<name>Andrey Grodzovsky</name>
</author>
<published>2019-04-18T15:00:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a5343b8a2ca5799ee6370e3cca77369a4c598221'/>
<id>urn:sha1:a5343b8a2ca5799ee6370e3cca77369a4c598221</id>
<content type='text'>
Problem:
Sched thread's cleanup function races against TO handler
and removes the guilty job from mirror list and we
have no way of differentiating if the job was removed from within the
TO handler or from the sched thread's clean-up function.

Fix:
Add a flag to scheduler to hint the TO handler that the guilty job needs
to be explicitly released.

v2: whitespace fix

Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/1555599624-12285-5-git-send-email-andrey.grodzovsky@amd.com
</content>
</entry>
<entry>
<title>drm/sched: Keep s_fence-&gt;parent pointer</title>
<updated>2019-05-02T20:46:52Z</updated>
<author>
<name>Andrey Grodzovsky</name>
</author>
<published>2019-04-18T15:00:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=290764af7e369f0001175dc8c3cb747aa9903bb8'/>
<id>urn:sha1:290764af7e369f0001175dc8c3cb747aa9903bb8</id>
<content type='text'>
For later driver's reference to see if the fence is signaled.

v2: Move parent fence put to resubmit jobs.

Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/1555599624-12285-4-git-send-email-andrey.grodzovsky@amd.com
</content>
</entry>
<entry>
<title>drm/scheduler: rework job destruction</title>
<updated>2019-05-02T20:45:48Z</updated>
<author>
<name>Christian König</name>
</author>
<published>2019-04-18T15:00:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5918045c4ed492fb5813f980dcf89a90fefd0a4e'/>
<id>urn:sha1:5918045c4ed492fb5813f980dcf89a90fefd0a4e</id>
<content type='text'>
We now destroy finished jobs from the worker thread to make sure that
we never destroy a job currently in timeout processing.
By this we avoid holding lock around ring mirror list in drm_sched_stop
which should solve a deadlock reported by a user.

v2: Remove unused variable.
v4: Move guilty job free into sched code.
v5:
Move sched-&gt;hw_rq_count to drm_sched_start to account for counter
decrement in drm_sched_stop even when we don't call resubmit jobs
if guily job did signal.
v6: remove unused variable

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109692

Acked-by: Chunming Zhou &lt;david1.zhou@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/1555599624-12285-3-git-send-email-andrey.grodzovsky@amd.com
</content>
</entry>
<entry>
<title>drm/sched: Fix description of drm_sched_stop</title>
<updated>2019-04-23T16:15:38Z</updated>
<author>
<name>Jonathan Neuschäfer</name>
</author>
<published>2019-04-20T12:50:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5d356328d676deca698d01324000e0d98fba643'/>
<id>urn:sha1:f5d356328d676deca698d01324000e0d98fba643</id>
<content type='text'>
Since commit 222b5f044159 ("drm/sched: Refactor ring mirror list
handling."), drm_sched_hw_job_reset is no longer there, so let's adjust
the doc comment accordingly.

Reviewed-by: Andrey Grodzovsky &lt;andrey.grodzovsky@amd.com&gt;
Signed-off-by: Jonathan Neuschäfer &lt;j.neuschaefer@gmx.net&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
</feed>
