From owner-cvs-src@FreeBSD.ORG Thu Nov 16 17:32:05 2006 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 661DB16A494; Thu, 16 Nov 2006 17:32:05 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B6643D55; Thu, 16 Nov 2006 17:32:04 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id kAGHVsts009768; Thu, 16 Nov 2006 09:32:04 -0800 (PST) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id kAGHVsdQ009765; Thu, 16 Nov 2006 09:31:54 -0800 (PST) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 16 Nov 2006 09:31:54 -0800 (PST) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: John Baldwin In-Reply-To: <200611161114.42297.jhb@freebsd.org> Message-ID: <20061116092809.O9739@ns1.feral.com> References: <455BA0B6.1000109@samsco.org> <455BA914.7010602@samsco.org> <20061115.220331.-957833409.imp@bsdimp.com> <200611161114.42297.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Scott Long , src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, ru@freebsd.org, "M. Warner Losh" Subject: Re: cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/em if_em.c if_em.h src/sys/dev/mpt mpt.h mpt_pci.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 17:32:05 -0000 >> >> Is there some convention for MSI naming? Or are the resources >> basically anonymous? > > They are just IRQ values. On x86 they will be >= 256, but that may not be > true on other platforms. Other busses might also support multiple IRQs per > device (if you had HT peripherals I think they could do this). In general > IRQs are just cookies anyway. On x86 they index into the interrupt_sources[] > array. On other platforms they can have other meanings. It would almost be > better if SYS_RES_IRQ was just SYS_RES_INTR. > Let me put back on my very very dusty Solaris DDI team hat and point out that you either coerce the naming of interrupts to an architected number space (as did Digital Unix and does Linux and more or less does FreeBSD) or leave the naming of interrupts to the bus nexus it has meaning to.