From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75719] mplayer -vo gl consume more CPU on r200
Date: Tue, 04 Mar 2014 13:06:32 +0000 [thread overview]
Message-ID: <bug-75719-502-6VMCCZ9sqi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75719-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75719
--- Comment #8 from Thomas Hellström <thellstrom@vmware.com> ---
There's really nothing in this commit that should affect anything but metadata,
and if anything, CPU usage should've decreased.
So if CPU usage is drastically increased by this commit (or rather this merge),
IMHO that points to a bug somewhere else, but triggered by this merge; possibly
in radeon / TTM caching setup or in the x86 PAT memory region tracking code.
In any case, I'm on out-of-office this week and can't look at this before next
week, but meantime it would be helpful if you could perform a couple of
additional checks:
1) Try to find out which of the commits in the merge that causes this. If that
turns out to be hard, could you change all occurencies of VM_PFNMAP in
ttm_bo_mmap() (ttm_bo_vm.c) to VM_MIXEDMAP and check if that fixes the problem
you are seeing?
2) If you're familiar with oprofile, it would be very helpful to see a profile
of a "good" and a "bad" run, including kernel symbols.
Thanks,
/Thomas
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-03-04 13:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 15:09 [Bug 75719] New: mplayer -vo gl consume more CPU on r200 bugzilla-daemon
2014-03-03 17:17 ` [Bug 75719] " bugzilla-daemon
2014-03-03 17:18 ` bugzilla-daemon
2014-03-03 17:19 ` bugzilla-daemon
2014-03-03 17:22 ` bugzilla-daemon
2014-03-03 18:04 ` bugzilla-daemon
2014-03-03 18:06 ` bugzilla-daemon
2014-03-03 18:08 ` bugzilla-daemon
2014-03-04 13:06 ` bugzilla-daemon [this message]
2014-03-04 14:37 ` bugzilla-daemon
2014-03-04 15:47 ` bugzilla-daemon
2014-03-04 17:37 ` bugzilla-daemon
2014-03-05 18:49 ` bugzilla-daemon
2014-03-05 18:50 ` bugzilla-daemon
2014-03-06 4:40 ` bugzilla-daemon
2014-03-10 9:41 ` bugzilla-daemon
2019-11-19 8:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-75719-502-6VMCCZ9sqi@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox