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>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Melissa Wen" <mwen@igalia.com>,
"Steven Price" <steven.price@arm.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] drm/sched: Add bloody spinlocks
Date: Thu, 30 Oct 2025 11:42:18 +0100 [thread overview]
Message-ID: <20251030104219.181704-2-phasta@kernel.org> (raw)
The scheduler wouldn't be the scheduler if there weren't functions like
drm_sched_job_arm() being called probably a few thousand times per
second without taking proper locks, just racing wildly.
This series adds the proper locks to drm_sched_job_init() and
drm_sched_job_arm().
Philipp Stanner (2):
drm/sched: Use proper locks in drm_sched_job_arm()
drm/sched: Use proper locks for drm_sched_job_init()
drivers/gpu/drm/scheduler/sched_main.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
--
2.49.0
next reply other threads:[~2025-10-30 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:42 Philipp Stanner [this message]
2025-10-30 10:42 ` [PATCH 1/2] drm/sched: Use proper locks in drm_sched_job_arm() Philipp Stanner
2025-10-30 10:42 ` [PATCH 2/2] drm/sched: Use proper locks for drm_sched_job_init() 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=20251030104219.181704-2-phasta@kernel.org \
--to=phasta@kernel.org \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.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=mwen@igalia.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.