Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: [igt-dev] [PATCH i-g-t 1/9] tests/i915/drm_fdinfo: Check engine info is supported
Date: Thu, 12 Oct 2023 09:15:39 +0100	[thread overview]
Message-ID: <20231012081547.852052-2-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20231012081547.852052-1-tvrtko.ursulin@linux.intel.com>

From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

On top of checking that parsing works, check that there are some engines
present. This will be needed once the memory stats are added and so return
value from __igt_parse_drm_fdinfo() will then be possible to be greater
than zero even when engine stats are not supported.

Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
 tests/intel/drm_fdinfo.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/intel/drm_fdinfo.c b/tests/intel/drm_fdinfo.c
index aca19db50680..344c44dce78b 100644
--- a/tests/intel/drm_fdinfo.c
+++ b/tests/intel/drm_fdinfo.c
@@ -737,6 +737,7 @@ igt_main
 
 		igt_require_gem(i915);
 		igt_require(igt_parse_drm_fdinfo(i915, &info, NULL, 0, NULL, 0));
+		igt_require(info.num_engines);
 
 		ctx = intel_ctx_create_all_physical(i915);
 
-- 
2.39.2

  reply	other threads:[~2023-10-12  8:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  8:15 [igt-dev] [PATCH i-g-t 0/9] Client memory fdinfo test and intel_gpu_top support Tvrtko Ursulin
2023-10-12  8:15 ` Tvrtko Ursulin [this message]
2023-11-03 18:21   ` [igt-dev] [Intel-gfx] [PATCH i-g-t 1/9] tests/i915/drm_fdinfo: Check engine info is supported Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 2/9] tests/i915/drm_fdinfo: Stress test context close versus fdinfo reads Tvrtko Ursulin
2023-11-03 18:32   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-11-06 12:38     ` Tvrtko Ursulin
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 3/9] tests/i915/drm_fdinfo: Add some memory info tests Tvrtko Ursulin
2023-11-03 19:05   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 4/9] lib/igt_drm_fdinfo: Copy over region map name on match Tvrtko Ursulin
2023-11-03 18:56   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 5/9] lib/igt_drm_clients: Fix client id type confusion Tvrtko Ursulin
2023-11-03 18:54   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 6/9] lib/igt_drm_clients: Allow passing in the memory region map Tvrtko Ursulin
2023-11-03 18:47   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 7/9] tools/intel_gpu_top: Fully wrap clients operations Tvrtko Ursulin
2023-11-03 18:57   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 8/9] tools/intel_gpu_top: Add per client memory info Tvrtko Ursulin
2023-11-03 19:01   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 9/9] tools/intel_gpu_top: Add ability to show memory region breakdown Tvrtko Ursulin
2023-11-03 19:04   ` Kamil Konieczny
2023-10-12 15:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Client memory fdinfo test and intel_gpu_top support (rev2) Patchwork
2023-10-12 15:29 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-13 13:18 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-06 12:41   ` Kamil Konieczny
2023-11-07 12:59     ` Illipilli, TejasreeX
2023-11-07 12:28 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-11-07 12:36 ` 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=20231012081547.852052-2-tvrtko.ursulin@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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