Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751408AbWBZVbd (ORCPT ); Sun, 26 Feb 2006 16:31:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751410AbWBZVbd (ORCPT ); Sun, 26 Feb 2006 16:31:33 -0500 Received: from viper.oldcity.dca.net ([216.158.38.4]:62390 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S1751408AbWBZVbd (ORCPT ); Sun, 26 Feb 2006 16:31:33 -0500 Subject: Re: old radeon latency problem still unfixed? From: Lee Revell To: Benjamin Herrenschmidt Cc: Arjan van de Ven , linux-kernel In-Reply-To: <1140988293.3982.8.camel@localhost.localdomain> References: <1140917787.24141.78.camel@mindpipe> <1140945232.2934.0.camel@laptopd505.fenrus.org> <1140982513.24141.118.camel@mindpipe> <1140988293.3982.8.camel@localhost.localdomain> Content-Type: text/plain Date: Sun, 26 Feb 2006 16:31:28 -0500 Message-Id: <1140989489.24141.159.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.5.91 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1434 Lines: 32 On Mon, 2006-02-27 at 08:11 +1100, Benjamin Herrenschmidt wrote: > > AFAICT it's more like trading 3D performance for having audio work at > > all. Other video drivers that were too aggressive and caused audio > > dropouts (VIA) were fixed, even though there was a slight performance > > cost. > > In addition, the radeon DRI shouldn't do active spinning like that in > "normal" circumstances ... it should instead block on interrupts. if it > does, I suppose that could safely be considered as a bug in the radeon > DRM/DRI driver. It will do such loops on engine reset and such, which > happen on X launch, VT switches or in case of lockups... I have to > double check what happens in the code path used for 2d/3d transitions > though, those might be a problem. What about switching from 2D->3D mode, like when xscreensaver kicks in? IIRC people reported audio underruns when that happened but I could never narrow it down any further. If as Arjan said the only lock this driver takes is the BKL then it's either a local config issue (ancient kernel or failure to enable preempt BKL) or something at the hardware level... I'm waiting for more info from the original reporter. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/