linux-kernel - Re: sharing interrupt between PCI device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8d6898730811092239s3397ef6bw4bb5934de258786e@mail.gmail.com>
Date:	Mon, 10 Nov 2008 12:09:17 +0530
From:	"Nobin Mathew" <nobin.mathew@...il.com>
To:	"Grant Grundler" <grundler@...isc-linux.org>
Cc:	"Jiri Slaby" <jirislaby@...il.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, "Robert Hancock" <hancockr@...w.ca>
Subject: Re: sharing interrupt between PCI device

lspci -vs 1:4 is taken before inserting the drivers.

Thanks

On Mon, Nov 10, 2008 at 12:05 PM, Nobin Mathew <nobin.mathew@...il.com> wrote:
> lspci output
>
> [root@...alhost ~]# lspci -vs 1:4
> 01:04.0 System peripheral: Compaq Computer Corporation Integrated
> Lights Out Controller (rev 03)
>        Subsystem: Hewlett-Packard Company Unknown device 3305
>        Flags: medium devsel, IRQ 11
>        I/O ports at 2800 [size=256]
>        Memory at fdee0000 (32-bit, non-prefetchable) [size=512]
>        Capabilities: [f0] Power Management version 3
>
> 01:04.2 System peripheral: Compaq Computer Corporation Integrated
> Lights Out  Processor (rev 03)
>        Subsystem: Hewlett-Packard Company Unknown device 3305
>        Flags: medium devsel, IRQ 225
>        BIST result: 00
>        I/O ports at 1400 [disabled] [size=256]
>        Memory at fded0000 (32-bit, non-prefetchable) [disabled] [size=2K]
>        Memory at fdec0000 (32-bit, non-prefetchable) [disabled] [size=8K]
>        Memory at fde00000 (32-bit, non-prefetchable) [disabled] [size=512K]
>        [virtual] Expansion ROM at fdd20000 [disabled] [size=64K]
>        Capabilities: [f0] Power Management version 3
>
> 01:04.4 USB Controller: Hewlett-Packard Company Proliant iLO2 virtual
> USB controller (prog-if 00 [UHCI])
>        Subsystem: Hewlett-Packard Company Unknown device 3305
>        Flags: medium devsel, IRQ 225
>        I/O ports at 1800 [disabled] [size=32]
>        Capabilities: [f0] Power Management version 3
>
> 01:04.6 IPMI SMIC interface: Hewlett-Packard Company Proliant iLO2
> virtual UART (prog-if 01)
>        Subsystem: Hewlett-Packard Company Unknown device 3305
>        Flags: medium devsel, IRQ 50
>        Memory at fddf0000 (32-bit, non-prefetchable) [size=256]
>        Capabilities: [f0] Power Management version 3
>
> dmesg messages and /proc/interupts are attached.
>
>
> command sequence just for reference
>
> insmod hpilo
> insmod uhci_hcd
> cat /proc/interrupts
> dmesg
> rmmod hpilo
> rmmod uhci_hcd
> dmesg
>
> Thanks
> Nobin Mathew
>
> On Sun, Nov 9, 2008 at 12:45 AM, Grant Grundler
> <grundler@...isc-linux.org> wrote:
>> On Sat, Nov 08, 2008 at 08:10:54PM +0100, Jiri Slaby wrote:
>>> Grant Grundler napsal(a):
>>> > So I see how the IRQ is enabled and disabled. I still don't see where
>>> > an interrupt handler is bound to IRQ 225 (output you posted today in
>>> > another email).
>>>
>>> This irq setup is done during pci_enable_device.
>>
>> Sorry, I wasn't quite correct: pci_enable_device() should only assign IRQs,
>> not enable them. request_irq() would enable them.
>>
>>> > Nobin, can you dump /proc/interrupts when both drivers
>>> > are loaded and also send the dmesg output after both are loaded?
>>>
>>> This won't show the hp driver as it doesn't request_irq.
>>
>> Yup - that's what I expect too. But I was afraid something else might
>> be calling request_irq() and I'm just not seeing it. :)
>>
>> grant
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/