From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org
Subject: [igt-dev] [CI 4/9] lib/igt_drm_fdinfo: Copy over region map name on match
Date: Mon, 6 Nov 2023 12:35:13 +0000 [thread overview]
Message-ID: <20231106123518.588528-4-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20231106123518.588528-1-tvrtko.ursulin@linux.intel.com>
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
I will need some record of which regions were found for intel_gpu_top so
lets just copy over the region name from the map on the first match.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
lib/igt_drm_fdinfo.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/igt_drm_fdinfo.c b/lib/igt_drm_fdinfo.c
index b72822894782..222ccbfb1fd6 100644
--- a/lib/igt_drm_fdinfo.c
+++ b/lib/igt_drm_fdinfo.c
@@ -148,6 +148,10 @@ static int parse_region(char *line, struct drm_client_fdinfo *info,
for (i = 0; i < region_entries; i++) {
if (!strncmp(name, region_map[i], name_len)) {
found = i;
+ if (!info->region_names[info->num_regions][0]) {
+ assert(name_len < sizeof(info->region_names[i]));
+ strncpy(info->region_names[i], name, name_len);
+ }
break;
}
}
--
2.39.2
next prev parent reply other threads:[~2023-11-06 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 12:35 [igt-dev] [CI 1/9] tests/i915/drm_fdinfo: Check engine info is supported Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 2/9] tests/i915/drm_fdinfo: Stress test context close versus fdinfo reads Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 3/9] tests/i915/drm_fdinfo: Add some memory info tests Tvrtko Ursulin
2023-11-06 12:35 ` Tvrtko Ursulin [this message]
2023-11-06 12:35 ` [igt-dev] [CI 5/9] lib/igt_drm_clients: Fix client id type confusion Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 6/9] lib/igt_drm_clients: Allow passing in the memory region map Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 7/9] tools/intel_gpu_top: Fully wrap clients operations Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 8/9] tools/intel_gpu_top: Add per client memory info Tvrtko Ursulin
2023-11-06 12:35 ` [igt-dev] [CI 9/9] tools/intel_gpu_top: Add ability to show memory region breakdown Tvrtko Ursulin
2023-11-06 14:38 ` [igt-dev] ✗ CI.xeBAT: failure for series starting with [CI,1/9] tests/i915/drm_fdinfo: Check engine info is supported Patchwork
2023-11-06 14:53 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-11-06 20:33 ` [igt-dev] ✗ Fi.CI.IGT: 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=20231106123518.588528-4-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
/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