From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id E9C80DDE19 for ; Tue, 20 May 2008 07:49:01 +1000 (EST) Message-ID: <4831F5F7.9050900@freescale.com> Date: Mon, 19 May 2008 16:49:43 -0500 From: Scott Wood MIME-Version: 1.0 To: Rune Torgersen Subject: Re: Oops with PREEMPT-RT on 2.6.25.4 References: <4831D527.2020907@freescale.com> <4831ECF0.5090101@freescale.com> <4831F364.8020702@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Rune Torgersen wrote: > Scott Wood wrote: >> Try calling irq_set_chip_and_handler() with handle_level_irq, rather >> than irq_set_chip(). The -rt patch doesn't seem to have threadified >> the __do_IRQ() path. > > The demuxer is setting itself up with set_irq_chained handler(), any > pointers on how to change to irq_set_chip_and_handler()? No, I mean the call to set_irq_chip() in pci_pic_host_map() where it sets up the IRQs it manages, not the cascade IRQ itself. -Scott