From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: REGRESSION: iommu fails to take address limit into account
Date: Fri, 25 May 2018 11:34:35 +0100 [thread overview]
Message-ID: <31cd3850-fb61-2d5d-7394-66d84d46b63e@arm.com> (raw)
In-Reply-To: <CAKv+Gu9HoV-V4nj3j6VPzwGz3Z-G4G7zUQcUHufQ6Rdkk8-VNQ@mail.gmail.com>
Hi Ard,
On 25/05/18 10:48, Ard Biesheuvel wrote:
> Hello all,
>
> I am looking into an issue where a platform device is wired to a
> MMU-500, and for some reason (which is under investigation) the
> platform device can not drive all address bits. I can work around this
> by limiting the DMA mask to 40 bits in the driver. However, the IORT
> table allows me to set the address limit as well, and so I was
> expecting this to be taken into account by the SMMU driver.
>
> When the iort/iommu layer sets up the DMA operations,
> iommu_dma_init_domain() is entered with the expected values:
>
> base == 0
> size == 0x100_0000_0000
>
> However, the iommu layer ends up generating IOVA addresses that have
> bits [47:40] set (which is what the MMU-500 supports). Looking closer,
> this is not surprising, given that the end_pfn variable that is
> calculated in iommu_dma_init_domain() is no longer used after Zhen's
> patch aa3ac9469c185 ("iommu/iova: Make dma_32bit_pfn implicit") was
> applied.
>
> So effectively, this is a regression, and I would like your help
> figuring out how to go about fixing this.
Note that the size passed to iommu_dma_init_domain() has *never* been
any kind of enforced limit, so nothing is actually regressing here. If
the device master interface is natively >40 bits wide (such that the
driver would expect to set a larger DMA mask) and the restriction is
purely in the interconnect between device and SMMU, then that's the case
which has always been broken.
I do have a long-standing plan of attack for fixing the underlying issue
(of actually enforcing any dma mask restriction described by IORT or DT
"dma-ranges"), but it's one of those things that's tied to a whole bunch
of other rework and fixes in order to be viable. I'm about to go off on
holiday for a while but I should hopefully have the bandwidth to start
looking at this seriously once I get back (frankly it's been getting
bumped down my to-do list for far too long now...)
Robin.
next prev parent reply other threads:[~2018-05-25 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 9:48 REGRESSION: iommu fails to take address limit into account Ard Biesheuvel
2018-05-25 10:34 ` Robin Murphy [this message]
2018-05-25 10:35 ` Ard Biesheuvel
2018-05-25 10:49 ` Robin Murphy
2018-05-25 10:52 ` Ard Biesheuvel
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=31cd3850-fb61-2d5d-7394-66d84d46b63e@arm.com \
--to=robin.murphy@arm.com \
--cc=linux-arm-kernel@lists.infradead.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