From: Daniel Vetter <daniel@ffwll.ch>
To: Nicolas Kalkhof <nkalkhof@web.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock
Date: Wed, 9 Nov 2011 17:28:27 +0100 [thread overview]
Message-ID: <20111109162827.GA4246@phenom.ffwll.local> (raw)
In-Reply-To: <802616320.177645.1320855720270.JavaMail.fmail@mwmweb017>
On Wed, Nov 09, 2011 at 05:22:00PM +0100, Nicolas Kalkhof wrote:
> Bisecting the kernel proved a little time consuming ;) however with the
> very latest linux.git anf xf86-video-intel the cpu load doesn't seem to
> go up accodring to top. What I can see is that the SNB draws approx
> 10-15 watts more when my system is completely idle. My first thought was
> that rc6 is being disabled but i915_enable_rc6 reports 1. Is there a way
> I can monitor the gpu frequency or its current power state?
cat /sys/kernel/debug/dri/0/i915_cur_delayinfo
atm you can't monitor the rc6 state, our current monitoring code doesn't
work on snb :(
Yours, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-11-09 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 16:22 [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock Nicolas Kalkhof
2011-11-09 16:28 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 18:14 Nicolas Kalkhof
2011-11-07 18:36 ` Daniel Vetter
2011-11-07 17:31 Nicolas Kalkhof
2011-11-07 16:39 Nicolas Kalkhof
2011-11-07 16:56 ` Daniel Vetter
2011-11-07 13:52 Nicolas Kalkhof
2011-11-07 16:05 ` Daniel Vetter
2011-11-06 17:42 Nicolas Kalkhof
2011-11-06 17:46 ` Daniel Vetter
2011-11-06 10:46 [PATCH 1/2] drm/i915: properly lock gt_fifo_count Daniel Vetter
2011-11-06 11:31 ` [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock Daniel Vetter
2011-11-06 11:57 ` Chris Wilson
2011-11-06 12:35 ` Daniel Vetter
2011-11-06 21:01 ` Chris Wilson
2011-11-06 22:06 ` Daniel Vetter
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=20111109162827.GA4246@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nkalkhof@web.de \
/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