On Tue, Sep 02, 2025 at 01:12:10PM +0200, Philipp Stanner wrote:
> + * The GPU scheduler is shared infrastructure intended to help drivers 
> managing
                          a shared infrastructure

> + * command submission to their hardware.
> <snipped>...
> + * Job initialization is split into two stages:
> + *   1. drm_sched_job_init() which serves for basic preparation of a job.
> + *      Drivers don't have to be mindful of this function's consequences and
> + *      its effects can be reverted through drm_sched_job_cleanup().

           ".. this function's side effects and these can be .."

> + *   2. drm_sched_job_arm() which irrevokably arms a job for execution. This

                                     irrevocably

> + *      initializes the job's fences and the job has to be submitted with
> + *      drm_sched_entity_push_job(). Once drm_sched_job_arm() has been 
> called,
> + *      the job structure has to be valid until the scheduler invoked
> + *      drm_sched_backend_ops.free_job().
> + *

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Attachment: signature.asc
Description: PGP signature

Reply via email to