From owner-freebsd-current@FreeBSD.ORG Fri May 11 03:02:25 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4866B16A402 for ; Fri, 11 May 2007 03:02:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id F1BF013C468 for ; Fri, 11 May 2007 03:02:24 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l4B32GxU021804; Thu, 10 May 2007 21:02:16 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4643DCB3.9080505@samsco.org> Date: Thu, 10 May 2007 21:02:11 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Rui Paulo References: <20070511021015.GF21472@obelix.dsto.defence.gov.au> <868xbwyu3i.wl%rpaulo@fnop.net> <86vef0oz1e.wl%rpaulo@fnop.net> In-Reply-To: <86vef0oz1e.wl%rpaulo@fnop.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 10 May 2007 21:02:16 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Message Signalled Interrupts Question ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 03:02:25 -0000 Rui Paulo wrote: > At Fri, 11 May 2007 03:25:37 +0100, > Rui Paulo wrote: >> At Fri, 11 May 2007 10:10:15 +0800, >> Wilkinson, Alex wrote: >>> Howdy, >>> >>> How does one know whether their PCI device supports MSI >>> and that FreeBSD is using MSI for this device ? >> You can boot with verbose mode on and the info will show up on dmesg. >> >> For example >> found-> vendor=0x11ab, dev=0x4362, revid=0x22 >> bus=1, slot=0, func=0 >> class=02-00-00, hdrtype=0x00, mfdev=0 >> cmdreg=0x0007, statreg=0x0010, cachelnsz=64 (dwords) >> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> intpin=a, irq=11 >> powerspec 2 supports D0 D1 D2 D3 current D0 >> MSI supports 2 messages, 64 bit > > Sorry, pciconf -lvc shows better information. > > For example, > mskc0@pci1:0:0: class=0x020000 card=0x532111ab chip=0x436211ab rev=0x22 hdr=0x00 > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > device = 'Yukon 88E8053 PCI-E Gigabit Ethernet Controller (Copper)' > class = network > subclass = ethernet > cap 01[48] = powerspec 2 supports D0 D1 D2 D3 current D0 > cap 03[50] = VPD > cap 05[5c] = MSI supports 2 messages, 64 bit > cap 10[e0] = PCI-Express 1 legacy endpoint > > pciconf -lvc is also a relatively new feature, I'm not sure it was in the 6.2 release, and it certainly wasn't in 6.1 or prior. The verbose dmesg output has reported MSI for several years. Scott