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, 15 May 2008 10:12:25 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: muli@...ibm.com Cc: fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, alexisb@...ibm.com Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops On Wed, 14 May 2008 08:49:24 +0300 Muli Ben-Yehuda <muli@...ibm.com> wrote: > On Tue, May 13, 2008 at 03:04:50PM +0900, FUJITA Tomonori wrote: > > > This patchset adds per-device dma_mapping_ops support for > > CONFIG_X86_64 like POWER architecture does. This change enables us > > to cleanly fix the Calgary IOMMU issue that some devices are not > > behind the IOMMU [1]. It also would be helpful to handle KVM PCI > > passthrough. > > Awesome! Much needed, thank you for doing this. No problem. Well, as you know, it's just a base. We need more work to solve the problems on the top of this. I'd like to have a mechanism to register a hook called when a new pci (or dma capable) device is created. It enables IOMMUs to set up an appropriate dma_mapping_ops per device. It could also enables us to simplify the IOMMUs code to initilize devices at startup (for exmple, intel-iommu checks all the pci devices and creates a domain per device if necessary). I'll post an updated version against -mm. If people seems to be fine with per-device dma_mapping_ops, then I'll work on further issues. -- 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