From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ns1.suse.de ([195.135.220.2]:55038 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbXBPMRD (ORCPT ); Fri, 16 Feb 2007 07:17:03 -0500 From: Andi Kleen Subject: Re: [RFC] killing the NR_IRQS arrays. Date: Fri, 16 Feb 2007 13:16:41 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702161316.41237.ak@suse.de> Sender: linux-arch-owner@vger.kernel.org To: "Eric W. Biederman" Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Benjamin Herrenschmidt , Ingo Molnar , Alan Cox List-ID: > I expect the most it makes sense to aim for 2.6.22 are the genirq > changes so the internal arch code is passing struct irq_desc > everywhere internally. Are there any livetime issues with passing pointers around? e.g. what happens on APIC hotunplug etc.? We don't necessarily support that yet, but for a big interface change it should be probably kept in mind first. -Andi