Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263893AbUANWVw (ORCPT ); Wed, 14 Jan 2004 17:21:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264126AbUANWVw (ORCPT ); Wed, 14 Jan 2004 17:21:52 -0500 Received: from modemcable178.89-70-69.mc.videotron.ca ([69.70.89.178]:53120 "EHLO montezuma.fsmlabs.com") by vger.kernel.org with ESMTP id S263893AbUANWVv (ORCPT ); Wed, 14 Jan 2004 17:21:51 -0500 Date: Wed, 14 Jan 2004 17:20:51 -0500 (EST) From: Zwane Mwaikambo To: "Nakajima, Jun" cc: James Cleverdon , Andrew Morton , linux-kernel@vger.kernel.org, Linus Torvalds , Chris McDermott , "Martin J. Bligh" Subject: RE: [PATCH] 2.6.1-mm2: Get irq_vector size right for generic subarch UP installer kernels In-Reply-To: <7F740D512C7C1046AB53446D3720017361883B@scsmsx402.sc.intel.com> Message-ID: References: <7F740D512C7C1046AB53446D3720017361883B@scsmsx402.sc.intel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 31 On Wed, 14 Jan 2004, Nakajima, Jun wrote: > assign_irq_vector() is okay, and it simply returns vectors > (FIRST_DEVICE_VECTOR <= vector < FIRST_SYSTEM_VECTOR). That means those > IRQs will eventually share the same vector(s). Look at the code. Ok so you have different irqs sharing vectors, how does this work with the following (where $vector really means $irq of course)? .data ENTRY(interrupt) .text vector=0 ENTRY(irq_entries_start) .rept NR_IRQS ALIGN 1: pushl $vector-256 jmp common_interrupt Also i was thinking about when you exhaust all 200 odd spare vectors and then end up doing set_intr_gate twice on the same vector? I may be missing something really obvious here. Thanks - 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/