From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: madalin.bucur@nxp.com, netdev@vger.kernel.org,
roy.pledge@nxp.com, linux-kernel@vger.kernel.org,
leoyang.li@nxp.com, Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, camelia.groza@nxp.com,
linuxppc-dev@lists.ozlabs.org, David Miller <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement
Date: Fri, 31 May 2019 10:08:04 -0700 [thread overview]
Message-ID: <20190531170804.GA12211@infradead.org> (raw)
In-Reply-To: <37406608-df48-c7a0-6975-4b4ad408ba36@arm.com>
On Fri, May 31, 2019 at 06:03:30PM +0100, Robin Murphy wrote:
> > The thing needs to be completely redone as it abuses parts of the
> > iommu API in a completely unacceptable way.
>
> `git grep iommu_iova_to_phys drivers/{crypto,gpu,net}`
>
> :(
>
> I guess one alternative is for the offending drivers to maintain their own
> lookup tables of mapped DMA addresses - I think at least some of these
> things allow storing some kind of token in a descriptor, which even if it's
> not big enough for a virtual address might be sufficient for an index.
Well, we'll at least need DMA API wrappers that work on the dma addr
only and hide this madness underneath. And then tell if an given device
supports this and fail the probe otherwise.
next prev parent reply other threads:[~2019-05-31 17:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 14:19 [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement laurentiu.tudor
2019-05-30 14:19 ` [PATCH v3 1/6] fsl/fman: don't touch liodn base regs reserved on non-PAMU SoCs laurentiu.tudor
2019-05-30 14:19 ` [PATCH v3 2/6] fsl/fman: add API to get the device behind a fman port laurentiu.tudor
2019-05-30 14:19 ` [PATCH v3 3/6] dpaa_eth: defer probing after qbman laurentiu.tudor
2019-05-30 14:19 ` [PATCH v3 4/6] dpaa_eth: base dma mappings on the fman rx port laurentiu.tudor
2019-05-30 14:19 ` [PATCH v3 5/6] dpaa_eth: fix iova handling for contiguous frames laurentiu.tudor
2019-05-31 16:32 ` Christoph Hellwig
2019-05-31 16:53 ` Laurentiu Tudor
2019-05-31 16:55 ` Christoph Hellwig
2019-05-31 17:01 ` Laurentiu Tudor
2019-05-30 14:19 ` [PATCH v3 6/6] dpaa_eth: fix iova handling for sg frames laurentiu.tudor
2019-05-30 22:08 ` [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement David Miller
2019-05-30 22:14 ` Li Yang
2019-05-31 13:09 ` Laurentiu Tudor
2019-05-31 16:33 ` Christoph Hellwig
2019-05-31 17:03 ` Robin Murphy
2019-05-31 17:08 ` Christoph Hellwig [this message]
2019-05-31 17:45 ` Robin Murphy
2019-05-31 17:46 ` Christoph Hellwig
2019-05-31 16:15 ` Andreas Färber
2019-05-31 16:46 ` Laurentiu Tudor
2019-05-31 17:03 ` Andreas Färber
2019-05-31 17:32 ` Laurentiu Tudor
2019-06-03 16:42 ` Andreas Färber
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=20190531170804.GA12211@infradead.org \
--to=hch@infradead.org \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=iommu@lists.linux-foundation.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=roy.pledge@nxp.com \
/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).