Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1612744

Re: [PATCH] xtensa: Fix mmap() support

From Christoph Hellwig <hch@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH] xtensa: Fix mmap() support
Date 2017-03-30 10:50 +0200
Message-ID <tqDWj-3FT-49@gated-at.bofh.it> (permalink)
References <tpUFP-4R5-7@gated-at.bofh.it> <tquzD-5dc-1@gated-at.bofh.it> <tqDMC-3Bj-25@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Mar 30, 2017 at 10:30:32AM +0200, Boris Brezillon wrote:
> I think I misunderstood what CONFIG_ARCH_NO_COHERENT_DMA_MMAP means.
> My understanding was that, if CONFIG_ARCH_NO_COHERENT_DMA_MMAP is not
> set, the architecture is assumed to be cache-coherent, but re-reading
> the option name I realize you're probably right.

It just says that the architecture did not support dma_common_mmap at
the point in time when I switched all architectures to use the common
dma_ops or implementing the various dma calls.  There is no inherent
logic behind the symbol, and if the few remaining architectures could
support it with a bit work the option could just go away.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] xtensa: Fix mmap() support Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-03-28 10:30 +0200
  Re: [PATCH] xtensa: Fix mmap() support Max Filippov <jcmvbkbc@gmail.com> - 2017-03-30 00:50 +0200
    Re: [PATCH] xtensa: Fix mmap() support Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-03-30 10:40 +0200
      Re: [PATCH] xtensa: Fix mmap() support Christoph Hellwig <hch@infradead.org> - 2017-03-30 10:50 +0200
      Re: [PATCH] xtensa: Fix mmap() support Max Filippov <jcmvbkbc@gmail.com> - 2017-03-30 11:10 +0200
        Re: [PATCH] xtensa: Fix mmap() support Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-03-30 12:10 +0200

csiph-web