From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de ([212.227.126.174]:60386 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946362AbXBQBiI (ORCPT ); Fri, 16 Feb 2007 20:38:08 -0500 From: Arnd Bergmann Subject: Re: [RFC] killing the NR_IRQS arrays. Date: Sat, 17 Feb 2007 02:37:42 +0100 References: <20070216195256.GE2572@flint.arm.linux.org.uk> <1171665426.5644.99.camel@localhost.localdomain> In-Reply-To: <1171665426.5644.99.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702170237.42910.arnd@arndb.de> Sender: linux-arch-owner@vger.kernel.org To: Benjamin Herrenschmidt Cc: Russell King , "Eric W. Biederman" , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Andi Kleen , Ingo Molnar , Alan Cox List-ID: On Friday 16 February 2007 23:37, Benjamin Herrenschmidt wrote: > You might want to have a look at the powerpc API with it's remaping > capabilities. It's very nice for handling multiple domain spaces. It > might be of some use for you. I don't consider the powerpc virtual IRQs a solution for the problem. While I believe you did the right thing for powerpc with generalizing this over all its platforms, it really isn't more than a workaround for the problem that we can't deal well with the static irq_desc array. When that problem is now getting worse on other architectures, we should try to get it right on all of them, rather than spreading the workaround further. Arnd <><