From: Christoph Hellwig <hch@infradead.org>
To: Pankaj Suryawanshi <pankajssuryawanshi@gmail.com>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@kernel.org>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
iommu@lists.linux-foundation.org
Subject: Re: DMA-API attr - DMA_ATTR_NO_KERNEL_MAPPING
Date: Wed, 26 Jun 2019 10:51:31 -0700 [thread overview]
Message-ID: <20190626175131.GA17250@infradead.org> (raw)
In-Reply-To: <CACDBo55GfomD4yAJ1qaOvdm8EQaD-28=etsRHb39goh+5VAeqw@mail.gmail.com>
On Wed, Jun 26, 2019 at 10:12:45PM +0530, Pankaj Suryawanshi wrote:
> [CC: linux kernel and Vlastimil Babka]
The right list is the list for the DMA mapping subsystem, which is
iommu@lists.linux-foundation.org. I've also added that.
> > I am writing driver in which I used DMA_ATTR_NO_KERNEL_MAPPING attribute
> > for cma allocation using dma_alloc_attr(), as per kernel docs
> > https://www.kernel.org/doc/Documentation/DMA-attributes.txt buffers
> > allocated with this attribute can be only passed to user space by calling
> > dma_mmap_attrs().
> >
> > how can I mapped in kernel space (after dma_alloc_attr with
> > DMA_ATTR_NO_KERNEL_MAPPING ) ?
You can't. And that is the whole point of that API.
next prev parent reply other threads:[~2019-06-26 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:41 Pankaj Suryawanshi
2019-06-26 16:42 ` Pankaj Suryawanshi
2019-06-26 17:51 ` Christoph Hellwig [this message]
2019-06-28 16:29 ` Pankaj Suryawanshi
2019-07-01 14:09 ` Robin Murphy
2019-07-01 17:47 ` Pankaj Suryawanshi
2019-07-01 17:52 ` Pankaj Suryawanshi
2019-07-01 17:54 ` Robin Murphy
2019-07-01 18:07 ` Pankaj Suryawanshi
2019-07-01 18:36 ` Pankaj Suryawanshi
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=20190626175131.GA17250@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pankajssuryawanshi@gmail.com \
--cc=vbabka@suse.cz \
/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