public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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: Mon, 7 Nov 2011 17:05:12 +0100	[thread overview]
Message-ID: <20111107160512.GB4015@phenom.ffwll.local> (raw)
In-Reply-To: <1478842321.1719911.1320673926178.JavaMail.fmail@mwmweb010>

On Mon, Nov 07, 2011 at 02:52:06PM +0100, Nicolas Kalkhof wrote:
> Hi Daniel,
> 
> thanks for the git branch. Strange thing is with the patched kernel the
> cpu load goes up after working with my desktop with no obvious reason.
> top shows a high user and system load but no process using up all the
> cpu cores. The cpufreq-daemon clocks the cpu cores down to the minimal
> frequency (800mhz) when idle while top still shows full cpu load but no
> process using up the cpu. The cpu load drops to normal after I kill X
> and immediately goes up again if I restart X.
> 
> I'm kinda lost here :( Any Ideas?

Step one is to check whether -linus master has the same issues. My branch
is based upon

commit 37be944a0270402f9cda291a930b0286f6dc92f5
Merge: ca836a2 1717c0e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Oct 28 05:54:23 2011 -0700

    Merge branch 'drm-core-next' of
    git://people.freedesktop.org/~airlied/linux'
 
If that doesn't show the same issue, can you please run a bisect (only 13
commits) to find out which patch introduced this?

Thanks, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2011-11-07 16:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 13:52 [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock Nicolas Kalkhof
2011-11-07 16:05 ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-09 16:22 Nicolas Kalkhof
2011-11-09 16:28 ` Daniel Vetter
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-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=20111107160512.GB4015@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