Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751272AbWELNDl (ORCPT ); Fri, 12 May 2006 09:03:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751271AbWELNDl (ORCPT ); Fri, 12 May 2006 09:03:41 -0400 Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55]:19697 "EHLO ms-smtp-01.nyroc.rr.com") by vger.kernel.org with ESMTP id S1751269AbWELNDk (ORCPT ); Fri, 12 May 2006 09:03:40 -0400 Date: Fri, 12 May 2006 09:03:24 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Mark Hounschell cc: Ingo Molnar , john stultz , lkml , Thomas Gleixner Subject: Re: [RFC][PATCH -rt] irqd starvation on SMP by a single process? In-Reply-To: <44648532.8080200@compro.net> Message-ID: References: <1147401812.1907.14.camel@cog.beaverton.ibm.com> <20060512055025.GA25824@elte.hu> <4464740C.8060305@compro.net> <20060512115614.GA28377@elte.hu> <44648532.8080200@compro.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 37 On Fri, 12 May 2006, Mark Hounschell wrote: > > > > Mark, does this fix the problem? > > > > Ingo > > > > Index: linux-rt.q/drivers/net/3c59x.c > > =================================================================== > > --- 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); > > > > Yes it does. > It fixes it for both "complete preemption" and "normal preemption"? -- Steve - 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/