From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261350AbVFAWj4 (ORCPT ); Wed, 1 Jun 2005 18:39:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261349AbVFAWcj (ORCPT ); Wed, 1 Jun 2005 18:32:39 -0400 Received: from relais.videotron.ca ([24.201.245.36]:51502 "EHLO relais.videotron.ca") by vger.kernel.org with ESMTP id S261345AbVFAW34 (ORCPT ); Wed, 1 Jun 2005 18:29:56 -0400 Date: Wed, 01 Jun 2005 18:29:37 -0400 (EDT) From: Nicolas Pitre Subject: Re: RT patch acceptance In-reply-to: <20050601213921.GF5413@g5.random> X-X-Sender: nico@localhost.localdomain To: Andrea Arcangeli Cc: Bill Huey , Esben Nielsen , Thomas Gleixner , Karim Yaghmour , Ingo Molnar , Paulo Marques , "Paul E. McKenney" , James Bruce , Nick Piggin , Andi Kleen , Sven-Thorsten Dietrich , dwalker@mvista.com, hch@infradead.org, Andrew Morton , lkml Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20050601192224.GV5413@g5.random> <20050601195905.GX5413@g5.random> <20050601201754.GA27795@nietzsche.lynx.com> <20050601203212.GZ5413@g5.random> <20050601204612.GA27934@nietzsche.lynx.com> <20050601210716.GB5413@g5.random> <20050601213921.GF5413@g5.random> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 1 Jun 2005, Andrea Arcangeli wrote: > On Wed, Jun 01, 2005 at 05:29:48PM -0400, Nicolas Pitre wrote: > > Actualy it's RTAI/rtlinux which is broken wrt the above IRQ disable. > > See for yourself when they're used and watch RTAI/rtlinux crash. > > Well it's not so clear so please elaborate since I'm curious. Especially > it'd be interesting to know if this is that an arm specific kernel > crash, or would it happen on x86 too? It would happen on any architecture supporting XIP from flash. The XIP code therefore polls the IRQ controller (with IRQs masked out) and whenever an IRQ is pending the flash operation is suspended and IRQs unmasked. In this case the hard IRQ latency is function of the flash suspend delay which is documented in the datasheet. > There sure can be arch dependencies where an hard_local_irq_disable can > be necessary in some places, but that's quite a separate topic, and on > x86 I don't see why it should crash. It would crash if the kernel is XIP. If not XIP then the local_irq_save() is never encountered in that case. Nicolas