From: Christoph Hellwig <hch@infradead.org>
To: Yifeng Li <tomli@tomli.me>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Add func1 DMA quirk for Marvell 88SE9125 SATA controller
Date: Wed, 17 Nov 2021 02:12:04 -0800 [thread overview]
Message-ID: <YZTVdOlEbMb0tv59@infradead.org> (raw)
In-Reply-To: <YZPA+gSsGWI6+xBP@work>
On Tue, Nov 16, 2021 at 02:32:26PM +0000, Yifeng Li wrote:
> Like other SATA controller chips in the Marvell 88SE91xx series, the
> Marvell 88SE9125 has the same DMA requester ID hardware bug that prevents
> it from working under IOMMU. This patch adds its device ID 0x9125 to the
> Function 1 DMA alias quirk list.
Btw, do we need to prevent vfio assignment for all devices with this
quirk?
next parent reply other threads:[~2021-11-17 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YZPA+gSsGWI6+xBP@work>
2021-11-17 10:12 ` Christoph Hellwig [this message]
2021-11-17 14:15 ` [PATCH v2] PCI: Add func1 DMA quirk for Marvell 88SE9125 SATA controller Alex Williamson
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=YZTVdOlEbMb0tv59@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tomli@tomli.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 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).