From: Vitaly Prosyak
The current implementation of drm_sched_start uses a hardcoded -ECANCELED to
dispose of a job when
the parent/hw fence is NULL. This results in drm_sched_job_done being called
with -ECANCELED for
each job with a NULL parent in the pending list, making it difficult to
disti
On 2024-07-25 03:37, Christian König wrote:
> Am 24.07.24 um 20:43 schrieb vitaly.pros...@amd.com:
>> From: Vitaly Prosyak
>>
>> The current implementation of drm_sched_start uses a hardcoded -ECANCELED to
>> dispose of a job when
>> the parent/hw fence is NULL. This results in drm_sched_job_do
Am 24.07.24 um 20:43 schrieb vitaly.pros...@amd.com:
From: Vitaly Prosyak
The current implementation of drm_sched_start uses a hardcoded -ECANCELED to
dispose of a job when
the parent/hw fence is NULL. This results in drm_sched_job_done being called
with -ECANCELED for
each job with a NULL pa
On Wed, Jul 24, 2024 at 2:43 PM wrote:
>
> From: Vitaly Prosyak
>
> The current implementation of drm_sched_start uses a hardcoded -ECANCELED to
> dispose of a job when
> the parent/hw fence is NULL. This results in drm_sched_job_done being called
> with -ECANCELED for
> each job with a NULL pa
From: Vitaly Prosyak
The current implementation of drm_sched_start uses a hardcoded -ECANCELED to
dispose of a job when
the parent/hw fence is NULL. This results in drm_sched_job_done being called
with -ECANCELED for
each job with a NULL parent in the pending list, making it difficult to
disti