| 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: Mon, 22 Mar 2010 21:16:37 +0100 From: Andreas Bombe <aeb@...ian.org> To: Leon Woestenberg <leon.woestenberg@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Memory-mapped I/O barriers, state of affairs? On Mon, Mar 22, 2010 at 08:18:49PM +0100, Leon Woestenberg wrote: > What is the current solution for that particular problem, i.e. how > should I make sure host memory writes are committed before I have an > external DMA device act on it? The dma_sync_* functions, if you reuse DMA buffers without unmapping, take care of that. Otherwise the process of mapping them handles it. Documentation/DMA-API.txt and Documentation/PCI/PCI-DMA-mapping.txt document those functions. -- 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