public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Interrupt latency on some 945GM platforms
Date: Tue, 14 Sep 2010 00:41:18 +0300	[thread overview]
Message-ID: <201009140041.23645.anarsoul@gmail.com> (raw)
In-Reply-To: <20100913141955.752cbdea@jbarnes-desktop>

[-- Attachment #1: Type: Text/Plain, Size: 1663 bytes --]

В сообщении от 14 of September 2010 00:19:55 автор Jesse Barnes написал:
> On Tue, 14 Sep 2010 00:10:08 +0300
> 
> Vasily Khoruzhick <anarsoul@gmail.com> wrote:
> > В сообщении от 13 of September 2010 23:44:41 автор Jesse Barnes написал:
> > > I remember seeing a similar problem on an Eee PC I had; it seemed to be
> > > timer/interrupt related somehow.  If I booted with clocksource=tsc
> > > (or maybe it was pit) I got nice smooth animations, but if I used the
> > > HPET things were really slow.
> > > 
> > > Does the same work for you?
> > 
> > Yeah, it works for me (will use it as temporary workaround). But it
> > definitely is not clean solution, as I can't use nohz mode with tsc
> > clocksource :)
> 
> Thomas, does this ring any bells for you?
> 
> I think the root symptom of the issue is that we get a much reduced i915
> interrupt frequency (or no interrupts) on some 945GM platforms when
> using HPET as our clock source.
> 
> In fact, on the platform I tested, it seemed that the i915 IRQs wouldn't
> generate interrupts at all when HPET was used.  But shaking the mouse or
> generating network traffic was enough to get i915 interrupts coming in,
> even though neither of those interrupts were shared with the i915
> device.
> 
> Here's hoping you have some ideas to try...
> 
> Thanks,

Jesse, is it possible to disable wait for vsync somehow? cpufreq is not 
working for me with nohz=no for some reason, as result cpu temperature and 
power usage are higher. I prefer to see tearing but with low power usage and 
without jerky keyboard :)

Regards
Vasily

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-09-13 21:42 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 [this message]
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
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=201009140041.23645.anarsoul@gmail.com \
    --to=anarsoul@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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