From: Phillip Susi <psusi@cfl.rr.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 29842] Radeon runs very hot
Date: Fri, 25 Feb 2011 12:11:26 -0500 [thread overview]
Message-ID: <4D67E2BE.1060007@cfl.rr.com> (raw)
In-Reply-To: <201102251454.p1PEs2sZ024354@demeter1.kernel.org>
So I have been looking over the source code in drivers/gpu/drm/radeon.
I see various functions to start/stop/resume/initialize "mc" and "cp".
I assume those stand for microcode and control program? What exactly is
the difference?
It seems like the GPU is executing a few different microcode kernels
that process commands placed into ring buffers. When the ring buffers
are empty and the gui is idle, it seems like the GPU is still busily
executing an infinite loop checking for work in the ring buffers.
Shouldn't the driver detect the idle condition and issue an
r600_cp_stop() to halt execution and stop wasting power?
next prev parent reply other threads:[~2011-02-25 17:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 19:24 [Bug 29842] New: Radeon runs very hot bugzilla-daemon
2011-02-25 14:54 ` [Bug 29842] " bugzilla-daemon
2011-02-25 17:11 ` Phillip Susi [this message]
2011-02-25 17:35 ` Matt Turner
2011-02-26 8:09 ` Michel Dänzer
2011-02-26 15:40 ` Phillip Susi
2011-02-26 17:35 ` Alex Deucher
2011-03-01 0:40 ` bugzilla-daemon
2011-03-01 3:19 ` bugzilla-daemon
2011-03-01 3:43 ` bugzilla-daemon
2011-03-01 3:49 ` bugzilla-daemon
2011-03-01 19:58 ` bugzilla-daemon
2011-03-01 21:06 ` bugzilla-daemon
2011-03-01 21:09 ` bugzilla-daemon
2011-04-12 1:22 ` bugzilla-daemon
2011-04-12 2:26 ` bugzilla-daemon
2011-04-12 16:35 ` bugzilla-daemon
2011-06-27 12:44 ` bugzilla-daemon
2011-06-27 19:12 ` bugzilla-daemon
2011-07-02 11:57 ` bugzilla-daemon
2012-02-22 16:56 ` bugzilla-daemon
2012-02-23 6:45 ` Pasi Kärkkäinen
2012-03-19 10:50 ` bugzilla-daemon
2012-03-19 14:01 ` bugzilla-daemon
2012-03-19 16:35 ` bugzilla-daemon
2012-05-12 15:13 ` bugzilla-daemon
2015-02-19 16:19 ` 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=4D67E2BE.1060007@cfl.rr.com \
--to=psusi@cfl.rr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.