From: James Dingwall <james@dingwall.me.uk>
To: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>, iommu@lists.linux.dev
Subject: Re: BUG kernel 6.12.19 defautl_swiotlb_limit() returns wrong value for CONFIG_SWIOTLB_DYNAMIC=y effects atm only under XEN dom0
Date: Fri, 18 Sep 2026 07:37:32 +0100 [thread overview]
Message-ID: <aqzcLJQCCmqpdxz3@dingwall.me.uk> (raw)
Hi,
I've been having a problem with a Dell HBA330 SCSI controller (mpt3sas)
when booting under Xen and CONFIG_SWIOTLB_DYNAMIC=y is set. I had a
similar issue with a megaraid_sas card that I previously posted about:
https://lkml.iu.edu/hypermail/linux/kernel/2407.3/08254.html
In that case we rebuilt the kernel with CONFIG_SWIOTLB_DYNAMIC=n.
While investigating the current problem I came across a patch that was
posted on the xen-devel list:
https://lists.xen.org/archives/html/xen-devel/2025-05/msg00991.html
I have applied that to the Ubuntu 7.0.0-31 kernel sources which has
resolved the controller initialisation error I was encountering and the
system now boots as expected.
[ 3.921136] mpt3sas_cm0: no suitable DMA mask for 0000:03:00.0
[ 3.921275] mpt3sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:13610/_scsih_probe()!
I've included the patch below, I don't have the author's real address
for the s-o-b. I'm able to test alternative fixes if there are any
issues with this one.
Thanks,
James
Signed-off-by: Andreas Greve andreas.greve@xxxxxxxxxx
Tested-by: James Dingwall <james@dingwall.me.uk>
diff --git a/kernel/dma/swiotlb.c b/kernel/dma/swiotlb.c
index abcf3fa63a56..742e6cbbe852 100644
--- a/kernel/dma/swiotlb.c
+++ b/kernel/dma/swiotlb.c
@@ -1654,7 +1654,16 @@ phys_addr_t default_swiotlb_base(void)
phys_addr_t default_swiotlb_limit(void)
{
#ifdef CONFIG_SWIOTLB_DYNAMIC
- return io_tlb_default_mem.phys_limit;
+ struct io_tlb_mem *mem = &io_tlb_default_mem;
+ phys_addr_t retval = mem->defpool.end;
+ struct io_tlb_pool *pool;
+ rcu_read_lock();
+ list_for_each_entry_rcu(pool, &mem->pools, node) {
+ if (pool->end > retval)
+ retval = pool->end;
+ }
+ rcu_read_unlock();
+ return retval - 1;
#else
return io_tlb_default_mem.defpool.end - 1;
#endif
next reply other threads:[~2026-09-18 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260918063741eucas1p290cc7d0360de73b3d07a23316a238b48@eucas1p2.samsung.com>
2026-09-18 6:37 ` James Dingwall [this message]
2026-09-18 7:48 ` Marek Szyprowski
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=aqzcLJQCCmqpdxz3@dingwall.me.uk \
--to=james@dingwall.me.uk \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®