Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932390AbWEBGPH (ORCPT ); Tue, 2 May 2006 02:15:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932389AbWEBGPG (ORCPT ); Tue, 2 May 2006 02:15:06 -0400 Received: from ns.suse.de ([195.135.220.2]:42964 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932390AbWEBGPE (ORCPT ); Tue, 2 May 2006 02:15:04 -0400 From: Andi Kleen To: "Brown, Len" Subject: Re: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision Date: Tue, 2 May 2006 08:14:48 +0200 User-Agent: KMail/1.9.1 Cc: "Eric W. Biederman" , "Protasevich, Natalie" , sergio@sergiomb.no-ip.org, "Kimball Murray" , linux-kernel@vger.kernel.org, akpm@digeo.com, kmurray@redhat.com, linux-acpi@vger.kernel.org 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: <200605020814.49144.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 809 Lines: 21 > >- Modify do_IRQ to get passed an interrupt vector# from the > > interrupt vector instead of an irq number, and then lookup > > the irq number in vector_irq. This means we don't need > > a code stub per irq, and allows us to handle more irqs > > by simply increasing NR_IRQS. > > isn't the vector number already on the stack from > ENTRY(interrupt) > pushl $vector-256 Yes - and interrupts/vectors are currently always identical. If we go to per CPU IDTs I suspect the stubs will just need to be generated at runtime and start passing interrupts. -Andi - 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/