lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 13 Sep 2010 14:19:55 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Vasily Khoruzhick <anarsoul@...il.com>
Cc:	intel-gfx@...ts.freedesktop.org,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Interrupt latency on some 945GM platforms

On Tue, 14 Sep 2010 00:10:08 +0300
Vasily Khoruzhick <anarsoul@...il.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 Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ