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: Mon, 7 Nov 2011 18:31:49 +0100 (CET) [thread overview]
Message-ID: <1833111785.1286053.1320687109926.JavaMail.fmail@mwmweb020> (raw)
Hi Daniel,
Thanks for your Advice. Since it might take some time for the issue to appear I'll try to use a profiler to speed up the bughunt. I don't have any experience in profiling the kernel so this might take some time.... :(
I'll keep you posted.
Yours
Nic
-----Ursprüngliche Nachricht-----
Von: "Daniel Vetter" <daniel@ffwll.ch>
Gesendet: Nov 7, 2011 5:56:38 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 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
___________________________________________________________
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
next reply other threads:[~2011-11-07 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:31 Nicolas Kalkhof [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2011-11-07 18:14 Nicolas Kalkhof
2011-11-07 18:36 ` Daniel Vetter
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=1833111785.1286053.1320687109926.JavaMail.fmail@mwmweb020 \
--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.