Skip to content

[Unitrace] Use L0 core extension to query PCI properties #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ph0b
Copy link

@ph0b ph0b commented Jun 20, 2025

Unitrace uses sysman in legacy mode (zeInit + ZES_ENABLE_SYSMAN), however this is not supported for Xe2 and newer platforms: https://github.com/intel/compute-runtime/blob/releases/25.22/programmers-guide/SYSMAN.md#support-and-limitations hence leading to an abort on Xe2 and newer devices when calling unitrace --device-list.

./src/levelzero/ze_metrics.h:66: void PrintDeviceList(): Assertion status == ZE_RESULT_SUCCESS' failed.

Since Level-Zero 1.3.0 specification, you can use zeDevicePciGetPropertiesExt instead of sysman.
As sysman is only used to query PCI information, you can remove its use and switch to the core extension instead.

Since Level-Zero 1.3.0 specification, we can use
zeDevicePciGetPropertiesExt instead of sysman.

Unitrace used sysman in legacy mode (zeInit + ZES_ENABLE_SYSMAN),
however this was not supported for Xe2 and newer platforms:
https://github.com/intel/compute-runtime/blob/releases/25.22/programmers-guide/SYSMAN.md#support-and-limitations
hence leading to an abort from ./src/levelzero/ze_metrics.h:66: `void
PrintDeviceList(): Assertion `status == ZE_RESULT_SUCCESS' failed.` on
Xe2 and newer devices when calling `unitrace --device-list`.

As sysman was only used to query PCI information, we could remove its
use and switch to the core extension instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant