[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z8hVlc0AgQkNqSGL@archie.me>
Date: Wed, 5 Mar 2025 20:45:57 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Philipp Stanner <phasta@...nel.org>,
Matthew Brost <matthew.brost@...el.com>,
Danilo Krummrich <dakr@...nel.org>,
Christian König <ckoenig.leichtzumerken@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Sumit Semwal <sumit.semwal@...aro.org>
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 1/3] drm/sched: Adjust outdated docu for run_job()
On Wed, Mar 05, 2025 at 02:05:50PM +0100, Philipp Stanner wrote:
> /**
> - * @run_job: Called to execute the job once all of the dependencies
> - * have been resolved. This may be called multiple times, if
> - * timedout_job() has happened and drm_sched_job_recovery()
> - * decides to try it again.
> + * @run_job: Called to execute the job once all of the dependencies
> + * have been resolved.
> + *
> + * @sched_job: the job to run
> + *
> + * The deprecated drm_sched_resubmit_jobs() (called by &struct
> + * drm_sched_backend_ops.timedout_job) can invoke this again with the
> + * same parameters. Using this is discouraged because it violates
> + * dma_fence rules, notably dma_fence_init() has to be called on
> + * already initialized fences for a second time. Moreover, this is
> + * dangerous because attempts to allocate memory might deadlock with
> + * memory management code waiting for the reset to complete.
> + *
> + * TODO: Document what drivers should do / use instead.
No replacement? Or bespoke/roll-your-own functionality as a must?
Confused...
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists