Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>,
	Gustavo Sousa <gustavo.sousa@intel.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: [PATCH v4 i-g-t 0/3] Add post-kmod-unbind igt_hook
Date: Wed, 23 Jul 2025 12:44:03 +0200	[thread overview]
Message-ID: <20250723104406.58784-1-peter.senna@linux.intel.com> (raw)

Introduces a new IGT hook: IGT_HOOK_POST_KMOD_UNBIND
(post-kmod-unbind), designed to facilitate kmemleak scans in our CI
workflows.

As suggested by Lucas de Marchi, a useful strategy for detecting memory
leaks is to run kmemleak scans both before binding and after unbinding
the kernel module. This patch adds support for the latter scenario,
enabling automated scans immediately after the module is unbound.

Example test-list:
 igt@xe_module_load@load
 igt@core_hotunplug@unbind-rebind
 igt@xe_module_load@unload

Example usage:
 IGT_PING_HOSTNAME='10.211.176.1'
 IGT_TEST_ROOT='/home/gta/UPSTREAM/igt-gpu-tools/build/tests/'
 ./build/runner/igt_runner -o -l verbose -s --per-test-timeout 120 \
   --overall-timeout 960 --piglit-style-dmesg --dmesg-warn-level=4 \
   --use-watchdog --inactivity-timeout 90 \
   --abort-on-monitored-error=ping,taint --disk-usage-limit=10M \
   --facts --hook 'post-kmod-unbind:OUTF=/tmp/kmemleak-post-unbind && \
                   echo $IGT_HOOK_TEST_FULLNAME $IGT_HOOK_TEST $IGT_HOOK_SUBTEST >> $OUTF && \
                   echo scan > /sys/kernel/debug/kmemleak && \
                   cat /sys/kernel/debug/kmemleak >> $OUTF' \
   --test-list ~/igt/test-list \
   /home/gta/igt/0

Known Limitations: In certain cases, such as when running
igt@core_hotunplug@unbind-rebind, the unbind operation is explicitly
managed by the igt if the module is already loaded. However, if the
unbind occurs outside of igt, the hook will not be triggered and
the scan will not run.

v4:
 - Updated hook unit testing to account for new env var
 - Updated cover letter

v3:
 - Wrote Gustavo's name and email address correctly (:facepalm:)
 - Renamed the hook to IGT_HOOK_POST_KMOD_UNBIND as the unbind can also happen
   for snd modules
 - Changed the logic for the IGT_HOOK_KMOD_UNBIND_MODULE_NAME env var so that
   it is only populated when the correct hook is used.

v2:
 - change function name to igt_core_get_igt_hook()
 - Add env var IGT_HOOK_KMOD_UNBIND_MODULE_NAME
 - Fix minor issues

Cc: Gustavo Sousa <gustavo.sousa@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>

Peter Senna Tschudin (3):
  lib/igt_core: Expose igt_hook pointer for other libs
  lib/igt_kmod: Add IGT_HOOK_POST_KMOD_UNBIND
  lib/tests: Update hook unit testing

 lib/igt_core.c                   | 12 ++++++++++++
 lib/igt_core.h                   |  2 ++
 lib/igt_hook.c                   | 11 +++++++++++
 lib/igt_hook.h                   |  3 +++
 lib/igt_kmod.c                   |  8 ++++++++
 lib/tests/igt_hook.c             |  1 +
 lib/tests/igt_hook_integration.c |  9 +++++----
 7 files changed, 42 insertions(+), 4 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-07-23 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 10:44 Peter Senna Tschudin [this message]
2025-07-23 10:44 ` [PATCH v4 i-g-t 1/3] lib/igt_core: Expose igt_hook pointer for other libs Peter Senna Tschudin
2025-07-23 10:44 ` [PATCH v4 i-g-t 2/3] lib/igt_kmod: Add IGT_HOOK_POST_KMOD_UNBIND Peter Senna Tschudin
2025-07-23 17:01   ` Kamil Konieczny
2025-07-25 10:13     ` Peter Senna Tschudin
2025-07-23 10:44 ` [PATCH v4 i-g-t 3/3] lib/tests: Update hook unit testing Peter Senna Tschudin
2025-07-23 16:58   ` Kamil Konieczny
2025-07-23 16:27 ` ✓ i915.CI.BAT: success for Add post-kmod-unbind igt_hook (rev2) Patchwork
2025-07-23 16:41 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-07-25 10:15   ` Peter Senna Tschudin
2025-07-23 22:07 ` ✗ Xe.CI.Full: " Patchwork
2025-07-25 10:15   ` Peter Senna Tschudin
2025-07-24  6:53 ` ✓ i915.CI.Full: success " Patchwork

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=20250723104406.58784-1-peter.senna@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.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