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, 22 Nov 2007 11:43:14 +0900 From: FUJITA Tomonori <tomof@....org> To: linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org Cc: fujita.tomonori@....ntt.co.jp Subject: [PATCH -mm 0/4] fix iommu segment boundary problems This is the latter half of my iommu work to make the IOMMUs respect LLDs restrictions. IOMMUs allocate memory areas without considering a low level driver's segment boundary limits. So we have some workarounds: splitting sg segments again in LLDs; reserving all I/O space spanning 4GB boundary in IOMMUs (with assumption that all the LLDs have 4GB boundary restrictions). The goal is killing all the workarounds. This patchset adds new accessors for segment_boundary_mask in device_dma_parameters structure in the same way as the first half of my work did for max_segment_size. Currently, I fixed only swiotlb. Next, I'll generalize swiotlb's free area management and convert all the IOMMUs to use it. Or I'll generalize a free area management to use bitmap that most of the IOMMUs use and convert them to use it. This is against 2.6.24-rc3-mm1. The first half of my iommu work is: http://thread.gmane.org/gmane.linux.scsi/35602 - 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