From: John.C.Harrison@Intel.com
To: IGT-Dev@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH i-g-t 2/2] tests/intel/*_query: Add support for new hwconfig table entry
Date: Thu, 1 Aug 2024 12:51:29 -0700 [thread overview]
Message-ID: <20240801195129.3667206-3-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20240801195129.3667206-1-John.C.Harrison@Intel.com>
From: John Harrison <John.C.Harrison@Intel.com>
A new enum value has been added to the hardware config table. So
update the tests accordingly.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
---
lib/intel_hwconfig_types.h | 1 +
tests/intel/i915_query.c | 1 +
tests/intel/xe_query.c | 3 ++-
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/intel_hwconfig_types.h b/lib/intel_hwconfig_types.h
index d5db217afba2..0e6ce5b17084 100644
--- a/lib/intel_hwconfig_types.h
+++ b/lib/intel_hwconfig_types.h
@@ -96,6 +96,7 @@ enum intel_hwconfig {
INTEL_HWCONFIG_MAX_TASK_URB_ENTRIES, /* 78 */
INTEL_HWCONFIG_MIN_MESH_URB_ENTRIES, /* 79 */
INTEL_HWCONFIG_MAX_MESH_URB_ENTRIES, /* 80 */
+ INTEL_HWCONFIG_MAX_GSC, /* 81 */
__INTEL_HWCONFIG_KEY_LIMIT
};
diff --git a/tests/intel/i915_query.c b/tests/intel/i915_query.c
index 4d706d62b286..54dbb193a50e 100644
--- a/tests/intel/i915_query.c
+++ b/tests/intel/i915_query.c
@@ -1339,6 +1339,7 @@ static const char * const hwconfig_keys[] = {
[INTEL_HWCONFIG_MAX_TASK_URB_ENTRIES] = "Max Task URB Entries",
[INTEL_HWCONFIG_MIN_MESH_URB_ENTRIES] = "Min Mesh URB Entries",
[INTEL_HWCONFIG_MAX_MESH_URB_ENTRIES] = "Max Mesh URB Entries",
+ [INTEL_HWCONFIG_MAX_GSC] = "MaxGSC",
};
static const char * const hwconfig_memtypes[] = {
diff --git a/tests/intel/xe_query.c b/tests/intel/xe_query.c
index 6ebf5e4b6d71..ddb2e76e5dd6 100644
--- a/tests/intel/xe_query.c
+++ b/tests/intel/xe_query.c
@@ -50,7 +50,7 @@ void dump_hex_debug(void *buffer, int len)
/* Please reflect intel_hwconfig_types.h changes below
* static_asserti_value + get_hwconfig_name
* Thanks :-) */
-static_assert(INTEL_HWCONFIG_MAX_MESH_URB_ENTRIES+1 == __INTEL_HWCONFIG_KEY_LIMIT, "");
+static_assert(INTEL_HWCONFIG_MAX_GSC + 1 == __INTEL_HWCONFIG_KEY_LIMIT, "");
#define CASE_STRINGIFY(A) case INTEL_HWCONFIG_##A: return #A;
const char* get_hwconfig_name(int param)
@@ -136,6 +136,7 @@ const char* get_hwconfig_name(int param)
CASE_STRINGIFY(MAX_TASK_URB_ENTRIES);
CASE_STRINGIFY(MIN_MESH_URB_ENTRIES);
CASE_STRINGIFY(MAX_MESH_URB_ENTRIES);
+ CASE_STRINGIFY(MAX_GSC);
}
igt_assert_lt(param, __INTEL_HWCONFIG_KEY_LIMIT);
igt_assert(!"Missing config table enum");
--
2.45.2
next prev parent reply other threads:[~2024-08-01 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 19:51 [PATCH i-g-t 0/2] Update hwconfig table tests John.C.Harrison
2024-08-01 19:51 ` [PATCH i-g-t 1/2] tests/intel/xe_query: Fail on unknown hwconfig entries John.C.Harrison
2024-08-02 23:12 ` Dixit, Ashutosh
2024-08-01 19:51 ` John.C.Harrison [this message]
2024-08-02 23:14 ` [PATCH i-g-t 2/2] tests/intel/*_query: Add support for new hwconfig table entry Dixit, Ashutosh
2024-08-01 20:26 ` ✓ CI.xeBAT: success for Update hwconfig table tests Patchwork
2024-08-01 20:50 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-05 11:24 ` Kamil Konieczny
2024-08-01 22:32 ` ✗ CI.xeFULL: " Patchwork
2024-08-05 11:33 ` Kamil Konieczny
2024-08-06 20:28 ` [PATCH i-g-t 0/2] " Dixit, Ashutosh
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=20240801195129.3667206-3-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--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