https://bugs.kde.org/show_bug.cgi?id=480885
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |UPSTREAM
Status|REPORTED |RESOLVED
--- Comment #37 from Zamundaaa <xaver.h...@gmail.com> ---
Okay, that worked.
About 5% of the CPU usage is in drmModeAddFB2WithModifiers, which is not great,
but more importantly 77% is in a drmIoctl in the framebuffer destructor, which
will be either
https://invent.kde.org/plasma/kwin/-/blob/bbfffec6d6efcb6ab81fc57a08430892b0b50e52/src/backends/drm/drm_buffer.cpp#L69
or
https://invent.kde.org/plasma/kwin/-/blob/bbfffec6d6efcb6ab81fc57a08430892b0b50e52/src/backends/drm/drm_buffer.cpp#L70
They get called when apps update the cursor image or their window, which causes
KWin to update the cursor or screen with a different buffer, which explains why
you see different behavior with different apps.
I don't know what the kernel driver is doing in the drm ioctl - hotspot just
shows ??? - but it's supposed to be pretty much free, so this is almost
certainly a driver bug. Please report it at
https://forums.developer.nvidia.com/c/gpu-graphics/linux/148
--
You are receiving this mail because:
You are watching all bug changes.
