linux-kernel - Re: PCIE

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: <ada1wh560u1.fsf@cisco.com>
Date:	Thu, 24 May 2007 20:25:58 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Manu Abraham <abraham.manu@...il.com>
Cc:	Greg KH <greg@...ah.com>, linux-pci@...ey.karlin.mff.cuni.cz,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCIE

 > I am now wondering whether the usage of MSI would help in this case and
 > that i should be using enable_msi before request_irq ?

MSI interrupts are never shared.  So if pci_enable_msi() succeeds, you
can be sure that the interrupts you get with that IRQ number are
coming from your device.

But using MSI does not work on all systems, so your driver needs to
work with standard (possibly shared) INTx interrupts too.  And you
should probably provide at least a module flag to disable the use of
MSI, to avoid problems on buggy systems.

 - R.
-
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/