From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>, iommu@lists.linux-foundation.org
Cc: David Rientjes <rientjes@google.com>
Subject: Re: [PATCH 04/10] dma-direct: clean up the remapping checks in dma_direct_alloc
Date: Thu, 4 Nov 2021 12:35:59 +0000 [thread overview]
Message-ID: <bc7bc5eb-282d-3dbb-b4f9-b9bbd9e0f0a1@arm.com> (raw)
In-Reply-To: <20211021090611.488281-5-hch@lst.de>
On 2021-10-21 10:06, Christoph Hellwig wrote:
> Add a local variable to track if we want to remap the returned address
> using vmap and use that to simplify the code flow.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> kernel/dma/direct.c | 47 +++++++++++++++++++++++----------------------
> 1 file changed, 24 insertions(+), 23 deletions(-)
>
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> index 60cb75aa6778e..a6b6fe72af4d1 100644
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -166,6 +166,7 @@ static void *dma_direct_alloc_from_pool(struct device *dev, size_t size,
> void *dma_direct_alloc(struct device *dev, size_t size,
> dma_addr_t *dma_handle, gfp_t gfp, unsigned long attrs)
> {
> + bool remap = false;
How about also adding a "bool set_uncached = false"...
> struct page *page;
> void *ret;
>
> @@ -217,9 +218,23 @@ void *dma_direct_alloc(struct device *dev, size_t size,
> if (!page)
> return NULL;
>
> - if ((IS_ENABLED(CONFIG_DMA_DIRECT_REMAP) &&
> - !dev_is_dma_coherent(dev)) ||
> - (IS_ENABLED(CONFIG_DMA_REMAP) && PageHighMem(page))) {
> + if (!dev_is_dma_coherent(dev) && IS_ENABLED(CONFIG_DMA_DIRECT_REMAP)) {
> + remap = true;
> + } else if (PageHighMem(page)) {
> + /*
> + * Depending on the cma= arguments and per-arch setup,
> + * dma_alloc_contiguous could return highmem pages.
> + * Without remapping there is no way to return them here, so
> + * log an error and fail.
> + */
> + if (!IS_ENABLED(CONFIG_DMA_REMAP)) {
> + dev_info(dev, "Rejecting highmem page from CMA.\n");
> + goto out_free_pages;
> + }
> + remap = true;
> + }
...then "else if (IS_ENABLED(CONFIG_ARCH_HAS_DMA_SET_UNCACHED))
set_uncached = true;"...
> +
> + if (remap) {
> /* remove any dirty cache lines on the kernel alias */
> arch_dma_prep_coherent(page, size);
>
> @@ -229,36 +244,22 @@ void *dma_direct_alloc(struct device *dev, size_t size,
> __builtin_return_address(0));
> if (!ret)
> goto out_free_pages;
> - if (dma_set_decrypted(dev, ret, size))
> - goto out_unmap_pages;
> - memset(ret, 0, size);
> - goto done;
> - }
> -
> - if (PageHighMem(page)) {
> - /*
> - * Depending on the cma= arguments and per-arch setup
> - * dma_alloc_contiguous could return highmem pages.
> - * Without remapping there is no way to return them here,
> - * so log an error and fail.
> - */
> - dev_info(dev, "Rejecting highmem page from CMA.\n");
> - goto out_free_pages;
> + } else {
> + ret = page_address(page);
As before, I'm thinking that dma_set_decrypted() probably belongs in here.
> }
>
> - ret = page_address(page);
> if (dma_set_decrypted(dev, ret, size))
> - goto out_free_pages;
> + goto out_unmap_pages;
> memset(ret, 0, size);
>
> - if (IS_ENABLED(CONFIG_ARCH_HAS_DMA_SET_UNCACHED) &&
> - !dev_is_dma_coherent(dev)) {
> + if (!dev_is_dma_coherent(dev) && !remap &&
> + IS_ENABLED(CONFIG_ARCH_HAS_DMA_SET_UNCACHED)) {
...then from earlier we'd have just a nice "if (set_uncached)" here?
> arch_dma_prep_coherent(page, size);
> ret = arch_dma_set_uncached(ret, size);
> if (IS_ERR(ret))
> goto out_encrypt_pages;
From a quick Kconfig survey, this is a purely theoretical exercise in
dead code generation. Let's just be pragmatic, stick in a
"BUILD_BUG_ON(IS_ENABLED(CONFIG_ARCH_HAS_DMA_SET_UNCACHED) &&
IS_ENABLED(CONFIG_ARCH_HAS_MEM_ENCRYPT));" and leave this re-encryption
case for theoretical future arch maintainers to worry about.
All that said, I'm also now wondering why the arch_set_dma_uncached()
call is down here in the first place. If we could do it at as an else
case of the remapping stage (given that it's a semantically equivalent
operation), the complexity inherently falls away.
> }
> -done:
> +
> *dma_handle = phys_to_dma_direct(dev, page_to_phys(page));
> return ret;
>
>
If the "out_unmap_pages" step is even still necessary, I think the
condition there should now simplify down to "if (remap)" as well.
Robin.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-11-04 12:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 9:06 dma-direct fixes and cleanups v2 Christoph Hellwig
2021-10-21 9:06 ` [PATCH 01/10] dma-direct: factor out dma_set_{de,en}crypted helpers Christoph Hellwig
2021-11-04 12:35 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 02/10] dma-direct: unmapped remapped pages when dma_set_decrypted Christoph Hellwig
2021-11-04 12:35 ` Robin Murphy
2021-11-09 14:10 ` Christoph Hellwig
2021-11-09 14:27 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 03/10] dma-direct: leak memory that can't be re-encrypted Christoph Hellwig
2021-11-04 12:35 ` Robin Murphy
2021-11-09 14:19 ` Christoph Hellwig
2021-10-21 9:06 ` [PATCH 04/10] dma-direct: clean up the remapping checks in dma_direct_alloc Christoph Hellwig
2021-11-04 12:35 ` Robin Murphy [this message]
2021-11-09 14:23 ` Christoph Hellwig
2021-10-21 9:06 ` [PATCH 05/10] dma-direct: factor out a helper for DMA_ATTR_NO_KERNEL_MAPPING allocations Christoph Hellwig
2021-11-04 12:36 ` Robin Murphy
2021-11-09 14:25 ` Christoph Hellwig
2021-11-09 14:39 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 06/10] dma-direct: refactor the !coherent checks in dma_direct_alloc Christoph Hellwig
2021-11-04 12:36 ` Robin Murphy
2021-11-09 14:27 ` Christoph Hellwig
2021-10-21 9:06 ` [PATCH 07/10] dma-direct: warn if there is no pool for force unencrypted allocations Christoph Hellwig
2021-11-04 12:36 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 08/10] dma-direct: drop two CONFIG_DMA_RESTRICTED_POOL conditionals Christoph Hellwig
2021-11-04 12:37 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 09/10] dma-direct: factor the swiotlb code out of __dma_direct_alloc_pages Christoph Hellwig
2021-11-04 12:37 ` Robin Murphy
2021-10-21 9:06 ` [PATCH 10/10] dma-direct: add a dma_direct_use_pool helper Christoph Hellwig
2021-11-04 12:37 ` Robin Murphy
2021-11-04 8:54 ` dma-direct fixes and cleanups v2 Christoph Hellwig
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=bc7bc5eb-282d-3dbb-b4f9-b9bbd9e0f0a1@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=rientjes@google.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