From: "Maíra Canal" <mcanal@igalia.com>
To: phasta@kernel.org, "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Xinhui Pan" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Frank Binns" <frank.binns@imgtec.com>,
"Matt Coster" <matt.coster@imgtec.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Qiang Yu" <yuq825@gmail.com>, "Rob Clark" <robdclark@gmail.com>,
"Sean Paul" <sean@poorly.run>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Karol Herbst" <kherbst@redhat.com>,
"Lyude Paul" <lyude@redhat.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Melissa Wen" <mwen@igalia.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Sunil Khatri" <sunil.khatri@amd.com>,
"Lijo Lazar" <lijo.lazar@amd.com>,
"Hawking Zhang" <Hawking.Zhang@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Ma Jun" <Jun.Ma2@amd.com>, "Yunxiang Li" <Yunxiang.Li@amd.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, etnaviv@lists.freedesktop.org,
lima@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, nouveau@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/sched: Use struct for drm_sched_init() params
Date: Wed, 29 Jan 2025 11:53:47 -0300 [thread overview]
Message-ID: <d3ab5057-22fe-43d5-baea-4dec091fb303@igalia.com> (raw)
In-Reply-To: <c5c3791df54b7ae4ba1a31159a4beda0b44d00cf.camel@mailbox.org>
Hi Philipp,
On 29/01/25 09:39, Philipp Stanner wrote:
> On Wed, 2025-01-29 at 07:53 -0300, Maíra Canal wrote:
>> Hi Philipp,
>>
>> On 28/01/25 11:29, Philipp Stanner wrote:
>>> drm_sched_init() has a great many parameters and upcoming new
>>> functionality for the scheduler might add even more. Generally, the
>>> great number of parameters reduces readability and has already
>>> caused
>>> one missnaming in:
>>>
>>> commit 6f1cacf4eba7 ("drm/nouveau: Improve variable name in
>>> nouveau_sched_init()").
>>>
>>> Introduce a new struct for the scheduler init parameters and port
>>> all
>>> users.
>>>
>>> Signed-off-by: Philipp Stanner <phasta@kernel.org>
>>> ---
>>> Changes in v2:
>>> - Point out that the hang-limit is deprecated. (Christian)
>>> - Initialize the structs to 0 at declaration. (Planet Earth)
>>> - Don't set stuff explicitly to 0 / NULL. (Tvrtko)
>>> - Make the structs const where possible. (Boris)
>>> - v3d: Use just 1, universal, function for sched-init. (Maíra)
>>> ---
>>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 18 ++++--
>>> drivers/gpu/drm/etnaviv/etnaviv_sched.c | 20 +++----
>>> drivers/gpu/drm/imagination/pvr_queue.c | 18 ++++--
>>> drivers/gpu/drm/lima/lima_sched.c | 16 +++--
>>> drivers/gpu/drm/msm/msm_ringbuffer.c | 17 +++---
>>> drivers/gpu/drm/nouveau/nouveau_sched.c | 15 +++--
>>> drivers/gpu/drm/panfrost/panfrost_job.c | 20 ++++---
>>> drivers/gpu/drm/panthor/panthor_mmu.c | 16 +++--
>>> drivers/gpu/drm/panthor/panthor_sched.c | 29 +++++----
>>> drivers/gpu/drm/scheduler/sched_main.c | 50 ++++++----------
>>> drivers/gpu/drm/v3d/v3d_sched.c | 68 +++++++++--------
>>> -----
>>> drivers/gpu/drm/xe/xe_execlist.c | 16 +++--
>>> drivers/gpu/drm/xe/xe_gpu_scheduler.c | 17 +++++-
>>> include/drm/gpu_scheduler.h | 37 ++++++++++--
>>> 14 files changed, 206 insertions(+), 151 deletions(-)
>>>
>>
>> [...]
>>
>>> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c
>>> b/drivers/gpu/drm/panthor/panthor_sched.c
>>> index 5844a7f639e0..44713cfdcd74 100644
>>> --- a/drivers/gpu/drm/panthor/panthor_sched.c
>>> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
>>> @@ -3284,6 +3284,22 @@ static struct panthor_queue *
>>> group_create_queue(struct panthor_group *group,
>>> const struct drm_panthor_queue_create *args)
>>> {
>>> + const struct drm_sched_init_args sched_args = {
>>> + .ops = &panthor_queue_sched_ops,
>>> + .submit_wq = group->ptdev->scheduler->wq,
>>> + .num_rqs = 1,
>>> + /*
>>> + * The credit limit argument tells us the total
>>> number of
>>> + * instructions across all CS slots in the
>>> ringbuffer, with
>>> + * some jobs requiring twice as many as others,
>>> depending on
>>> + * their profiling status.
>>> + */
>>> + .credit_limit = args->ringbuf_size / sizeof(u64),
>>> + .timeout = msecs_to_jiffies(JOB_TIMEOUT_MS),
>>> + .timeout_wq = group->ptdev->reset.wq,
>>> + .name = "panthor-queue",
>>> + .dev = group->ptdev->base.dev
>>> + };
>>> struct drm_gpu_scheduler *drm_sched;
>>> struct panthor_queue *queue;
>>> int ret;
>>> @@ -3354,17 +3370,8 @@ group_create_queue(struct panthor_group
>>> *group,
>>> if (ret)
>>> goto err_free_queue;
>>>
>>> - /*
>>> - * Credit limit argument tells us the total number of
>>> instructions
>>> - * across all CS slots in the ringbuffer, with some jobs
>>> requiring
>>> - * twice as many as others, depending on their profiling
>>> status.
>>> - */
>>> - ret = drm_sched_init(&queue->scheduler,
>>> &panthor_queue_sched_ops,
>>> - group->ptdev->scheduler->wq, 1,
>>> - args->ringbuf_size / sizeof(u64),
>>> - 0, msecs_to_jiffies(JOB_TIMEOUT_MS),
>>> - group->ptdev->reset.wq,
>>> - NULL, "panthor-queue", group->ptdev-
>>>> base.dev);
>>> +
>>
>> Please don't use multiple blank lines.
>>
>>> + ret = drm_sched_init(&queue->scheduler, &sched_args);
>>> if (ret)
>>> goto err_free_queue;
>>>
>>> diff --git a/drivers/gpu/drm/scheduler/sched_main.c
>>> b/drivers/gpu/drm/scheduler/sched_main.c
>>> index a48be16ab84f..6295b2654a7c 100644
>>> --- a/drivers/gpu/drm/scheduler/sched_main.c
>>> +++ b/drivers/gpu/drm/scheduler/sched_main.c
>>> @@ -1244,40 +1244,24 @@ static void drm_sched_run_job_work(struct
>>> work_struct *w)
>>> * drm_sched_init - Init a gpu scheduler instance
>>> *
>>> * @sched: scheduler instance
>>> - * @ops: backend operations for this scheduler
>>> - * @submit_wq: workqueue to use for submission. If NULL, an
>>> ordered wq is
>>> - * allocated and used
>>> - * @num_rqs: number of runqueues, one for each priority, up to
>>> DRM_SCHED_PRIORITY_COUNT
>>> - * @credit_limit: the number of credits this scheduler can hold
>>> from all jobs
>>> - * @hang_limit: number of times to allow a job to hang before
>>> dropping it
>>> - * @timeout: timeout value in jiffies for the scheduler
>>> - * @timeout_wq: workqueue to use for timeout work. If NULL, the
>>> system_wq is
>>> - * used
>>> - * @score: optional score atomic shared with other schedulers
>>> - * @name: name used for debugging
>>> - * @dev: target &struct device
>>> + * @args: scheduler initialization arguments
>>> *
>>> * Return 0 on success, otherwise error code.
>>> */
>>> -int drm_sched_init(struct drm_gpu_scheduler *sched,
>>> - const struct drm_sched_backend_ops *ops,
>>> - struct workqueue_struct *submit_wq,
>>> - u32 num_rqs, u32 credit_limit, unsigned int
>>> hang_limit,
>>> - long timeout, struct workqueue_struct
>>> *timeout_wq,
>>> - atomic_t *score, const char *name, struct
>>> device *dev)
>>> +int drm_sched_init(struct drm_gpu_scheduler *sched, const struct
>>> drm_sched_init_args *args)
>>> {
>>> int i;
>>>
>>> - sched->ops = ops;
>>> - sched->credit_limit = credit_limit;
>>> - sched->name = name;
>>> - sched->timeout = timeout;
>>> - sched->timeout_wq = timeout_wq ? : system_wq;
>>> - sched->hang_limit = hang_limit;
>>> - sched->score = score ? score : &sched->_score;
>>> - sched->dev = dev;
>>> + sched->ops = args->ops;
>>> + sched->credit_limit = args->credit_limit;
>>> + sched->name = args->name;
>>> + sched->timeout = args->timeout;
>>> + sched->timeout_wq = args->timeout_wq ? : system_wq;
>>> + sched->hang_limit = args->hang_limit;
>>> + sched->score = args->score ? args->score : &sched->_score;
>>
>> Could we keep it consistent and use the Elvis Operator here as well?
>> Just like `sched->timeout_wq`.
>
> This is literally just the old code.
>
> And if at all, this insanely stupid GCC extension should not be used.
> It's one of the typical compiler people rampages that make the C
> language so terrible.
Not a problem to me, we can remove the Elvis Operator from `sched-
>timeout_wq`. My idea is just to do things consistently in variable
assignment.
Best Regards,
- Maíra
prev parent reply other threads:[~2025-01-29 14:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 14:29 [PATCH v2] drm/sched: Use struct for drm_sched_init() params Philipp Stanner
2025-01-28 14:56 ` Danilo Krummrich
2025-01-29 15:18 ` Philipp Stanner
2025-01-29 16:50 ` Danilo Krummrich
2025-01-28 15:29 ` ✓ CI.Patch_applied: success for drm/sched: Use struct for drm_sched_init() params (rev2) Patchwork
2025-01-28 15:29 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-28 15:31 ` ✓ CI.KUnit: success " Patchwork
2025-01-28 15:47 ` ✓ CI.Build: " Patchwork
2025-01-28 15:49 ` ✗ CI.Hooks: failure " Patchwork
2025-01-28 15:50 ` ✓ CI.checksparse: success " Patchwork
2025-01-28 16:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-28 16:17 ` [PATCH v2] drm/sched: Use struct for drm_sched_init() params Liviu Dudau
2025-01-28 21:49 ` Christian Gmeiner
2025-01-29 7:56 ` Boris Brezillon
2025-01-29 7:58 ` Christian Gmeiner
2025-01-29 3:32 ` Matthew Brost
2025-01-29 3:47 ` ✗ Xe.CI.Full: failure for drm/sched: Use struct for drm_sched_init() params (rev2) Patchwork
2025-01-29 7:59 ` [PATCH v2] drm/sched: Use struct for drm_sched_init() params Boris Brezillon
2025-01-29 8:09 ` Christian Gmeiner
2025-01-29 8:54 ` Frank Binns
2025-01-29 10:53 ` Maíra Canal
2025-01-29 12:39 ` Philipp Stanner
2025-01-29 14:53 ` Maíra Canal [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=d3ab5057-22fe-43d5-baea-4dec091fb303@igalia.com \
--to=mcanal@igalia.com \
--cc=Hawking.Zhang@amd.com \
--cc=Jun.Ma2@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=Yunxiang.Li@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=boris.brezillon@collabora.com \
--cc=christian.gmeiner@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=konradybcio@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=lijo.lazar@amd.com \
--cc=lima@lists.freedesktop.org \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lucas.demarchi@intel.com \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mario.limonciello@amd.com \
--cc=matt.coster@imgtec.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=nouveau@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=sunil.khatri@amd.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=yuq825@gmail.com \
/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