From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Ben Copeland <ben.copeland@linaro.org>,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
regressions@lists.linux.dev, linux-nvme@lists.infradead.org,
Dan Carpenter <dan.carpenter@linaro.org>,
axboe@kernel.dk, sagi@grimberg.me, iommu@lists.linux.dev,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: next-20250627: IOMMU DMA warning during NVMe I/O completion after 06cae0e3f61c
Date: Tue, 1 Jul 2025 17:00:58 -0400 [thread overview]
Message-ID: <aGRMilWhgF4z0WOf@kbusch-mbp> (raw)
In-Reply-To: <20250701132936.GA18807@lst.de>
On Tue, Jul 01, 2025 at 03:29:36PM +0200, Christoph Hellwig wrote:
> Yes, that's broken, and I remember fixing it before. A little digging
> shows that my fixes disappeared between the oct 30 version of Leon's
> dma-split branch and the latest one somewhere. Below is what should
> restore it, but at least when forcing my Intel IOMMU down this path it
> still has issues with VPTEs already set. So maybe Bob should not try
> it quite yet. I'll try to get to it, but my availability today and
> tomorrow is a bit limited.
Let's say we're using ARM64 SMMU configured with 64k granularity like I
showed earlier.
Now let's send a read command with 128k transfer, and let's assume the
payload is two 64k aligned physical segments, so we have 2 bvecs.
Since nvme's virtual boundary is smaller than the iommu's granule, we
won't attempt to coalesce. We instead iommu map each bvec segment
individually.
And let's say each segment just so happens to get consecutive IOVA's.
The mapping side had done each segment individually, but your proposal
here will assume the contiguous dma_addr ranges were done as a single
larger mapping. Is that okay?
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 38be1505dbd9..02bb5cf5db1a 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -678,40 +678,55 @@ static void nvme_free_prps(struct request *req)
> enum dma_data_direction dir = rq_dma_dir(req);
> int length = iod->total_len;
> dma_addr_t dma_addr;
> - int i, desc;
> + int prp_len, i, desc;
> __le64 *prp_list;
> + dma_addr_t dma_start;
> u32 dma_len;
>
> dma_addr = le64_to_cpu(iod->cmd.common.dptr.prp1);
> - dma_len = min_t(u32, length,
> - NVME_CTRL_PAGE_SIZE - (dma_addr & (NVME_CTRL_PAGE_SIZE - 1)));
> - length -= dma_len;
> + prp_len = NVME_CTRL_PAGE_SIZE - (dma_addr & (NVME_CTRL_PAGE_SIZE - 1));
> + prp_len = min(length, prp_len);
> + length -= prp_len;
> if (!length) {
> - dma_unmap_page(dma_dev, dma_addr, dma_len, dir);
> + dma_unmap_page(dma_dev, dma_addr, prp_len, dir);
> return;
> }
>
> + dma_start = dma_addr;
> + dma_len = prp_len;
> + dma_addr = le64_to_cpu(iod->cmd.common.dptr.prp2);
> +
> if (length <= NVME_CTRL_PAGE_SIZE) {
> - dma_unmap_page(dma_dev, dma_addr, dma_len, dir);
> - dma_addr = le64_to_cpu(iod->cmd.common.dptr.prp2);
> - dma_unmap_page(dma_dev, dma_addr, length, dir);
> - return;
> + if (dma_addr != dma_start + dma_len) {
> + dma_unmap_page(dma_dev, dma_start, dma_len, dir);
> + dma_start = dma_addr;
> + dma_len = 0;
> + }
> + dma_len += length;
> + goto done;
> }
>
> i = 0;
> desc = 0;
> prp_list = iod->descriptors[desc];
> do {
> - dma_unmap_page(dma_dev, dma_addr, dma_len, dir);
> if (i == NVME_CTRL_PAGE_SIZE >> 3) {
> prp_list = iod->descriptors[++desc];
> i = 0;
> }
>
> dma_addr = le64_to_cpu(prp_list[i++]);
> - dma_len = min(length, NVME_CTRL_PAGE_SIZE);
> - length -= dma_len;
> + if (dma_addr != dma_start + dma_len) {
> + dma_unmap_page(dma_dev, dma_start, dma_len, dir);
> + dma_start = dma_addr;
> + dma_len = 0;
> + }
> + prp_len = min(length, NVME_CTRL_PAGE_SIZE);
> + dma_len += prp_len;
> + length -= prp_len;
> } while (length);
> +done:
> + dma_unmap_page(dma_dev, dma_start, dma_len, dir);
> }
>
> static void nvme_free_sgls(struct request *req)
next prev parent reply other threads:[~2025-07-01 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250630075218epcas5p1f3d467fffa468cac0ccd012c193e94df@epcas5p1.samsung.com>
2025-06-30 7:50 ` next-20250627: IOMMU DMA warning during NVMe I/O completion after 06cae0e3f61c Ben Copeland
2025-06-30 13:33 ` Christoph Hellwig
2025-06-30 19:51 ` Ben Copeland
2025-07-01 19:43 ` Keith Busch
2025-06-30 20:25 ` Keith Busch
2025-07-01 0:54 ` Keith Busch
2025-07-01 13:05 ` Ben Copeland
2025-07-01 14:20 ` Keith Busch
2025-07-01 13:29 ` Christoph Hellwig
2025-07-01 15:58 ` Leon Romanovsky
2025-07-01 21:00 ` Keith Busch [this message]
2025-07-03 9:30 ` Christoph Hellwig
2025-07-03 14:29 ` Keith Busch
2025-07-03 15:13 ` Ben Copeland
2025-07-03 5:54 ` Kanchan Joshi
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=aGRMilWhgF4z0WOf@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=ben.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
/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.