| 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: <adaveceah8l.fsf@cisco.com> Date: Fri, 20 Jul 2007 14:38:02 -0700 From: Roland Dreier <rdreier@...co.com> To: "Manu Abraham" <abraham.manu@...il.com> Cc: "Leech, Christopher" <christopher.leech@...el.com>, "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>, "Nelson, Shannon" <shannon.nelson@...el.com>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, davem@...emloft.net, jeff@...zik.org, "Williams, Dan J" <dan.j.williams@...el.com> Subject: Re: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X > In a case where you have a device that which supports MSI-X (multiple > interrupts) but the device in default is in MSI mode, ie some > configuration change is needed on the device. In such a case, how > would one handle between MSI-X and MSI ? > > ie the device initially doesn't support MSI-X I don't understand the question really. Does the PCI spec even allow a device to be in MSI mode by default? Surely the OS must initialize the address/message before the device can generate an MSI? What device do you have in mind? I guess the interesting case is a PCIe device that supports MSI and MSI-X but not legacy interrupts. However I would assume such a device would come up with both MSI and MSI-X disabled. - 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/
Powered by blists - more mailing lists