From: Robin Murphy <robin.murphy@arm.com>
To: Walter Wu <walter-zh.wu@mediatek.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: wsd_upstream <wsd_upstream@mediatek.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dma-direct: fix DMA_ATTR_NO_KERNEL_MAPPING
Date: Mon, 1 Nov 2021 10:29:19 +0000 [thread overview]
Message-ID: <0316e4f0-b0ad-c702-676f-36347b4ebcb1@arm.com> (raw)
In-Reply-To: <20211101031558.7184-1-walter-zh.wu@mediatek.com>
On 2021-11-01 03:15, Walter Wu wrote:
> DMA_ATTR_NO_KERNEL_MAPPING is to avoid creating a kernel mapping
> for the allocated buffer, but current implementation is that
> PTE of allocated buffer in kernel page table is valid. So we
> should set invalid for PTE of allocate buffer so that there are
> no kernel mapping for the allocated buffer.
No, the semantic of NO_KERNEL_MAPPING is an indication that the *caller*
does not need a mapping, such that the DMA API implementation may choose
to optimise for that internally. It has never given any guarantee of any
particular behaviour - like most attributes it is only a hint.
> In some cases, we don't hope the allocated buffer to be read
> by cpu or speculative execution, so we use DMA_ATTR_NO_KERNEL_MAPPING
> to get no kernel mapping in order to achieve this goal.
If it's important that no CPU accesses to this memory can happen, then I
think the only way to absolutely guarantee that is to exclude it from
the kernel's memory map in the first place, e.g. as a DT reserved-memory
region with the "no-map" property.
Robin.
> Signed-off-by: Walter Wu <walter-zh.wu@mediatek.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Matthias Brugger <matthias.bgg@gmail.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> kernel/dma/direct.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> index 4c6c5e0635e3..aa10b4c5d762 100644
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -13,6 +13,7 @@
> #include <linux/vmalloc.h>
> #include <linux/set_memory.h>
> #include <linux/slab.h>
> +#include <asm/cacheflush.h>
> #include "direct.h"
>
> /*
> @@ -169,6 +170,9 @@ void *dma_direct_alloc(struct device *dev, size_t size,
> if (!PageHighMem(page))
> arch_dma_prep_coherent(page, size);
> *dma_handle = phys_to_dma_direct(dev, page_to_phys(page));
> + /* remove kernel mapping for pages */
> + set_memory_valid((unsigned long)phys_to_virt(dma_to_phys(dev, *dma_handle)),
> + size >> PAGE_SHIFT, 0);
> /* return the page pointer as the opaque cookie */
> return page;
> }
> @@ -278,6 +282,10 @@ void dma_direct_free(struct device *dev, size_t size,
>
> if ((attrs & DMA_ATTR_NO_KERNEL_MAPPING) &&
> !force_dma_unencrypted(dev) && !is_swiotlb_for_alloc(dev)) {
> + size = PAGE_ALIGN(size);
> + /* create kernel mapping for pages */
> + set_memory_valid((unsigned long)phys_to_virt(dma_to_phys(dev, dma_addr)),
> + size >> PAGE_SHIFT, 1);
> /* cpu_addr is a struct page cookie, not a kernel address */
> dma_free_contiguous(dev, cpu_addr, size);
> return;
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-11-01 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 3:15 [PATCH] dma-direct: fix DMA_ATTR_NO_KERNEL_MAPPING Walter Wu
2021-11-01 6:10 ` kernel test robot
2021-11-01 8:34 ` Ard Biesheuvel
2021-11-01 12:20 ` Walter Wu
2021-11-01 14:17 ` Ard Biesheuvel
2021-11-02 3:21 ` Walter Wu
2021-11-02 6:43 ` Christoph Hellwig
2021-11-01 10:29 ` Robin Murphy [this message]
2021-11-01 12:07 ` Walter Wu
2021-11-02 6:41 ` Christoph Hellwig
2021-11-02 7:08 ` Walter Wu
2021-11-02 7:26 ` Walter Wu
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=0316e4f0-b0ad-c702-676f-36347b4ebcb1@arm.com \
--to=robin.murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=matthias.bgg@gmail.com \
--cc=walter-zh.wu@mediatek.com \
--cc=wsd_upstream@mediatek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox