From owner-freebsd-stable@FreeBSD.ORG Fri Apr 10 14:53:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A522106564A; Fri, 10 Apr 2009 14:53:26 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id E8A578FC1A; Fri, 10 Apr 2009 14:53:25 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (p5DCF3F99.dip.t-dialin.net [93.207.63.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id AED5D8A00D1; Fri, 10 Apr 2009 16:53:09 +0200 (CEST) Message-ID: <49DF5D60.9010803@bsdforen.de> Date: Fri, 10 Apr 2009 16:53:20 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.21 (X11/20090408) MIME-Version: 1.0 To: Robert Noland References: <1238293386.00093672.1238281804@10.7.7.3> <49CF0803.1070505@FreeBSD.org> <49CF2F8D.6000905@bsdforen.de> <49CF4EB9.60108@FreeBSD.org> <49CF49F5.6010800@bsdforen.de> <49CF615A.6050304@FreeBSD.org> <49CF595A.30805@bsdforen.de> <49CF6B28.2080400@FreeBSD.org> <49CF60AB.4040709@bsdforen.de> <49CF6899.2060002@bsdforen.de> <49CF8E8D.1080604@bsdforen.de> <49CF9C19.3020509@FreeBSD.org> <49D5DA33.4010800@bsdforen.de> <1238778004.65025.30.camel@balrog.2hip.net> In-Reply-To: <1238778004.65025.30.camel@balrog.2hip.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Motin , freebsd-stable@freebsd.org Subject: Re: powerd broken X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2009 14:53:26 -0000 Robert Noland wrote: > I've been working on the Intel vblank / irq issues. Every time I commit > something thinking that I have it resolved, it isn't. So I'm waiting on > hardware to arrive that will let me test this all more thoroughly. I do > have a patch that I think fixes most of the issues on Intel, but the ddx > driver is still doing some silly things that cause issues in some cases. > I *think* the only outstanding issue I have with Intel is if something > is rendering (synced to vblank or not) when the display goes into dpms > sleep, there isn't anything to block that app, so it renders as hard as > it can even though it isn't being displayed. In reality, this probably > isn't a huge issue, but running gears while the display is asleep keeps > the cpu at 100%, which isn't ideal. Normal apps that aren't trying to > draw as fast as they can, shouldn't cause an issue. With the latest drm, the IRQ craziness is gone. However, the crappy performance remains. 2 months ago a RELENG_7 with all packages up to date yielded 124fps in a q3 timedemo that now yields 80fps. Regards