All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Kalkhof" <nkalkhof@web.de>
To: Daniel Vetter <daniel@ffwll.ch>
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:22:00 +0100 (CET)	[thread overview]
Message-ID: <802616320.177645.1320855720270.JavaMail.fmail@mwmweb017> (raw)

Daniel,

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?

Nic

-----Ursprüngliche Nachricht-----
Von: "Daniel Vetter" <daniel@ffwll.ch>
Gesendet: Nov 7, 2011 7:36:28 PM
An: "Nicolas Kalkhof" <nkalkhof@web.de>
Betreff: Re: [Intel-gfx] [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock

>On Mon, Nov 07, 2011 at 07:14:35PM +0100, Nicolas Kalkhof wrote:
>> ok here is the sysprof result (see below). No cpu/gpu intensive apps are
>> running, just the idling desktop. CPU Temperature is low and frequency
>> is throttled down to 800 MHz like it should be. The System is responsive
>> and behaves normal but top shows full cpu load. Honestly I cannot see
>> the reason why X and gkrellm should eat up all the gpu since they
>> clearly don't hog the cpu. Maybe the kernel reports wrong cpu stats?
>> Then again the load goes down when I kill X! Hope this gives you a clue.
>
>On a quick look it seems that at least X is busy-spinning in the select
>loop and gkrellm seems to be eqally busy doing not much. Have you tried
>what happens when you kill gkrellm?
>
>Otherwise I think it's time for a bit of bisecting.
>-Daniel
>--
>Daniel Vetter
>Mail: daniel@ffwll.ch
>Mobile: +41 (0)79 365 57 48


___________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2011-11-09 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 16:22 Nicolas Kalkhof [this message]
2011-11-09 16:28 ` [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock Daniel Vetter
  -- 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=802616320.177645.1320855720270.JavaMail.fmail@mwmweb017 \
    --to=nkalkhof@web.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@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.