iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: iommu@lists.linux-foundation.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] "iommu/amd: Relax locking in dma_ops path" makes tg3 ethernet transmit queue timeout
Date: Mon, 18 May 2020 15:32:09 +0200	[thread overview]
Message-ID: <20200518133209.GM8135@suse.de> (raw)
In-Reply-To: <4E9B03FB-9DA5-4831-B4CE-A0AA645D3F22@canonical.com>

On Mon, May 18, 2020 at 05:06:45PM +0800, Kai-Heng Feng wrote:
> 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.

Is there any error message from the IOMMU driver?

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-05-18 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  9:06 [Regression] "iommu/amd: Relax locking in dma_ops path" makes tg3 ethernet transmit queue timeout Kai-Heng Feng
2020-05-18 13:32 ` Joerg Roedel [this message]
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=20200518133209.GM8135@suse.de \
    --to=jroedel@suse.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=kai.heng.feng@canonical.com \
    --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;
as well as URLs for NNTP newsgroup(s).