Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751406AbWEDFmf (ORCPT ); Thu, 4 May 2006 01:42:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751403AbWEDFmf (ORCPT ); Thu, 4 May 2006 01:42:35 -0400 Received: from mga02.intel.com ([134.134.136.20]:22344 "EHLO orsmga101-1.jf.intel.com") by vger.kernel.org with ESMTP id S1750749AbWEDFme convert rfc822-to-8bit (ORCPT ); Thu, 4 May 2006 01:42:34 -0400 X-IronPort-AV: i="4.05,86,1146466800"; d="scan'208"; a="31269844:sNHT18678247" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT X-MIMEOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [RFC][PATCH] Document what in IRQ is. Date: Thu, 4 May 2006 01:42:30 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [RFC][PATCH] Document what in IRQ is. Thread-index: AcZvJUmO6FTZVetSRz2WGxrw/9CM1gAFHGNA From: "Brown, Len" To: "Eric W. Biederman" , "Randy.Dunlap" Cc: , , , , , , , X-OriginalArrivalTime: 04 May 2006 05:42:31.0183 (UTC) FILETIME=[892E29F0:01C66F3D] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 963 Lines: 24 >Linux does not have generic infrastructure to allow two interrupt >sources to share the same token passed to the kernel. On i386 and x86_64 io_apic.c, see irq_pin_list This advertises to support multiple pins per IRQ. I suspect this code never runs, and simply adds complexity to code that has no shortage of complexity. If somebody can explain to me what a "shared ISA-space IRQ" is supposed to be, I'm all ears. I've had a BUG() in this code for a while waiting for it to be used, and never seen it fire. If we can get rid of that concept, then we have a 1:1 mapping between irqs and apic:pin. Possibly this simplification would be helpful as we re-think how the mapping from cpu:vector -> irq works. -Len - 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/