From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, helen.fornazier@gmail.com,
airlied@gmail.com, simona.vetter@ffwll.ch, robdclark@gmail.com,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, jani.nikula@linux.intel.com,
dmitry.baryshkov@linaro.org, mripard@kernel.org,
boqun.feng@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] drm/ci: enable lockdep detection
Date: Tue, 11 Feb 2025 20:58:03 +0530 [thread overview]
Message-ID: <20250211152812.54018-1-vignesh.raman@collabora.com> (raw)
This patch series enables lockdep detection in drm-ci. Any lockdep
failures will be shown as warnings in the pipeline. This series
also enables CONFIG_DEBUG_WW_MUTEX_SLOWPATH for mutex slowpath
debugging and refactors software-driver stage jobs.
Test run with this series,
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1362134
Link to v1:
https://lore.kernel.org/all/20240812112030.81774-1-vignesh.raman@collabora.com/
Vignesh Raman (3):
drm/ci: refactor software-driver stage jobs
drm/ci: enable CONFIG_DEBUG_WW_MUTEX_SLOWPATH
drm/ci: enable lockdep detection
Documentation/gpu/automated_testing.rst | 4 ++
drivers/gpu/drm/ci/build.yml | 6 +-
drivers/gpu/drm/ci/igt_runner.sh | 11 ++++
drivers/gpu/drm/ci/test.yml | 78 +++++++++++++------------
4 files changed, 58 insertions(+), 41 deletions(-)
--
2.43.0
next reply other threads:[~2025-02-11 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:28 Vignesh Raman [this message]
2025-02-11 15:28 ` [PATCH v2 1/3] drm/ci: refactor software-driver stage jobs Vignesh Raman
2025-02-11 15:28 ` [PATCH v2 2/3] drm/ci: enable CONFIG_DEBUG_WW_MUTEX_SLOWPATH Vignesh Raman
2025-02-11 15:28 ` [PATCH v2 3/3] drm/ci: enable lockdep detection Vignesh Raman
2025-02-13 12:43 ` Helen Mae Koike Fornazier
2025-02-14 7:52 ` Vignesh Raman
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=20250211152812.54018-1-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=valentine.burley@collabora.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
all inboxes | Powered by JetHome®