From: Robert Hancock <hancockrwd@gmail.com>
To: Tejun Heo <tj@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bad DMA from Marvell 9230
Date: Fri, 04 Apr 2014 20:35:03 -0600 [thread overview]
Message-ID: <533F6BD7.4000301@gmail.com> (raw)
In-Reply-To: <20140327151915.GF18503@htj.dyndns.org>
On 27/03/14 09:19 AM, Tejun Heo wrote:
> On Thu, Mar 27, 2014 at 05:57:37PM +1100, Benjamin Herrenschmidt wrote:
>> I've contacted Marvell, but I was wondering if anybody here had already
>> experienced something similar or has an idea of what else the chip
>> might be doing wrong so we can try to find a workaround ?
>
> No idea. First time to hear such problem. :(
>
There are other Marvell controllers that do DMA requests from the wrong
PCI function ID and cause IOMMU issues, so it seems like testing on such
systems (or just validating the DMA transactions done by the controller
by some other means) isn't something that Marvell likes to do.
Presumably reading from address 0 is normally fine without an IOMMU, so
this problem wouldn't be noticed otherwise.
next prev parent reply other threads:[~2014-04-05 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 6:57 Bad DMA from Marvell 9230 Benjamin Herrenschmidt
2014-03-27 15:19 ` Tejun Heo
2014-04-05 2:35 ` Robert Hancock [this message]
2014-05-30 7:06 ` Jérôme Carretero
2014-05-30 10:37 ` Benjamin Herrenschmidt
2014-05-30 13:58 ` Jérôme Carretero
2014-05-30 14:13 ` Roger Heflin
2014-05-30 15:14 ` Jérôme Carretero
2014-05-30 21:06 ` Benjamin Herrenschmidt
2014-05-30 23:08 ` Roger Heflin
2014-05-30 20:59 ` Benjamin Herrenschmidt
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=533F6BD7.4000301@gmail.com \
--to=hancockrwd@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).