Re: [PATCH] drm/i915: protect force_wake_(get|put) with the gt_lock

[Daniel Vetter <daniel@ffwll.ch>]

On Mon, Nov 07, 2011 at 05:39:44PM +0100, Nicolas Kalkhof wrote:
> Hi Daniel,
> 
> confirmed. Linus's linux-next.git shows the same behaviour. Until now
> I've used a patched 3.1-rc-6+ Kernel from Dave Airlie's branch
> (git://people.freedesktop.org/~airlied/linux' from Oct 26th.).
> dmesg/syslog shows nothing special, neither does i915_error_state.
> 
> Any advice?

If the behaviour-difference is clear, you could try to bisect this. The
alternative is to use your favourite system profiler and see where the
cycles get wasted (either sysprof or perf). I suggest you'll try whatever
approach your more familiar with first and then switch over to the other
if the first one doesn't yield any clear results. If the difference is
really clear, I'd start with the bisect (aside: don't restrict the bisect
to any subdir, the change causing the regression could equally likely be
somewhere in the core kernel).

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