From: Philipp Stanner <phasta@kernel.org>
To: "Matthew Brost" <matthew.brost@intel.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Philipp Stanner" <phasta@kernel.org>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/3] drm/sched: Documentation and refcount improvements
Date: Wed, 5 Mar 2025 14:05:49 +0100 [thread overview]
Message-ID: <20250305130551.136682-2-phasta@kernel.org> (raw)
Changes in v7:
- Add Christian's info about violated dma_fence rules. (Christian)
- Fix some typos
Changes in v6:
- Switch patches 1 and 2. (Maira)
- Move section related to run_job() out of timedout_job() patch.
(Maira).
- Fix some places for correct crosslink references.
- Add comment to inform about run_job() incrementing the refcount.
(Danilo)
Changes in v5:
- Fix broken enumarated list in timedout_job's docu.
- Add TODO for documenting the dma_fence rules in timedout_job one
day.
Changes in v4:
- Remove mention of vague "dma_fence rules" in timedout_job() again
since I couldn't get input on what those rules precisely are.
- Address a forgotten TODO. (Me)
- Reposition "Return:" statements to make them congruent with the
official kernel style. (Tvrtko)
- Change formatting a bit because of crazy make htmldocs errors. (Me)
Changes in v3:
- timedout_job(): various docu wording improvements. (Danilo)
- Use the term "ring" consistently. (Danilo)
- Add fully fledged docu for enum drm_gpu_sched_stat. (Danilo)
Changes in v2:
- Document what run_job() is allowed to return. (Tvrtko)
- Delete confusing comment about putting the fence. (Danilo)
- Apply Danilo's RB to patch 1.
- Delete info about job recovery for entities in patch 3. (Danilo, me)
- Set the term "ring" as fix term for both HW rings and FW rings. A
ring shall always be the thingy on the CPU ;) (Danilo)
- Many (all) other comments improvements in patch 3. (Danilo)
This is as series succeeding my previous patch [1].
I recognized that we are still referring to a non-existing function and
a deprecated one in the callback docu. We should probably also point out
the important distinction between hardware and firmware schedulers more
cleanly.
Please give me feedback, especially on the RFC comments in patch3.
(This series still fires docu-build-warnings. I want to gather feedback
on the opion questions first and will solve them in v2.)
Thank you,
Philipp
[1] https://lore.kernel.org/all/20241220124515.93169-2-phasta@kernel.org/
Philipp Stanner (3):
drm/sched: Adjust outdated docu for run_job()
drm/sched: Document run_job() refcount hazard
drm/sched: Update timedout_job()'s documentation
drivers/gpu/drm/scheduler/sched_main.c | 9 +-
include/drm/gpu_scheduler.h | 112 +++++++++++++++++--------
2 files changed, 83 insertions(+), 38 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-05 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:05 Philipp Stanner [this message]
2025-03-05 13:05 ` [PATCH v7 1/3] drm/sched: Adjust outdated docu for run_job() Philipp Stanner
2025-03-05 13:45 ` Bagas Sanjaya
2025-03-05 14:24 ` Philipp Stanner
2025-03-07 18:09 ` Maíra Canal
2025-03-07 18:17 ` Philipp Stanner
2025-03-05 13:05 ` [PATCH v7 2/3] drm/sched: Document run_job() refcount hazard Philipp Stanner
2025-03-05 13:05 ` [PATCH v7 3/3] drm/sched: Update timedout_job()'s documentation Philipp Stanner
2025-03-06 20:57 ` Matthew Brost
2025-03-07 9:37 ` Philipp Stanner
2025-03-07 17:07 ` Matthew Brost
2025-03-07 17:35 ` Matthew Brost
2025-03-06 14:28 ` [PATCH v7 0/3] drm/sched: Documentation and refcount improvements Danilo Krummrich
2025-03-06 15:44 ` Philipp Stanner
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=20250305130551.136682-2-phasta@kernel.org \
--to=phasta@kernel.org \
--cc=airlied@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--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