From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t 0/2] Fix perf_pmu@unload
Date: Tue, 22 Oct 2024 22:05:00 -0700 [thread overview]
Message-ID: <20241023050502.3049664-1-lucas.demarchi@intel.com> (raw)
This is now passing for me on DG2 since it now uses the unbind + unload
logic. Besides, this should not explode in the kernel anymore when used
together with the patch mentioned below.
I have other changes on top to make the unbind+unload logic for all i915
tests (just like it is for xe), but I don't want possible noises in the
tests, so I will leave these for later.
Test-with: 20241023042909.3038309-2-lucas.demarchi@intel.com
Lucas De Marchi (2):
lib/igt_kmod: Export igt_kmod_unbind()
tests/intel/perf_pmu: Migrate to unbind + unload
lib/igt_kmod.c | 6 +++---
lib/igt_kmod.h | 2 ++
tests/intel/perf_pmu.c | 22 ++++++++++++----------
3 files changed, 17 insertions(+), 13 deletions(-)
--
2.47.0
next reply other threads:[~2024-10-23 5:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 5:05 Lucas De Marchi [this message]
2024-10-23 5:05 ` [PATCH i-g-t 1/2] lib/igt_kmod: Export igt_kmod_unbind() Lucas De Marchi
2024-10-30 0:08 ` Umesh Nerlige Ramappa
2024-10-30 14:11 ` Lucas De Marchi
2024-11-04 19:24 ` Umesh Nerlige Ramappa
2024-11-04 20:51 ` Lucas De Marchi
2024-10-23 5:05 ` [PATCH i-g-t 2/2] tests/intel/perf_pmu: Migrate to unbind + unload Lucas De Marchi
2024-11-04 19:25 ` Umesh Nerlige Ramappa
2024-11-04 20:49 ` Lucas De Marchi
2024-11-04 22:03 ` Umesh Nerlige Ramappa
2024-10-23 6:16 ` ✓ Fi.CI.BAT: success for Fix perf_pmu@unload Patchwork
2024-10-23 6:17 ` ✓ CI.xeBAT: " Patchwork
2024-10-23 9:10 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-23 10:09 ` ✗ CI.xeFULL: " 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=20241023050502.3049664-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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