From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
iommu@lists.linux.dev, baolu.lu@linux.intel.com
Subject: Re: [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235
Date: Mon, 17 Apr 2023 12:21:58 +0100 [thread overview]
Message-ID: <6a775920-9260-f82e-dace-0b792f5371c4@arm.com> (raw)
In-Reply-To: <20230416064156.GA6410@lst.de>
On 2023-04-16 07:41, Christoph Hellwig wrote:
> On Thu, Mar 30, 2023 at 01:18:45PM +0100, Robin Murphy wrote:
>> FWIW "Marvell SATA" instantly makes me suspect the phantom function quirk.
>> What *should* happen is the IOMMU driver sees the PCI DMA aliases correctly
>> and sets up context entries for both 07.00.0 and 07.00.1, but it looks like
>> that may be what's gone awry.
>
> Looking at the bug report it seems this is device 9235, which doesn't
> need the DMA alias quirks.
Indeed that one doesn't appear to be in the quirk list currently.
However the symptom of DMA traffic from function 1 which the IOMMU
clearly wasn't expecting firmly suggests that it *does* need the quirk.
Digging up the original report, the lspci output there suggests that
07:00.1 isn't a real function, which would further confirm it.
The other thing which catches my interest is the seemingly-conflicting
"iommu=soft" and "intel_iommu=on" arguments - I could well believe that
refactoring the x86 IOMMU detection stuff might have subtly changed the
interaction there, such that previously it ended up not actually using
the IOMMU for DMA ops, but now it is?
Robin.
next prev parent reply other threads:[~2023-04-17 11:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 13:52 [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235 Linux regression tracking (Thorsten Leemhuis)
2023-03-22 9:46 ` Jason Adriaanse
2023-03-22 13:54 ` Christoph Hellwig
2023-03-28 1:22 ` Christoph Hellwig
2023-03-30 12:18 ` Robin Murphy
2023-03-31 2:20 ` Jason Adriaanse
2023-04-16 6:55 ` Christoph Hellwig
2023-04-22 6:25 ` Jason Adriaanse
2023-04-24 13:20 ` Robin Murphy
2023-04-24 13:44 ` Jason Adriaanse
2023-04-24 14:07 ` Robin Murphy
2023-04-25 4:17 ` Jason Adriaanse
2023-04-25 11:37 ` Robin Murphy
2023-04-25 13:58 ` Jason Adriaanse
2023-05-22 10:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:01 ` Robin Murphy
2023-05-22 11:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-02 13:07 ` Thorsten Leemhuis
2023-06-06 9:24 ` Christoph Hellwig
2023-06-06 10:26 ` Jason Adriaanse
2023-04-16 6:41 ` Christoph Hellwig
2023-04-17 11:21 ` Robin Murphy [this message]
2023-06-20 13:30 ` Linux regression tracking #update (Thorsten Leemhuis)
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=6a775920-9260-f82e-dace-0b792f5371c4@arm.com \
--to=robin.murphy@arm.com \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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.