Eero Tamminen

> We have reproduced the issue and placed the bug in our debug queue, but do not have an ETA for a fix. @AdamCetnerowski Over a year has passed. Any...

Same issue also with the (last week) drm-tip 5.17-rc4 kernel, GuC 69.0.3 and latest compute-runtime "22.07.22465" release.

Still happens with the (last week) drm-tip 5.18-rc3 kernel, GuC 70.1.1 and latest compute-runtime "22.16.22992" release.

Still happens with drm-tip 5.18 kernel, GuC 70.1.1 and latest compute-runtime "22.23.23405" release.

Tested drm-tip 6.0-rc3 kernel, GuC 70.1.1, and compute-runtime " 22.31.23852", and memory reporting seems to be working now -> closing.

FYI: IGC build issue got resolved, but I think there's still value in separating compute and Sysman functionality as I do not think there's much overlap between them. Being able...

While snappy is one problem for performance, it's not the only one. I opened issues 145 and 146 for other things I noticed when investigating why retracing takes all CPU...

Are you interested in investigating underlying 3D driver or application/game performance? For driver performance investigation, apitrace's retracing CPU usage is less of an issue, as performance can be measured at...

For comparing performance of GL calls i.e. stuff below apitrace, trace file handling overhead shouldn't be important, I would think you to just need measurements for how much time the...

> While in master we end up serializing the user memory over and over and over again on every glDrawArrays call, because we don't know how big the arrays in...