Bug 63192 - [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor
Summary: [nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load ...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-06 00:14 UTC by Vova
Modified: 2015-10-22 05:10 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Vova 2013-04-06 00:14:24 UTC 
Weston runned in drm-mode provide very high cpu load on mouse moving. I don`t think that the bug of weston, seems problem in nouveau drm. At launch weston have a log:

...
[24465.734894] nouveau W[   PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004
[24465.748153] nouveau W[   PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004
[24521.950788] nouveau W[   PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004
[24521.955032] nouveau W[   PFIFO][0000:02:00.0] INTR 0x00000001: 0x00000004
...


ioread32_native(ioread32 on litle-endian) using 100% of cpu core. If in weston comment out drmModeSetCursor - cpu load is normal, but no see cursor ofcourse. They copying cursor(64x64) from bo-object. Seems TTM iomem access provide very high cpu load... On radeon it works smoothly and no have very high cpu load.


Kernel 3.9-rc5 (x86_64)
Wayland/Weston: git
Mesa: git
libdrm: git
Comment 1 Pierre Moreau 2014-12-09 18:39:12 UTC 
Moving to Nouveau.

Are you still experiencing this issue with an updated graphic stack, aka. kernel 3.18, mesa 10.4, libdrm 2.4.58 and waylaid/weston 1.6?
(The bug went unnoticed as it wasn't linked to Nouveau.)
Comment 2 Ilia Mirkin 2015-10-22 05:10:00 UTC 
No response to retest request in a year. Marking invalid.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.