linux-kernel - Re: Lossy interrupts on x86

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-prev] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2007 17:40:48 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Lossy interrupts on x86_64

On Thursday, September 20, 2007, Thomas Gleixner wrote:
> On Thu, 2007-09-20 at 12:22 -0700, Jesse Barnes wrote:
> > > Eeek, that sounds scary. Can you add "highres=off" as well ?
> >
> > FWIW I just tried your linux-2.6-hires tree with the attached
> > config and still see the problem.  It doesn't look like NO_HZ is
> > even an option in that tree...
>
> Right, that's a 2.6-hrt update tree for Linus to pull. The 64 bit
> parts are not in there. It's basically Linus + some fixes.

Arg, looks like this is actually a DRM problem, but it doesn't exist in 
the DRM upstream tree, only the upstream kernel tree.  I've only seen 
it on 965 chips though, and they have other vblank related problems, so 
I won't worry about it for 2.6.23 proper.

Thanks,
Jesse
-
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/