From: Xin Wang <x.wang@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kamil.konieczny@intel.com, matthew.d.roper@intel.com,
shuicheng.lin@intel.com, brian3.nguyen@intel.com,
alex.zuo@intel.com, nakshtra.goyal@intel.com,
dnyaneshwar.bhadane@intel.com, gustavo.sousa@intel.com,
Xin Wang <x.wang@intel.com>
Subject: [PATCH v5 0/2] lib/intel_device_info: get the xe .graphics_rel from GMD_ID
Date: Tue, 14 Oct 2025 18:31:19 +0000 [thread overview]
Message-ID: <20251014183121.53185-1-x.wang@intel.com> (raw)
This series enables IGT to retrieve the accurate IP minor version
(graphics_rel) at runtime for xe platforms with GMD_ID support,
instead of relying on hardcoded values in the PCI device table.
Background:
-----------
Current IGT uses static PCI device tables with hardcoded graphics_rel
values. For Xe2 platforms, Different device instances may have
different graphics_rel (minor version) values
The kernel's GMD_ID ioctl provides accurate runtime IP version
information (ip_ver_major.ip_ver_minor) which should be used for
platform-specific workarounds and feature detection.
Solution:
---------
This series adds support to query xe device info at runtime:
Patch 1/2: Get runtime xe device graphics version from GMD_ID
- Populate graphics versions in xe_device from GMD_ID ioctl
- Cache device info by devid in global map for efficient lookup
- Provide xe_device_get_info() API for other components
Patch 2/2: Query runtime xe device graphics versions
- Use runtime xe device info for Gen20+ platforms
- Use weak symbol linkage to avoid breaking static library builds
- Remove hardcoded graphics_rel from static table for xe platforms
Benefits:
---------
- Accurate IP version for platform-specific workarounds
- Proper feature detection for hardware variants
- Unified device info API between i915 and xe drivers
- No changes needed to existing test code
V2:
- set the graphics version info in xe_device_get() don't copy
the whole struct of the intel_device_info
- update the graphics_rel when the info is already in the cache
Xin Wang (2):
lib/xe/xe_query: Get runtime xe device graphics version from GMD_ID
lib/intel_device_info: Query runtime xe device graphics versions
lib/intel_device_info.c | 27 ++++++++++++++++++++++++---
lib/xe/xe_query.c | 33 ++++++++++++++++++++++++++++++++-
lib/xe/xe_query.h | 4 ++++
3 files changed, 60 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2025-10-14 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 18:31 Xin Wang [this message]
2025-10-14 18:31 ` [PATCH v5 1/2] lib/xe/xe_query: Get runtime xe device graphics version from GMD_ID Xin Wang
2025-10-14 18:31 ` [PATCH v5 2/2] lib/intel_device_info: Query runtime xe device graphics versions Xin Wang
2025-10-14 23:43 ` ✓ Xe.CI.BAT: success for lib/intel_device_info: get the xe .graphics_rel from GMD_ID (rev5) Patchwork
2025-10-14 23:52 ` ✓ i915.CI.BAT: " Patchwork
2025-10-15 9:59 ` ✗ i915.CI.Full: failure " Patchwork
2025-10-15 11:47 ` ✓ Xe.CI.Full: success " 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=20251014183121.53185-1-x.wang@intel.com \
--to=x.wang@intel.com \
--cc=alex.zuo@intel.com \
--cc=brian3.nguyen@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nakshtra.goyal@intel.com \
--cc=shuicheng.lin@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