From: Christoph Hellwig <hch@lst.de>
To: Ajay kumar <ajaynumb@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Shaik Ameer Basha <shaik.samsung@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
linux-mm@kvack.org, Joerg Roedel <joro@8bytes.org>,
Rob Clark <robdclark@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
jean-philippe@linaro.org, will@kernel.org,
baolu.lu@linux.intel.com,
Shaik Ameer Basha <shaik.ameer@samsung.com>
Subject: Re: IOVA allocation dependency between firmware buffer and remaining buffers
Date: Wed, 23 Sep 2020 15:47:56 +0200 [thread overview]
Message-ID: <20200923134756.GA10902@lst.de> (raw)
In-Reply-To: <CAEC9eQMoqYBU_9H9QoAwwayR8u2MK4aMDvTocOqrPRK3cuVeHw@mail.gmail.com>
On Wed, Sep 23, 2020 at 01:15:33PM +0530, Ajay kumar wrote:
> Hello all,
>
> We pretty much tried to solve the same issue here with a new API in DMA-IOMMU:
> https://lore.kernel.org/linux-iommu/20200811054912.GA301@infradead.org/T/
>
> Christopher- the user part would be MFC devices on exynos platforms
I still think we:
a) need to wire it up through the DMA API with an ops vector,
and an error for devices not using dma-iommu
b) submit it together with an actual users (like the series from Marek)
next prev parent reply other threads:[~2020-09-23 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 15:54 IOVA allocation dependency between firmware buffer and remaining buffers Ajay kumar
2020-04-24 15:04 ` Ajay kumar
2020-04-24 15:29 ` Robin Murphy
2020-04-24 16:15 ` Shaik Ameer Basha
2020-09-23 6:48 ` Marek Szyprowski
2020-09-23 6:58 ` Christoph Hellwig
2020-09-23 7:45 ` Ajay kumar
2020-09-23 13:47 ` Christoph Hellwig [this message]
2020-09-23 8:25 ` Ajay Kumar
2020-09-24 8:28 ` Joerg Roedel
2020-09-24 8:46 ` Marek Szyprowski
2020-09-24 10:16 ` Thierry Reding
2020-09-24 10:40 ` Robin Murphy
2020-09-24 10:47 ` Marek Szyprowski
2020-09-24 11:06 ` Robin Murphy
2020-09-24 14:14 ` Shaik Ameer Basha
2020-09-28 6:52 ` Marek Szyprowski
2020-09-24 10:41 ` Marek Szyprowski
2020-09-24 14:33 ` Thierry Reding
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=20200923134756.GA10902@lst.de \
--to=hch@lst.de \
--cc=ajaynumb@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=will@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).