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
| ||
|
Date: Thu, 04 Oct 2007 13:39:39 +1000 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com> Cc: Linux Kernel <linux-kernel@...r.kernel.org>, akpm@...ux-foundation.org, Greg KH <greg@...ah.com>, muli@...ibm.com, paulus@...ba.org, kristen.c.accardi@...el.com Subject: Re: [patch take 2][Intel-IOMMU] Fix for IOMMU early crash > > Why don't you use the new struct dev_archdata mechanism ? That's what I > > use on powerpc to provide optional iommu linkage to any device in the > > system. > Good one. I will certainly try out your idea and will update the list > tomorrow. The advantage is that it allows to completely isolate the iommu code from any dependency to PCI, which means you can implement DMA ops support for various platform devices or other fancy things. Maybe not the most useful in x86-land, but still ;-) Ben. - 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