Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751150AbWEXRKF (ORCPT ); Wed, 24 May 2006 13:10:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751194AbWEXRKE (ORCPT ); Wed, 24 May 2006 13:10:04 -0400 Received: from gateway-1237.mvista.com ([63.81.120.158]:16925 "EHLO gateway-1237.mvista.com") by vger.kernel.org with ESMTP id S1751150AbWEXRKC (ORCPT ); Wed, 24 May 2006 13:10:02 -0400 Subject: Re: Ingo's realtime_preempt patch causes kernel oops From: Sven-Thorsten Dietrich To: tglx@linutronix.de Cc: Steven Rostedt , Yann.LEPROVOST@wavecom.fr, Daniel Walker , linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org, Ingo Molnar In-Reply-To: <1148489706.5239.68.camel@localhost.localdomain> References: <1148475334.24623.45.camel@localhost.localdomain> <1148476383.5239.54.camel@localhost.localdomain> <1148484729.14683.5.camel@localhost.localdomain> <1148485943.24623.54.camel@localhost.localdomain> <1148486614.5239.63.camel@localhost.localdomain> <1148488687.24623.67.camel@localhost.localdomain> <1148489706.5239.68.camel@localhost.localdomain> Content-Type: text/plain Organization: MontaVista Software, Inc. Date: Wed, 24 May 2006 10:09:22 -0700 Message-Id: <1148490563.17131.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1675 Lines: 52 On Wed, 2006-05-24 at 18:55 +0200, Thomas Gleixner wrote: > On Wed, 2006-05-24 at 12:38 -0400, Steven Rostedt wrote: > > OK I haven't worked on arm much at all. Only had to port one board > > before, and didn't need to get too involved. > > > > Can't two devices share the same interrupt line? Not talking about a > > cascading interrupt controller, but two actual devices that can trigger > > a single interrupt line. So, if this is the case, how do you disable a > > particular source without going to the driver itself? > > Yeah, the demux code has to go into the device driver to figure that > out, which is not hard to do on SoC devices, as the peripherals are > usually unique for a given SoC family. > > PCI and other globally shared devices are completely differnt beasts and > you would need a legion of hackers to fix that up. > I am looking at a particular case where I am dealing with it on PCI, and sharing USB. In this particular case, the uhci USB driver is almost structured, such that we can execute the lockless portion, and then run the locked code in a thread... Sven > tglx > > -- *********************************** Sven-Thorsten Dietrich Real-Time Software Architect MontaVista Software, Inc. 2901 Patrick Henry Drive, Suite 150 Santa Clara, CA 95054-1831 Direct: 408.572.7870 Main: 408.572.8000 Fax: 408.572.8005 www.mvista.com Platform To Innovate *********************************** - 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/