From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 3F800DDE48 for ; Mon, 29 Jan 2007 10:51:56 +1100 (EST) Date: Sun, 28 Jan 2007 15:51:55 -0800 (PST) Message-Id: <20070128.155155.51857352.davem@davemloft.net> To: ebiederm@xmission.com Subject: Re: [RFC/PATCH 0/16] Ops based MSI Implementation From: David Miller In-Reply-To: References: <1170026259.26655.114.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: kyle@parisc-linux.org, linuxppc-dev@ozlabs.org, brice@myri.com, greg@kroah.com, shaohua.li@intel.com, linux-pci@atrey.karlin.mff.cuni.cz List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: ebiederm@xmission.com (Eric W. Biederman) Date: Sun, 28 Jan 2007 16:38:28 -0700 > That isn't even the reason it is that way. It is because allocating > 4096 irqs in a single vector is a bad idea, and because it requires you > to pass type information of what kind of msi you are dealing with to the > lower levels in an allocation routine that make it bad idea. Because > if you don't consider the IBM HV it provides not benefit and just puts > unnecessary loops, and type information in architecture code. Eric, get over it, sparc64 will need this kind of abstraction too in order to support MSI properly. There are specific calls into the sparc64 hypervisor for MSI vs. MSI-X configuration operations. So a type is necessary. Sun Niagara and IBM RTAS hypervisors are not going to get rearchitected because you peed your pants over this on some Linux mailing list :-) Trust me on that one :))