From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Philipp Stanner" <phasta@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Matthew Brost" <matthew.brost@intel.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
"Philipp Stanner" <pstanner@redhat.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2] drm/sched: Extend and update documentation
Date: Fri, 19 Sep 2025 06:23:08 +0700 [thread overview]
Message-ID: <aMyUXCF-Jlu3wAjt@archie.me> (raw)
In-Reply-To: <20250902111209.64082-2-phasta@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-09-18 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 11:12 [PATCH v2] drm/sched: Extend and update documentation Philipp Stanner
2025-09-18 12:56 ` Philipp Stanner
2025-09-18 23:23 ` Bagas Sanjaya [this message]
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=aMyUXCF-Jlu3wAjt@archie.me \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=phasta@kernel.org \
--cc=pstanner@redhat.com \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).