All of 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>,
	kamil.konieczny@linux.intel.com, rodrigo.vivi@intel.com,
	katarzyna.piecielska@intel.com
Subject: [PATCH v2 i-g-t 0/1] tests/intel/intel_kernelfs: Unify sysfs and debugfs testing
Date: Sat, 22 Mar 2025 14:03:15 +0100	[thread overview]
Message-ID: <20250322130316.272087-1-peter.senna@linux.intel.com> (raw)
In-Reply-To: <20250318213755.366638-1-peter.senna@linux.intel.com>

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_kernelfs, 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.

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: kamil.konieczny@linux.intel.com
Cc: rodrigo.vivi@intel.com
Cc: katarzyna.piecielska@intel.com

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

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

-- 
2.34.1


  parent reply	other threads:[~2025-03-22 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 21:37 [PATCH i-g-t] tests/intel/intel_kernelfs: Unified testing for sysfs and debugfs Peter Senna Tschudin
2025-03-18 22:25 ` ✓ i915.CI.BAT: success for " Patchwork
2025-03-18 22:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-18 23:55 ` ✗ i915.CI.Full: " Patchwork
2025-03-22 13:03 ` Peter Senna Tschudin [this message]
2025-03-22 13:03   ` [PATCH v2 i-g-t 1/1] tests/intel/intel_kernelfs: Unify sysfs and debugfs testing Peter Senna Tschudin
2025-03-27 22:22     ` Rodrigo Vivi
2025-03-28  8:28       ` Peter Senna Tschudin
2025-03-22 13:33 ` ✓ Xe.CI.BAT: success for tests/intel/intel_kernelfs: Unified testing for sysfs and debugfs (rev2) Patchwork
2025-03-22 14:25 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-22 16:24 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-22 18:46 ` ✗ i915.CI.Full: failure " 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=20250322130316.272087-1-peter.senna@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=katarzyna.piecielska@intel.com \
    --cc=rodrigo.vivi@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 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.