Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752747AbXEZWtR (ORCPT ); Sat, 26 May 2007 18:49:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750954AbXEZWtH (ORCPT ); Sat, 26 May 2007 18:49:07 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:51407 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750743AbXEZWtF (ORCPT ); Sat, 26 May 2007 18:49:05 -0400 Date: Sat, 26 May 2007 15:49:10 -0700 (PDT) Message-Id: <20070526.154910.78725926.davem@davemloft.net> To: abraham.manu@gmail.com Cc: rdreier@cisco.com, greg@kroah.com, linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org Subject: Re: PCIE From: David Miller In-Reply-To: <46584C30.4030206@gmail.com> References: <46561287.8020103@gmail.com> <46584C30.4030206@gmail.com> X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 698 Lines: 18 From: Manu Abraham Date: Sat, 26 May 2007 19:03:12 +0400 > i presume then i shouldn't be using IRQF_SHARED, if using MSI. That's actually a really good question. It is likely architecture dependant whether the PCI controller wires unique MSI interrupts to shared cpu interrupt lines. I can imagine many systems where the cpu simply doesn't have enough interrupt pins to uniquely identify every possible MSI interrupt source. - 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/