From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Paolo Ornati <ornati@gmail.com>,
Simon Farnsworth <simon.farnsworth@onelan.co.uk>,
intel-gfx@lists.freedesktop.org,
Sitsofe Wheeler <sitsofe@yahoo.com>,
Venkatesh Pallipadi <venki@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] Interrupt latency on some 945GM platforms
Date: Wed, 22 Sep 2010 08:57:30 +0300 [thread overview]
Message-ID: <201009220857.30980.anarsoul@gmail.com> (raw)
In-Reply-To: <20100921155653.440afea4@jbarnes-desktop>
On 22 of September 2010 01:56:53 Jesse Barnes wrote:
> Can you guys try something like this? My theory is that 945GM has some
> power management behavior we're failing to configure correctly. If
> disabling it works, then it's likely related.
Nope, it doesn't help, sorry
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_d index 40cc5da..26e1d23 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5786,6 +5786,10 @@ void intel_init_clock_gating(struct drm_device *dev)
> I915_READ(MCHBAR_RENDER_STANDBY) &
> ~RCX_SW_EX }
> }
> +
> +
> + /* Disable power management on 945GM */
> + I915_WRITE(0x10f10, 0);
> }
>
> /* Set up chip specific display functions */
next prev parent reply other threads:[~2010-09-22 5:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201009132336.17310.anarsoul@gmail.com>
[not found] ` <20100913134441.762001f7@jbarnes-desktop>
[not found] ` <201009140010.14783.anarsoul@gmail.com>
2010-09-13 21:19 ` Interrupt latency on some 945GM platforms Jesse Barnes
2010-09-13 21:41 ` Vasily Khoruzhick
2010-09-13 21:46 ` Jesse Barnes
2010-09-13 21:52 ` Vasily Khoruzhick
2010-09-13 21:59 ` Jesse Barnes
2010-09-13 22:03 ` Vasily Khoruzhick
2010-09-14 0:55 ` Venkatesh Pallipadi
2010-09-14 8:09 ` Vasily Khoruzhick
2010-09-14 9:52 ` Thomas Gleixner
2010-09-14 12:29 ` Vasily Khoruzhick
2010-09-14 22:41 ` Sitsofe Wheeler
2010-09-15 7:07 ` Vasily Khoruzhick
2010-09-16 15:03 ` Vasily Khoruzhick
2010-09-16 18:07 ` Thomas Gleixner
2010-09-16 18:30 ` Vasily Khoruzhick
2010-09-16 18:42 ` Vasily Khoruzhick
2010-09-16 18:50 ` Thomas Gleixner
2010-09-16 20:06 ` Vasily Khoruzhick
2010-09-24 19:39 ` Jesse Barnes
2010-09-24 19:48 ` Vasily Khoruzhick
2010-09-24 19:51 ` Jesse Barnes
2010-09-26 10:53 ` Stefan Biereigel
2010-09-27 0:46 ` Shaohua Li
2010-09-27 5:45 ` Stefan Biereigel
2010-09-27 11:41 ` Vasily Khoruzhick
2010-09-27 21:18 ` Vasily Khoruzhick
2010-09-25 10:25 ` Paolo Ornati
2010-09-17 9:02 ` [Intel-gfx] " Simon Farnsworth
2010-09-17 16:30 ` Jesse Barnes
2010-09-17 12:50 ` Vasily Khoruzhick
2010-09-21 18:26 ` Paolo Ornati
2010-09-21 22:56 ` Jesse Barnes
2010-09-22 5:57 ` Vasily Khoruzhick [this message]
2010-09-23 18:21 ` Paolo Ornati
2010-09-25 10:28 ` Paolo Ornati
2010-10-16 15:54 ` [Intel-gfx] Interrupt latency on some 945GM platforms -- and TCP/IP silent data corruption? Paolo Ornati
2010-09-24 18:41 ` Interrupt latency on some 945GM platforms Jesse Barnes
2010-09-14 9:55 ` Andi Kleen
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=201009220857.30980.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@gmail.com \
--cc=simon.farnsworth@onelan.co.uk \
--cc=sitsofe@yahoo.com \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
/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