Message Signalled Interrupts Question ...

Scott Long scottl at samsco.org
Fri May 11 03:02:25 UTC 2007


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 at 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



More information about the freebsd-current mailing list