linux-kernel - Re: [PATCH 01/34] bnx2: Use pci_enable_msix

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] [day] [month] [year] [list]

Message-ID: <20140212180803.GA7948@dhcp-26-207.brq.redhat.com>
Date:	Wed, 12 Feb 2014 19:08:04 +0100
From:	Alexander Gordeev <agordeev@...hat.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH 01/34] bnx2: Use pci_enable_msix_range()

On Wed, Feb 12, 2014 at 10:00:28AM -0700, Bjorn Helgaas wrote:
> > Do you want pci_enable_msi_exact() in addition to pci_enable_msix_exact()?
> 
> If there are cases where pci_enable_msi_exact() would be used, I guess
> the same arguments would apply, so yes.  I haven't looked at the

Just a handful of cases in the tree where it could be used for MSI right now,
but still - they do exist.

> archives, but I have this nagging feeling that this is exactly what
> you proposed initially, and I had some objection.  If so, I'm sorry
> about changing my mind :)

You are on PCI guard, no worries ;)

> Bjorn

-- 
Regards,
Alexander Gordeev
agordeev@...hat.com
--
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/