From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 63192] New: [nouveau]
drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when
using weston drm-compositor
Date: Sat, 06 Apr 2013 00:14:24 +0000
Message-ID:
Priority
medium
Bug ID
63192
Assignee
dri-devel@lists.freedesktop.org
Summary
[nouveau] drmModeSetCursor->nouveau_bo_rd32->ioread32 provides high cpu load when using weston drm-compositor
Severity
normal
Classification
Unclassified
OS
Linux (All)
Reporter
vova7890@mail.ru
Hardware
x86-64 (AMD64)
Status
NEW
Version
DRI CVS
Component
DRM/other
Product
DRI
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