From: Philipp Stanner <pstanner@redhat.com>
To: "Philipp Stanner" <phasta@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"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>,
"Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v2 0/3] drm/sched: Documentation and refcount improvements
Date: Wed, 22 Jan 2025 09:23:23 +0100 [thread overview]
Message-ID: <9329836ce71a24360abc568498dc7e4ea059cd87.camel@redhat.com> (raw)
In-Reply-To: <20250121151544.44949-2-phasta@kernel.org>
On Tue, 2025-01-21 at 16:15 +0100, Philipp Stanner wrote:
> 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)
s/CPU/GPU
obviously.
P.
> - 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: Document run_job() refcount hazard
> drm/sched: Adjust outdated docu for run_job()
> drm/sched: Update timedout_job()'s documentation
>
> drivers/gpu/drm/scheduler/sched_main.c | 5 +-
> include/drm/gpu_scheduler.h | 106 ++++++++++++++++-------
> --
> 2 files changed, 71 insertions(+), 40 deletions(-)
>
prev parent reply other threads:[~2025-01-22 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 15:15 [PATCH v2 0/3] drm/sched: Documentation and refcount improvements Philipp Stanner
2025-01-21 15:15 ` [PATCH v2 1/3] drm/sched: Document run_job() refcount hazard Philipp Stanner
2025-01-21 15:15 ` [PATCH v2 2/3] drm/sched: Adjust outdated docu for run_job() Philipp Stanner
2025-01-21 15:15 ` [PATCH v2 3/3] drm/sched: Update timedout_job()'s documentation Philipp Stanner
2025-01-24 12:27 ` Danilo Krummrich
2025-01-27 12:32 ` Philipp Stanner
2025-01-27 12:59 ` Danilo Krummrich
2025-01-22 8:23 ` Philipp Stanner [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=9329836ce71a24360abc568498dc7e4ea059cd87.camel@redhat.com \
--to=pstanner@redhat.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.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=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