| 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: <455C37B9.4020000@ens-lyon.org> Date: Thu, 16 Nov 2006 11:04:41 +0100 From: Brice Goglin <Brice.Goglin@...-lyon.org> To: Roland Dreier <rdreier@...co.com> CC: LKML <linux-kernel@...r.kernel.org> Subject: [PATCH] ALSA: hda-intel - Disable MSI support by default] (forgot to cc: LKML) Roland Dreier wrote: > > A whitelist is an awkward solution, the problem is the number of > > chipsets available with MSI will continue to grow. And the assumption > > is that after Microsoft OS supports MSI, that newer chipsets will work. > > Maybe a whitelist for older systems and then enable everything after a > DMI cutoff date by default? Doesn't work on non-PC stuff though... When I started sending patches about all this, I proposed a whitelist for PCI bridges and a blacklist for PCIe bridges, but Greg was against whitelisting. Now, reading this thread, I am very disturbed with the idea of disabling MSI on all non-Intel bridges. Blacklisting correctly shouldn't be that hard. From my point of view, there are several non-Intel bridges that seem to support MSI very well (especially some HT<->PCIe bridges). And apart from being required for ipath, MSI improves the performance of network drivers a bit, so I'd rather keep it enabled on trusted bridges... Brice - 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/
Powered by blists - more mailing lists