From: Steven Price <steven.price@arm.com>
To: "Boris Brezillon" <boris.brezillon@collabora.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: dri-devel@lists.freedesktop.org,
Florent Tomasin <florent.tomasin@arm.com>,
Heinrich Fink <hfink@snap.com>,
kernel@collabora.com
Subject: Re: [PATCH v1 7/8] drm/panthor: Make sure we resume the tick when new jobs are submitted
Date: Thu, 6 Nov 2025 16:39:13 +0000 [thread overview]
Message-ID: <730fe6c8-a651-4f1a-b8a4-0d17986687ff@arm.com> (raw)
In-Reply-To: <20251106144656.1012274-8-boris.brezillon@collabora.com>
On 06/11/2025 14:46, Boris Brezillon wrote:
> If the group is already assigned a slot but was idle before this job
> submission, we need to make sure the priority rotation happens in the
> future. Extract the existing logic living in group_schedule_locked()
> and call this new sched_resume_tick() helper from the "group is
> assigned a slot" path.
>
> Fixes: de8548813824 ("drm/panthor: Add the scheduler logical block")
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panthor/panthor_sched.c | 43 +++++++++++++++++++------
> 1 file changed, 34 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index 7b164228af7b..923816397751 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -2541,14 +2541,33 @@ static void sync_upd_work(struct work_struct *work)
> sched_queue_delayed_work(sched, tick, 0);
> }
>
> +static void sched_resume_tick(struct panthor_device *ptdev)
> +{
> + struct panthor_scheduler *sched = ptdev->scheduler;
> + u64 delay_jiffies, now;
> +
> + drm_WARN_ON(&ptdev->base, sched->resched_target != U64_MAX);
> +
> + /* Scheduler tick was off, recalculate the resched_target based on the
> + * last tick event, and queue the scheduler work.
> + */
> + now = get_jiffies_64();
> + sched->resched_target = sched->last_tick + sched->tick_period;
> + if (sched->used_csg_slot_count == sched->csg_slot_count &&
> + time_before64(now, sched->resched_target))
> + delay_jiffies = min_t(unsigned long, sched->resched_target - now, ULONG_MAX);
> + else
> + delay_jiffies = 0;
> +
> + sched_queue_delayed_work(sched, tick, delay_jiffies);
> +}
> +
> static void group_schedule_locked(struct panthor_group *group, u32 queue_mask)
> {
> struct panthor_device *ptdev = group->ptdev;
> struct panthor_scheduler *sched = ptdev->scheduler;
> struct list_head *queue = &sched->groups.runnable[group->priority];
> - u64 delay_jiffies = 0;
> bool was_idle;
> - u64 now;
>
> if (!group_can_run(group))
> return;
> @@ -2593,13 +2612,7 @@ static void group_schedule_locked(struct panthor_group *group, u32 queue_mask)
> /* Scheduler tick was off, recalculate the resched_target based on the
> * last tick event, and queue the scheduler work.
> */
> - now = get_jiffies_64();
> - sched->resched_target = sched->last_tick + sched->tick_period;
> - if (sched->used_csg_slot_count == sched->csg_slot_count &&
> - time_before64(now, sched->resched_target))
> - delay_jiffies = min_t(unsigned long, sched->resched_target - now, ULONG_MAX);
> -
> - sched_queue_delayed_work(sched, tick, delay_jiffies);
> + sched_resume_tick(ptdev);
> }
>
> static void queue_stop(struct panthor_queue *queue,
> @@ -3200,6 +3213,18 @@ queue_run_job(struct drm_sched_job *sched_job)
>
> group_schedule_locked(group, BIT(job->queue_idx));
> } else {
> + u32 queue_mask = BIT(job->queue_idx);
> + bool resume_tick = group_is_idle(group) &&
> + (group->idle_queues & queue_mask) &&
> + !(group->blocked_queues & queue_mask) &&
> + sched->resched_target == U64_MAX;
> +
> + /* We just added something to the queue, so it's no longer idle. */
> + group->idle_queues &= ~BIT(job->queue_idx);
> +
> + if (resume_tick)
> + sched_resume_tick(ptdev);
> +
> gpu_write(ptdev, CSF_DOORBELL(queue->doorbell_id), 1);
> if (!sched->pm.has_ref &&
> !(group->blocked_queues & BIT(job->queue_idx))) {
next prev parent reply other threads:[~2025-11-06 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 14:46 [PATCH v1 0/8] drm/panthor: Misc scheduler fixes Boris Brezillon
2025-11-06 14:46 ` [PATCH v1 1/8] drm/panthor: Simplify group idleness tracking Boris Brezillon
2025-11-06 16:15 ` Steven Price
2025-11-06 14:46 ` [PATCH v1 2/8] drm/panthor: Don't try to enable extract events Boris Brezillon
2025-11-06 16:17 ` Steven Price
2025-11-06 14:46 ` [PATCH v1 3/8] drm/panthor: Fix the group priority rotation logic Boris Brezillon
2025-11-06 16:18 ` Steven Price
2025-11-06 16:30 ` Boris Brezillon
2025-11-06 14:46 ` [PATCH v1 4/8] drm/panthor: Fix the full_tick check Boris Brezillon
2025-11-06 16:20 ` Steven Price
2025-11-06 14:46 ` [PATCH v1 5/8] drm/panthor: Fix immediate ticking on a disabled tick Boris Brezillon
2025-11-06 16:23 ` Steven Price
2025-11-06 16:33 ` Boris Brezillon
2025-11-06 14:46 ` [PATCH v1 6/8] drm/panthor: Fix the logic that decides when to stop ticking Boris Brezillon
2025-11-06 16:29 ` Steven Price
2025-11-06 14:46 ` [PATCH v1 7/8] drm/panthor: Make sure we resume the tick when new jobs are submitted Boris Brezillon
2025-11-06 16:39 ` Steven Price [this message]
2025-11-06 14:46 ` [PATCH v1 8/8] drm/panthor: Kill panthor_sched_immediate_tick() Boris Brezillon
2025-11-06 16:44 ` Steven Price
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=730fe6c8-a651-4f1a-b8a4-0d17986687ff@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=florent.tomasin@arm.com \
--cc=hfink@snap.com \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.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