From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: jroedel@suse.de
Cc: iommu@lists.linux-foundation.org,
open list <linux-kernel@vger.kernel.org>
Subject: [Regression] "iommu/amd: Relax locking in dma_ops path" makes tg3 ethernet transmit queue timeout
Date: Mon, 18 May 2020 17:06:45 +0800 [thread overview]
Message-ID: <4E9B03FB-9DA5-4831-B4CE-A0AA645D3F22@canonical.com> (raw)
Hi,
Broadcom ethernet tg3 unusable after commit 92d420ec028d ("iommu/amd: Relax locking in dma_ops path").
After a short period it stops:
[ 122.717144] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x237/0x240()
[ 122.717152] NETDEV WATCHDOG: enp3s0 (tg3): transmit queue 0 timed out
After testing the patch section by section, this is the part that caused the regression:
@@ -2578,19 +2580,8 @@ static dma_addr_t map_page(struct device *dev, struct page *page,
dma_mask = *dev->dma_mask;
- spin_lock_irqsave(&domain->lock, flags);
-
- addr = __map_single(dev, domain->priv, paddr, size, dir, false,
+ return __map_single(dev, domain->priv, paddr, size, dir, false,
dma_mask);
- if (addr == DMA_ERROR_CODE)
- goto out;
-
- domain_flush_complete(domain);
-
-out:
- spin_unlock_irqrestore(&domain->lock, flags);
-
- return addr;
}
Particularly, as soon as the spinlock is removed, the issue can be reproduced.
Function domain_flush_complete() doesn't seem to affect the status.
However, the .map_page callback was removed by be62dbf554c5 ("iommu/amd: Convert AMD iommu driver to the dma-iommu api"), so there's no easy revert for this issue.
This is still reproducible as of today's mainline kernel, v5.7-rc6.
Kai-Heng
next reply other threads:[~2020-05-18 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 9:06 Kai-Heng Feng [this message]
2020-05-18 13:32 ` Joerg Roedel
2020-05-18 14:05 ` Kai-Heng Feng
2020-05-18 15:32 ` Kai-Heng Feng
2020-06-29 12:33 ` Kai-Heng Feng
2020-08-21 13:43 ` Joerg Roedel
2020-08-21 13:50 ` Kai-Heng Feng
2020-08-21 14:43 ` Joerg Roedel
2020-08-23 13:19 ` Kai-Heng Feng
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=4E9B03FB-9DA5-4831-B4CE-A0AA645D3F22@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®