Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262523AbTEFKiJ (ORCPT ); Tue, 6 May 2003 06:38:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262524AbTEFKiJ (ORCPT ); Tue, 6 May 2003 06:38:09 -0400 Received: from [66.212.224.118] ([66.212.224.118]:53004 "HELO hemi.commfireservices.com") by vger.kernel.org with SMTP id S262523AbTEFKiI (ORCPT ); Tue, 6 May 2003 06:38:08 -0400 Date: Tue, 6 May 2003 06:41:57 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: Alan Cox Cc: Andrew Morton , Shane Shrybman , Linux Kernel Mailing List Subject: Re: 2.5.68-mmX: Drowning in irq 7: nobody cared! In-Reply-To: <1052213733.28797.1.camel@dhcp22.swansea.linux.org.uk> Message-ID: References: <1052141029.2527.27.camel@mars.goatskin.org> <20030505143006.29c0301a.akpm@digeo.com> <1052213733.28797.1.camel@dhcp22.swansea.linux.org.uk> 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: 931 Lines: 35 On Tue, 6 May 2003, Alan Cox wrote: > With APIC at least it doesnt suprise me the least. The IRQ hack seems > extremely racey. Remember on most systems (especially with PIII type > APIC) IRQ delivery is asynchronous to the bus so you get > > IRQ arrives > sound card > loop > clean up IRQ > IRQ sent > still more work, do it > done > HANDLED > > IRQ arrives > sound card > Umm duh no work for me > NOT HANDLED > > Whine > > For anything where you get pairs of close IRQ's Shouldn't this also be observed more easily on P4/xAPIC since you can have a pending vector in the IRR and ISR whilst the core processes one. Zwane -- function.linuxpower.ca - 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/