All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
	Adam Miszczak <adam.miszczak@linux.intel.com>,
	Jakub Kolakowski <jakub1.kolakowski@intel.com>,
	Lukasz Laguna <lukasz.laguna@intel.com>,
	Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Subject: [PATCH i-g-t] tests/intel/xe_sriov_flr: Handle missing provisioning data per-GT
Date: Fri, 22 Aug 2025 11:39:08 +0200	[thread overview]
Message-ID: <20250822093908.414306-1-marcin.bernatowicz@linux.intel.com> (raw)

When reading provisioned LMEM ranges from debugfs, some GTs may not
expose provisioning data at all. Previously, this caused the test to
skip entirely with a "Failed read" reason.

Relax the check to treat -ENOENT as a valid case and simply continue
to the next GT. This ensures the test is not skipped unnecessarily
when provisioning data is absent on some GTs.

Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
---
 tests/intel/xe_sriov_flr.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/intel/xe_sriov_flr.c b/tests/intel/xe_sriov_flr.c
index fc08703c0..9eebe5f71 100644
--- a/tests/intel/xe_sriov_flr.c
+++ b/tests/intel/xe_sriov_flr.c
@@ -816,7 +816,9 @@ static int populate_vf_lmem_sizes(struct subcheck_data *data)
 		ret = xe_sriov_pf_debugfs_read_provisioned_ranges(data->pf_fd,
 								  XE_SRIOV_SHARED_RES_LMEM,
 								  gt, &ranges, &nr_ranges);
-		if (ret) {
+		if (ret == -ENOENT) {
+			continue;
+		} else if (ret) {
 			set_skip_reason(data, "Failed read %s on gt%u (%d)\n",
 					xe_sriov_debugfs_provisioned_attr_name(XE_SRIOV_SHARED_RES_LMEM),
 					gt, ret);
-- 
2.31.1


             reply	other threads:[~2025-08-22  9:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22  9:39 Marcin Bernatowicz [this message]
2025-08-22  9:47 ` [PATCH i-g-t] tests/intel/xe_sriov_flr: Handle missing provisioning data per-GT K V P, Satyanarayana
2025-08-22 10:21   ` Bernatowicz, Marcin
2025-08-22 12:48     ` K V P, Satyanarayana
2025-08-22 13:00       ` Michal Wajdeczko
2025-08-25  7:11         ` Bernatowicz, Marcin
2025-08-22 10:36 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-08-22 10:38 ` ✓ i915.CI.BAT: success " Patchwork
2025-08-22 11:55 ` ✗ i915.CI.Full: failure " Patchwork
2025-08-23  2:51 ` ✗ Xe.CI.Full: " 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=20250822093908.414306-1-marcin.bernatowicz@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=satyanarayana.k.v.p@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.