From: Christoph Hellwig <hch@lst.de>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
Gavin Li <git@thegavinli.com>,
gavinli@thegavinli.com, Christoph Hellwig <hch@lst.de>,
"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 18:39:39 +0100 [thread overview]
Message-ID: <20201028173939.GB10317@lst.de> (raw)
In-Reply-To: <CAFCwf10HzngDA17sLxYRY_z1QcPp6NE+HYKnAzm_fEuN6FzmGA@mail.gmail.com>
On Wed, Oct 28, 2020 at 07:38:04PM +0200, Oded Gabbay wrote:
> > > 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 ?
> >
> > What are the kernel log messages that gaving has mentioned?
>
> This one:
> 11:22:43 [Wed Oct 28 11:22:34 2020] x86/PAT: synapse_tests:29265 map
> pfn RAM range req uncached-minus for [mem 0xe6236b000-0xe6236bfff],
> got write-back
>
> Thousands of the same message with different addresses of course.
What kernel version is this on? And what is the test case?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-10-28 17: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
2020-10-28 17:31 ` Christoph Hellwig
2020-10-28 17:38 ` Oded Gabbay
2020-10-28 17:39 ` Christoph Hellwig [this message]
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=20201028173939.GB10317@lst.de \
--to=hch@lst.de \
--cc=gavinli@thegavinli.com \
--cc=git@thegavinli.com \
--cc=iommu@lists.linux-foundation.org \
--cc=oded.gabbay@gmail.com \
--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).