Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: janga.rahul.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com,
	janga.rahul.kumar@intel.com
Cc: matthew.d.roper@intel.com
Subject: [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry
Date: Thu, 21 Mar 2024 20:46:36 +0530	[thread overview]
Message-ID: <20240321151637.3320911-2-janga.rahul.kumar@intel.com> (raw)
In-Reply-To: <20240321151637.3320911-1-janga.rahul.kumar@intel.com>

From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>

Read and dump mocs debugfs entry.

Cc: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
---
 tests/intel/xe_debugfs.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/intel/xe_debugfs.c b/tests/intel/xe_debugfs.c
index c5a586e9b..ba12f6ccc 100644
--- a/tests/intel/xe_debugfs.c
+++ b/tests/intel/xe_debugfs.c
@@ -158,6 +158,7 @@ test_gt(int fd, int gt_id)
 		"topology",
 		"sa_info",
 		"hw_engines",
+		"mocs",
 //		"force_reset"
 	};
 	static const char * const expected_files_uc[] = {
@@ -183,6 +184,10 @@ test_gt(int fd, int gt_id)
 	igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
 	igt_debugfs_dump(fd, name);
 
+	sprintf(name, "gt%d/mocs", gt_id);
+	igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
+	igt_debugfs_dump(fd, name);
+
 	sprintf(name, "gt%d/uc/guc_info", gt_id);
 	igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
 	igt_debugfs_dump(fd, name);
-- 
2.25.1


  reply	other threads:[~2024-03-21 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 15:16 [PATCH i-g-t 0/2] Add mocs tests janga.rahul.kumar
2024-03-21 15:16 ` janga.rahul.kumar [this message]
2024-03-22 21:18   ` [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry Matt Roper
2024-04-24 20:19     ` Kumar, Janga Rahul
2024-03-21 15:16 ` [PATCH i-g-t 2/2] tests/intel/xe_pm: Add mocs suspend resume test janga.rahul.kumar
2024-03-22 21:25   ` Matt Roper
2024-04-24 20:21     ` Kumar, Janga Rahul
2024-03-21 17:12 ` ✓ Fi.CI.BAT: success for Add mocs tests Patchwork
2024-03-21 17:22 ` ✗ CI.xeBAT: failure " Patchwork
2024-03-22  8:42 ` ✗ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-04-24 20:08 [PATCH i-g-t v2 0/2] " janga.rahul.kumar
2024-04-24 20:08 ` [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry janga.rahul.kumar
2024-05-02  9:16   ` Nilawar, Badal

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=20240321151637.3320911-2-janga.rahul.kumar@intel.com \
    --to=janga.rahul.kumar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=ramadevi.gandi@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