From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-xtensa@linux-xtensa.org, Michal Simek <monstr@monstr.eu>,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: remove default fallbacks in dma_map_ops
Date: Thu, 25 Jul 2019 06:33:56 +0000 [thread overview]
Message-ID: <20190725063401.29904-1-hch@lst.de> (raw)
Hi all,
we have a few places where the DMA mapping layer has non-trivial default
actions that are questionable and/or dangerous.
This series instead wires up the mmap, get_sgtable and get_required_mask
methods explicitly and cleans up some surrounding areas. This also means
we could get rid of the ARCH_NO_COHERENT_DMA_MMAP kconfig option, as we
now require a mmap method wired up, or in case of non-coherent dma-direct
the presence of the arch_dma_coherent_to_pfn hook. The only interesting
case is that the sound code also checked the ARCH_NO_COHERENT_DMA_MMAP
symbol in somewhat odd ways, so I'd like to see a review of the sound
situation before going forward with that patch.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Takashi Iwai <tiwai@suse.de>, Robin Murphy <robin.murphy@arm.com>,
Michal Simek <monstr@monstr.eu>,
linux-arm-kernel@lists.infradead.org,
linux-m68k@lists.linux-m68k.org, linux-parisc@vger.kernel.org,
linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: remove default fallbacks in dma_map_ops
Date: Thu, 25 Jul 2019 08:33:56 +0200 [thread overview]
Message-ID: <20190725063401.29904-1-hch@lst.de> (raw)
Hi all,
we have a few places where the DMA mapping layer has non-trivial default
actions that are questionable and/or dangerous.
This series instead wires up the mmap, get_sgtable and get_required_mask
methods explicitly and cleans up some surrounding areas. This also means
we could get rid of the ARCH_NO_COHERENT_DMA_MMAP kconfig option, as we
now require a mmap method wired up, or in case of non-coherent dma-direct
the presence of the arch_dma_coherent_to_pfn hook. The only interesting
case is that the sound code also checked the ARCH_NO_COHERENT_DMA_MMAP
symbol in somewhat odd ways, so I'd like to see a review of the sound
situation before going forward with that patch.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-xtensa@linux-xtensa.org, Michal Simek <monstr@monstr.eu>,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: remove default fallbacks in dma_map_ops
Date: Thu, 25 Jul 2019 08:33:56 +0200 [thread overview]
Message-ID: <20190725063401.29904-1-hch@lst.de> (raw)
Hi all,
we have a few places where the DMA mapping layer has non-trivial default
actions that are questionable and/or dangerous.
This series instead wires up the mmap, get_sgtable and get_required_mask
methods explicitly and cleans up some surrounding areas. This also means
we could get rid of the ARCH_NO_COHERENT_DMA_MMAP kconfig option, as we
now require a mmap method wired up, or in case of non-coherent dma-direct
the presence of the arch_dma_coherent_to_pfn hook. The only interesting
case is that the sound code also checked the ARCH_NO_COHERENT_DMA_MMAP
symbol in somewhat odd ways, so I'd like to see a review of the sound
situation before going forward with that patch.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-xtensa@linux-xtensa.org, Michal Simek <monstr@monstr.eu>,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: remove default fallbacks in dma_map_ops
Date: Thu, 25 Jul 2019 08:33:56 +0200 [thread overview]
Message-ID: <20190725063401.29904-1-hch@lst.de> (raw)
Hi all,
we have a few places where the DMA mapping layer has non-trivial default
actions that are questionable and/or dangerous.
This series instead wires up the mmap, get_sgtable and get_required_mask
methods explicitly and cleans up some surrounding areas. This also means
we could get rid of the ARCH_NO_COHERENT_DMA_MMAP kconfig option, as we
now require a mmap method wired up, or in case of non-coherent dma-direct
the presence of the arch_dma_coherent_to_pfn hook. The only interesting
case is that the sound code also checked the ARCH_NO_COHERENT_DMA_MMAP
symbol in somewhat odd ways, so I'd like to see a review of the sound
situation before going forward with that patch.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-xtensa@linux-xtensa.org, Michal Simek <monstr@monstr.eu>,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: remove default fallbacks in dma_map_ops
Date: Thu, 25 Jul 2019 08:33:56 +0200 [thread overview]
Message-ID: <20190725063401.29904-1-hch@lst.de> (raw)
Hi all,
we have a few places where the DMA mapping layer has non-trivial default
actions that are questionable and/or dangerous.
This series instead wires up the mmap, get_sgtable and get_required_mask
methods explicitly and cleans up some surrounding areas. This also means
we could get rid of the ARCH_NO_COHERENT_DMA_MMAP kconfig option, as we
now require a mmap method wired up, or in case of non-coherent dma-direct
the presence of the arch_dma_coherent_to_pfn hook. The only interesting
case is that the sound code also checked the ARCH_NO_COHERENT_DMA_MMAP
symbol in somewhat odd ways, so I'd like to see a review of the sound
situation before going forward with that patch.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-07-25 6:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 6:33 Christoph Hellwig [this message]
2019-07-25 6:33 ` remove default fallbacks in dma_map_ops Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` [PATCH 1/5] m68knommu: add a pgprot_noncached stub Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` [PATCH 2/5] dma-mapping: move the dma_get_sgtable API comments from arm to common code Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` [PATCH 3/5] dma-mapping: explicitly wire up ->mmap and ->get_sgtable Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:33 ` Christoph Hellwig
2019-07-25 6:34 ` [PATCH 4/5] dma-mapping: provide a better default ->get_required_mask Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-29 9:57 ` Geert Uytterhoeven
2019-07-29 9:57 ` Geert Uytterhoeven
2019-07-29 9:57 ` Geert Uytterhoeven
2019-07-29 9:57 ` Geert Uytterhoeven
2019-07-29 9:57 ` Geert Uytterhoeven
2019-07-30 6:26 ` Christoph Hellwig
2019-07-30 6:26 ` Christoph Hellwig
2019-07-30 6:26 ` Christoph Hellwig
2019-07-30 6:26 ` Christoph Hellwig
2019-07-30 6:26 ` Christoph Hellwig
2019-07-25 6:34 ` [PATCH 5/5] dma-mapping: remove ARCH_NO_COHERENT_DMA_MMAP Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-07-25 6:34 ` Christoph Hellwig
2019-08-02 7:03 ` Christoph Hellwig
2019-08-02 7:03 ` Christoph Hellwig
2019-08-02 7:03 ` Christoph Hellwig
2019-08-02 7:03 ` Christoph Hellwig
2019-08-02 7:03 ` Christoph Hellwig
2019-08-02 8:24 ` Takashi Iwai
2019-08-02 8:24 ` Takashi Iwai
2019-08-02 8:24 ` Takashi Iwai
2019-08-02 8:24 ` Takashi Iwai
2019-08-02 8:24 ` Takashi Iwai
2019-08-03 10:30 ` Christoph Hellwig
2019-08-03 10:30 ` Christoph Hellwig
2019-08-03 10:30 ` Christoph Hellwig
2019-08-03 10:30 ` Christoph Hellwig
2019-08-03 10:30 ` Christoph Hellwig
2019-08-03 11:22 ` Takashi Iwai
2019-08-03 11:22 ` Takashi Iwai
2019-08-03 11:22 ` Takashi Iwai
2019-08-03 11:22 ` Takashi Iwai
2019-08-03 11:22 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190725063401.29904-1-hch@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=monstr@monstr.eu \
--cc=robin.murphy@arm.com \
--cc=tiwai@suse.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.