From: Andrew Cooks <acooks@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: [Bug 42679] New: DMA Read on Marvell 88SE9128 fails when Intel's IOMMU is on
Date: Fri, 11 May 2012 09:18:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20120511T103733-249@post.gmane.org> (raw)
In-Reply-To: op.v8w77qlcc3q55a@localhost
On Tue, 31 Jan 2012, Chris Wright <chrisw <at> sous-sol.org> wrote:
>> >Well, the lspci dump in the bugzilla report doesn't show a device
>> >w/BDF=0b:00.1;
>> >so, if the SATA device (which is 0b:00.0) is spitting out 0b:00.1
>> >as the source
>> >of any of its DMA packets, the IOMMU will fault on it, since
>> >0b:00.1 didn't
>> >request DMA mappings (0b:00.0 did).
>> >I semi-recall someone else reporting this 'feature' on this list.
>> >Wonder if pci-quirk has to filter this case (0b:00.0 on this system
>> means
>> >map for 0b:00.0 & 0b:00.1 -- ick!)
>> >
It would seem that there are multiple Marvell 88SE91xx controllers that use
xx:00.0 and xx:00.1 and only report xx:00.0. I've got the same issue on a
88SE9172 and can't simply move to a different controller without buying more
hardware. Besides, this should work ;)
Is this an issue of a missing entry in some ACPI table?
It's been suggested that a pci-quirk could handle this by mapping both the .0
and .1 entry when the .0 shows up, but what isn't clear to me is where this
should be done. Is it a case of setting the "present" bit for an existing
context entry, or adding an additional context entry?
AC.
prev parent reply other threads:[~2012-05-11 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42679-27@https.bugzilla.kernel.org/>
[not found] ` <bug-42679-27-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2012-01-30 20:59 ` [Bug 42679] New: DMA Read on Marvell 88SE9128 fails when Intel's IOMMU is on Andrew Morton
[not found] ` <20120130125934.7971c815.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2012-01-30 21:41 ` Don Dutile
2012-01-30 22:13 ` Paweł Żak
2012-01-30 23:32 ` Chris Wright
2012-01-30 23:44 ` Paweł Żak
2012-05-11 9:18 ` Andrew Cooks [this message]
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=loom.20120511T103733-249@post.gmane.org \
--to=acooks@gmail.com \
--cc=linux-ide@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