From: David Stevens <stevensd@chromium.org>
To: Robin Murphy <robin.murphy@arm.com>, Christoph Hellwig <hch@lst.de>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Lu Baolu <baolu.lu@linux.intel.com>, Tom Murphy <murphyt7@tcd.ie>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
David Stevens <stevensd@chromium.org>
Subject: [PATCH v5 0/7] Fixes for dma-iommu swiotlb bounce buffers
Date: Mon, 16 Aug 2021 11:57:48 +0900 [thread overview]
Message-ID: <20210816025755.2906695-1-stevensd@google.com> (raw)
From: David Stevens <stevensd@chromium.org>
This patch set includes various fixes for dma-iommu's swiotlb bounce
buffers for untrusted devices. There are four fixes for correctness
issues, one for a performance issue, and one for general cleanup.
The min_align_mask issue was found when running fio on an untrusted nvme
device with bs=512. The other issues were found via code inspection, so
I don't have any specific use cases where things were not working, nor
any concrete performance numbers.
v4 -> v5:
- Fix xen build error
- Move _swiotlb refactor into its own patch
v3 -> v4:
- Fold _swiotlb functions into _page functions
- Add patch to align swiotlb buffer to iovad granule
- Combine if checks in iommu_dma_sync_sg_* functions
v2 -> v3:
- Add new patch to address min_align_mask bug
- Set SKIP_CPU_SYNC flag after syncing in map/unmap
- Properly call arch_sync_dma_for_cpu in iommu_dma_sync_sg_for_cpu
v1 -> v2:
- Split fixes into dedicated patches
- Less invasive changes to fix arch_sync when mapping
- Leave dev_is_untrusted check for strict iommu
David Stevens (7):
dma-iommu: fix sync_sg with swiotlb
dma-iommu: fix arch_sync_dma for map
dma-iommu: skip extra sync during unmap w/swiotlb
dma-iommu: fold _swiotlb helpers into callers
dma-iommu: Check CONFIG_SWIOTLB more broadly
swiotlb: support aligned swiotlb buffers
dma-iommu: account for min_align_mask
drivers/iommu/dma-iommu.c | 193 +++++++++++++++++---------------------
drivers/xen/swiotlb-xen.c | 2 +-
include/linux/swiotlb.h | 3 +-
kernel/dma/swiotlb.c | 11 ++-
4 files changed, 98 insertions(+), 111 deletions(-)
--
2.33.0.rc1.237.g0d66db33f3-goog
next reply other threads:[~2021-08-16 2:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 2:57 David Stevens [this message]
2021-08-16 2:57 ` [PATCH v5 1/7] dma-iommu: fix sync_sg with swiotlb David Stevens
2021-08-16 2:57 ` [PATCH v5 2/7] dma-iommu: fix arch_sync_dma for map David Stevens
2021-08-16 12:05 ` Christoph Hellwig
2021-08-16 2:57 ` [PATCH v5 3/7] dma-iommu: skip extra sync during unmap w/swiotlb David Stevens
2021-08-16 12:05 ` Christoph Hellwig
2021-08-16 2:57 ` [PATCH v5 4/7] dma-iommu: fold _swiotlb helpers into callers David Stevens
2021-08-16 12:07 ` Christoph Hellwig
2021-08-16 2:57 ` [PATCH v5 5/7] dma-iommu: Check CONFIG_SWIOTLB more broadly David Stevens
2021-08-16 12:08 ` Christoph Hellwig
2021-08-16 2:57 ` [PATCH v5 6/7] swiotlb: support aligned swiotlb buffers David Stevens
2021-08-16 2:57 ` [PATCH v5 7/7] dma-iommu: account for min_align_mask David Stevens
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=20210816025755.2906695-1-stevensd@google.com \
--to=stevensd@chromium.org \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murphyt7@tcd.ie \
--cc=robin.murphy@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).