From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751296AbWELNgt (ORCPT ); Fri, 12 May 2006 09:36:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751298AbWELNgt (ORCPT ); Fri, 12 May 2006 09:36:49 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:30621 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1751296AbWELNgt (ORCPT ); Fri, 12 May 2006 09:36:49 -0400 Date: Fri, 12 May 2006 15:36:27 +0200 From: Ingo Molnar To: Steven Rostedt Cc: Mark Hounschell , linux-kernel , Daniel Walker , Thomas Gleixner , akpm@osdl.org Subject: Re: 3c59x vortex_timer rt hack (was: rt20 patch question) Message-ID: <20060512133627.GA30447@elte.hu> References: <4461E53B.7050905@compro.net> <446207D6.2030602@compro.net> <44623157.9090105@compro.net> <20060512081628.GA26736@elte.hu> <20060512092159.GC18145@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-ELTE-SpamScore: -2.8 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.8 required=5.9 tests=ALL_TRUSTED,AWL autolearn=no SpamAssassin version=3.0.3 -2.8 ALL_TRUSTED Did not pass through any untrusted hosts 0.0 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > > > On Fri, 12 May 2006, Ingo Molnar wrote: > > > --- linux-rt.q.orig/drivers/net/3c59x.c > > +++ linux-rt.q/drivers/net/3c59x.c > > @@ -1897,7 +1897,8 @@ vortex_timer(unsigned long data) > > > > if (vp->medialock) > > goto leave_media_alone; > > - disable_irq(dev->irq); > > + /* hack! */ > > + disable_irq_nosync(dev->irq); > > old_window = ioread16(ioaddr + EL3_CMD) >> 13; > > EL3WINDOW(4); > > media_status = ioread16(ioaddr + Wn4_Media); > > BTW, I originally thought about having Mark do this, but I'm nervious > about the side effects that this might have. Basically, it's doing > ioreads from the device while the interrupt could be doing iowrites. yes, that can happen - but since this is a timeout, this is rather unlikely in practice. Nevertheless it's possible, so i marked the code a hack. Ingo