Eero Tamminen

> Also is that benchmark good reference or is there better way to check if this regression is real? Unfortunately I have no idea. (While I work for Intel and...

Other metrics have not regressed, only engine ones. Engine metrics fail also with latest [zello_sysman](https://github.com/intel/compute-runtime/blob/master/level_zero/tools/test/black_box_tests/zello_sysman.cpp), or one built from the same `compute-runtime` version: ``` # zello_sysman -e ... Device Name...

No idea whether `zello_sysman` being initialized with `zeInit` or `zesInit` (using `ZELLO_SYSMAN_USE_ZESINIT=1` env var) affects this, as it segfaults with latter when querying engine metrics (both with `i915` & `xe`...

Segfault when zesInit() is used, is specific `zello_sysman`. In my own program there's no segfault, engine metrics just do not work.

Noticed (by accident) that engine metrics work (now) if process has `SYS_ADMIN` capability, `PERFMON` capability is not enough for that any more. PERFMON capability: ``` # docker run -it --net...

As far as I can see from the latest `i915` KMD code, `SYS_ADMIN` capability is needed only for (early Gens) SECURE_BATCHES. For perf API usage, `PERFMON` capability should still be...

> @eero-t Checking this @joshuaranjan Any results?

> We will look into this issue , ideally it shouldn't segfault @saik-intel / @JablonskiMateusz (nearly) 4 months gone, any news?

> ldconfig doesn't help. This is new in 24.13.29138.7. Was fine in the previous release. Does `ldconfig -v` list the library? And if not, is that path in your ldconfig...

Related: https://github.com/intel/compute-runtime/issues/529