From: Oded Gabbay <oded.gabbay@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
Gavin Li <git@thegavinli.com>,
gavinli@thegavinli.com,
"list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>,
" <iommu@lists.linux-foundation.org>
Subject: Re: [PATCH v1] dma-mapping: normal memory for mmap() on coherent architectures
Date: Wed, 28 Oct 2020 13:39:17 +0200 [thread overview]
Message-ID: <CAFCwf122xMQJgqN9qJ1SXAHkVqg4GoNDC+NvXuj=-owXB=AO0A@mail.gmail.com> (raw)
In-Reply-To: <20190803062333.GC29348@lst.de>
On Sat, Aug 3, 2019 at 9:26 AM Christoph Hellwig <hch@lst.de> wrote:
>
> See the discussion at:
>
> https://lists.linuxfoundation.org/pipermail/iommu/2019-August/037716.html
>
> Just curious, what driver do you use that uses dma_mmap_coherent on
> x86?
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
Hi Christoph,
In the habanalabs driver we have moved to use dma_mmap_coherent (to
match dma_alloc_coherent - see commit
https://lkml.org/lkml/2020/8/29/252)
Since then, we are plagued by the kernel log message that gavin has
mentioned, as we are mostly running in our C/I environment with 5.4.
I wondered if you know if there was any fix to that in the more recent kernels ?
If not, can I help to fix that ?
Thanks,
oded
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-10-28 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 18:07 [PATCH v1] dma-mapping: normal memory for mmap() on coherent architectures gavinli
2019-08-03 6:23 ` Christoph Hellwig
2019-08-03 6:35 ` Gavin Li
2019-08-03 6:39 ` Christoph Hellwig
2020-10-28 11:39 ` Oded Gabbay [this message]
2020-10-28 17:31 ` Christoph Hellwig
2020-10-28 17:38 ` Oded Gabbay
2020-10-28 17:39 ` Christoph Hellwig
2020-10-28 19:33 ` Oded Gabbay
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='CAFCwf122xMQJgqN9qJ1SXAHkVqg4GoNDC+NvXuj=-owXB=AO0A@mail.gmail.com' \
--to=oded.gabbay@gmail.com \
--cc=gavinli@thegavinli.com \
--cc=git@thegavinli.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=robin.murphy@arm.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).