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: sai.gowtham.ch@intel.com
Subject: [igt-dev] [PATCH i-g-t] tests/xe/xe_query.c: Update subtest query-engines
Date: Fri, 28 Apr 2023 17:14:45 +0530	[thread overview]
Message-ID: <20230428114445.3244549-1-janga.rahul.kumar@intel.com> (raw)

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

Log engine instance and tile info along with engine type.

Reviewed-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
---
 tests/xe/xe_query.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/xe/xe_query.c b/tests/xe/xe_query.c
index 3f038225..94eb046c 100644
--- a/tests/xe/xe_query.c
+++ b/tests/xe/xe_query.c
@@ -183,8 +183,9 @@ test_query_engines(int fd)
 
 	xe_for_each_hw_engine(fd, hwe) {
 		igt_assert(hwe);
-		igt_info("engine %d: %s\n", i++,
-			xe_engine_class_string(hwe->engine_class));
+		igt_info("engine %d: %s, engine instance: %d, tile: TILE-%d\n", i++,
+			 xe_engine_class_string(hwe->engine_class), hwe->engine_instance,
+								    hwe->gt_id);
 	}
 
 	igt_assert(i > 0);
-- 
2.25.1

             reply	other threads:[~2023-04-28 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 11:44 janga.rahul.kumar [this message]
2023-04-28 15:20 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/xe/xe_query.c: Update subtest query-engines (rev2) Patchwork
2023-04-28 23:12 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-04-25 12:36 [igt-dev] [PATCH i-g-t] tests/xe/xe_query.c: Update subtest query-engines janga.rahul.kumar
2023-04-27 11:58 ` Kumar, Janga Rahul
2023-04-27 12:20   ` Ch, Sai Gowtham
2023-04-28 11:47     ` Kumar, Janga Rahul

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=20230428114445.3244549-1-janga.rahul.kumar@intel.com \
    --to=janga.rahul.kumar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ramadevi.gandi@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