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>,
	himanshu.girotra@intel.com, aditya.chauhan@intel.com,
	pravalika.gurram@intel.com, sai.gowtham.ch@intel.com,
	ramadevi.gandi@intel.com, lucas.demarchi@intel.com,
	rodrigo.vivi@intel.com, kamil.konieczny@linux.intel.com,
	katarzyna.piecielska@intel.com
Subject: [PATCH v3 i-g-t 0/1] tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing
Date: Fri, 28 Mar 2025 11:19:29 +0100	[thread overview]
Message-ID: <20250328101930.231985-1-peter.senna@linux.intel.com> (raw)

The existing debugfs_test scans and reads relevant sysfs and debugfs
files, but it is limited to i915. Meanwhile, xe_debugfs.c provides
similar functionality for Xe but has two key gaps:
 - It lacks sysfs file testing.
 - It does not attempt to read all debugfs files.

This patch introduces intel_sysfs_debugfs, unifying both tests into a single
framework that ensures comprehensive coverage for both i915 and Xe.

Follow-up improvements

Once this patch is merged, I will submit a follow-up to:
 - Remove the redundant hwmon-basic test from debugfs_test, as
   intel_hwmon already provides full coverage for i915 and Xe.
 - Remove both debugfs_test and xe_debugfs.

The removal of existing tests impacts external test lists, requiring
updates that take time. By first addressing the test gap, we ensure
complete coverage while minimizing disruption. The follow-up series will
then focus on cleanup for improving long-term maintainability.

v3:
 - rename test to intel_sysfs_debugfs
 - fix copy paste error on commit message
 - expand Cc list

v2:
 - renamed xe-specific functions with the xe_ prefix
 - created two igt_subtest_groups: one for i915 and another for Xe
 - prefixed each test with either i915 or xe

Cc: himanshu.girotra@intel.com
Cc: aditya.chauhan@intel.com
Cc: pravalika.gurram@intel.com
Cc: sai.gowtham.ch@intel.com
Cc: ramadevi.gandi@intel.com
Cc: lucas.demarchi@intel.com
Cc: rodrigo.vivi@intel.com
Cc: kamil.konieczny@linux.intel.com
Cc: katarzyna.piecielska@intel.com

Peter Senna Tschudin (1):
  tests/intel/intel_sysfs_debugfs Unify sysfs and debugfs testing

 tests/intel/intel_sysfs_debugfs.c | 500 ++++++++++++++++++++++++++++++
 tests/meson.build                 |   1 +
 2 files changed, 501 insertions(+)
 create mode 100644 tests/intel/intel_sysfs_debugfs.c

-- 
2.34.1


             reply	other threads:[~2025-03-28 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 10:19 Peter Senna Tschudin [this message]
2025-03-28 10:19 ` [PATCH v3 i-g-t 1/1] tests/intel/intel_sysfs_debugfs Unify sysfs and debugfs testing Peter Senna Tschudin
2025-03-28 15:37   ` Rodrigo Vivi
2025-03-28 22:22 ` ✓ Xe.CI.BAT: success for tests/intel/intel_sysfs_debugfs: " Patchwork
2025-03-28 22:42 ` ✓ i915.CI.BAT: " Patchwork
2025-03-29  3:10 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-29 13:37 ` ✗ Xe.CI.Full: " Patchwork
2025-04-06 19:06 ` 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=20250328101930.231985-1-peter.senna@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=aditya.chauhan@intel.com \
    --cc=himanshu.girotra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=katarzyna.piecielska@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=pravalika.gurram@intel.com \
    --cc=ramadevi.gandi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sai.gowtham.ch@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