| 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
| ||
|
Message-Id: <20101027.084604.226761472.davem@davemloft.net> Date: Wed, 27 Oct 2010 08:46:04 -0700 (PDT) From: David Miller <davem@...emloft.net> To: michael@...erman.id.au Cc: bhutchings@...arflare.com, somnath.kotur@...lex.com, netdev@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: [PATCH net-next-2.6 1/2] be2net: Adding an option to use INTx instead of MSI-X From: Michael Ellerman <michael@...erman.id.au> Date: Wed, 27 Oct 2010 10:20:35 +1100 > On Tue, 2010-10-26 at 14:32 +0100, Ben Hutchings wrote: >> Michael Ellerman wrote: >> > On Mon, 2010-10-25 at 16:25 -0700, David Miller wrote: >> > > From: Ben Hutchings <bhutchings@...arflare.com> >> > > Date: Mon, 25 Oct 2010 23:38:53 +0100 > >> > Ethtool would be nice, but only for network drivers. Is there a generic >> > solution, quirks are obviously not keeping people happy. >> >> Since this is (normally) a property of the system, pci=nomsi is the >> generic solution. > > Sort of, it's a big hammer. Did all these driver writers not know about > pci=nomsi or did they prefer to add a parameter to their driver for some > reason? Every time I've actually done the work to try and track down the true issue, it always turned out to be a PCI chipset problem rather than a device specific issue. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists