linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* consolidate direct dma mapping V4
@ 2018-01-12  8:41 Christoph Hellwig
  0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2018-01-12  8:41 UTC (permalink / raw)
  To: iommu
  Cc: Konrad Rzeszutek Wilk, linux-alpha, linux-snps-arc,
	linux-arm-kernel, linux-c6x-dev, linux-cris-kernel,
	linux-hexagon, linux-ia64, linux-m68k, linux-metag, Michal Simek,
	linux-mips, linux-parisc, linuxppc-dev, patches, linux-s390,
	linux-sh, sparclinux, Guan Xuetao, x86, linux-arch, linux-kernel

Almost every architecture supports a direct dma mapping implementation,
where no iommu is used and the device dma address is a 1:1 mapping to
the physical address or has a simple linear offset.  Currently the
code for this implementation is most duplicated over the architectures,
and the duplicated again in the swiotlb code, and then duplicated again
for special cases like the x86 memory encryption DMA ops.

This series takes the existing very simple dma-noop dma mapping
implementation, enhances it with all the x86 features and quirks, and
creates a common set of architecture hooks for it and the swiotlb code.

It then switches a number of architectures to this generic
direct map implemention.

Note that for now this only handles architectures that do cache coherent
DMA, but a similar consolidation for non-coherent architectures is in the
work for later merge windows.

A git tree is also available:

   git://git.infradead.org/users/hch/misc.git dma-direct.3

Gitweb:

   http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-direct.3

Changes since V3
 - new patch to fix an off-by-one in mips dma_capable
Changes since V2:
 - fixed a few patch description typos
 - fixed a few printk formats
 - fixed an off by one in dma_coherent_ok
 - add a few Reviewed-by/Acked-by tags.
 - moved the swiotlb consolidation to a new series
 - dropped a few patches for now to not overwhelem the x86
   maintainers.  They will be resubmitted in the next merge window

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: consolidate direct dma mapping V4
       [not found] <20180112084232.2857-1-hch@lst.de>
@ 2018-01-16  7:52 ` Christoph Hellwig
  0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2018-01-16  7:52 UTC (permalink / raw)
  To: Christoph Hellwig
  Cc: iommu, linux-mips, linux-ia64, linux-sh, sparclinux, Guan Xuetao,
	linux-arch, linux-s390, linux-c6x-dev, linux-hexagon, x86,
	Konrad Rzeszutek Wilk, linux-snps-arc, linux-m68k, patches,
	linux-metag, linux-arm-kernel, Michal Simek, linux-parisc,
	linux-cris-kernel, linux-kernel, linux-alpha, linuxppc-dev

I've pulled this into the dma-mapping for-next branch so that we get
a few days exposure before then end of the merge window.  If there is
anything important (e.g. the powerpc naming issue) please send
incremental patches.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-01-16  7:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-12  8:41 consolidate direct dma mapping V4 Christoph Hellwig
     [not found] <20180112084232.2857-1-hch@lst.de>
2018-01-16  7:52 ` Christoph Hellwig

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).