From: Robin Murphy <robin.murphy@arm.com>
To: "Petr Tesařík" <petr@tesarici.cz>, "T.J. Mercier" <tjmercier@google.com>
Cc: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
isaacmanjarres@google.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-direct: Set SG_DMA_SWIOTLB flag for dma-direct
Date: Thu, 9 May 2024 14:28:33 +0100 [thread overview]
Message-ID: <9af152ec-e68f-4f10-833b-400f9fe87bda@arm.com> (raw)
In-Reply-To: <20240504105319.75eec54a@meshulam.tesarici.cz>
On 04/05/2024 9:53 am, Petr Tesařík wrote:
> On Fri, 3 May 2024 18:37:12 +0000
> "T.J. Mercier" <tjmercier@google.com> wrote:
>
>> As of commit 861370f49ce4 ("iommu/dma: force bouncing if the size is
>> not cacheline-aligned") sg_dma_mark_swiotlb is called when
>> dma_map_sgtable takes the IOMMU path and uses SWIOTLB for some portion
>> of a scatterlist. It is never set for the direct path, so drivers
>> cannot always rely on sg_dma_is_swiotlb to return correctly after
>> calling dma_map_sgtable. Fix this by calling sg_dma_mark_swiotlb in the
>> direct path like it is in the IOMMU path.
>>
>> Signed-off-by: T.J. Mercier <tjmercier@google.com>
>> ---
>> kernel/dma/direct.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
>> index 4d543b1e9d57..52f0dcb25ca2 100644
>> --- a/kernel/dma/direct.c
>> +++ b/kernel/dma/direct.c
>> @@ -12,7 +12,7 @@
>> #include <linux/pfn.h>
>> #include <linux/vmalloc.h>
>> #include <linux/set_memory.h>
>> -#include <linux/slab.h>
>> +#include <linux/swiotlb.h>
>> #include "direct.h"
>>
>> /*
>> @@ -497,6 +497,8 @@ int dma_direct_map_sg(struct device *dev, struct scatterlist *sgl, int nents,
>> goto out_unmap;
>> }
>> sg_dma_len(sg) = sg->length;
>> + if (is_swiotlb_buffer(dev, dma_to_phys(dev, sg->dma_address)))
>> + sg_dma_mark_swiotlb(sg);
>> }
>>
>> return nents;
>
> I'm not sure this does the right thing. IIUC when the scatterlist flags
> include SG_DMA_SWIOTLB, iommu_dma_sync_sg_for_*() will call
> iommu_dma_sync_single_for_*(), which in turn translates the DMA address
> to a physical address using iommu_iova_to_phys(). It seems to me that
> this function may not work correctly if there is no IOMMU, but it also
> seems to me that the scatterlist may contain such non-IOMMU addresses.
In principle dma-direct *could* make use of the SG_DMA_SWIOTLB flag for
an ever-so-slightly cheaper check than is_swiotlb_buffer() in sync_sg
and unmap_sg, the same way as iommu-dma does. However the benefit would
be a lot less significant than for iommu-dma, where it's really about
the overhead of needing to perform iommu_iova_to_phys() translations for
every segment every time in order to *get* the right thing to check
is_swiotlb_buffer() on - that's what would be unreasonably prohibitive
otherwise.
Thanks,
Robin
next prev parent reply other threads:[~2024-05-09 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 18:37 [PATCH] dma-direct: Set SG_DMA_SWIOTLB flag for dma-direct T.J. Mercier
2024-05-04 8:53 ` Petr Tesařík
2024-05-09 13:28 ` Robin Murphy [this message]
2024-05-06 5:29 ` Christoph Hellwig
2024-05-06 16:00 ` T.J. Mercier
2024-05-06 16:02 ` Christoph Hellwig
2024-05-06 16:10 ` T.J. Mercier
2024-05-06 16:19 ` Christoph Hellwig
2024-05-06 16:39 ` T.J. Mercier
2024-05-07 5:43 ` Christoph Hellwig
2024-05-07 20:07 ` T.J. Mercier
2024-05-08 11:33 ` Christoph Hellwig
2024-05-09 12:54 ` Robin Murphy
2024-05-09 18:26 ` T.J. Mercier
2024-05-08 17:19 ` Catalin Marinas
2024-05-08 20:14 ` T.J. Mercier
2024-05-09 7:49 ` Catalin Marinas
2024-05-09 13:06 ` Christoph Hellwig
2024-05-09 18:32 ` T.J. Mercier
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=9af152ec-e68f-4f10-833b-400f9fe87bda@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=isaacmanjarres@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=petr@tesarici.cz \
--cc=tjmercier@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 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.