From: Christoph Hellwig <hch@infradead.org>
To: Richard Weinberger <richard@nod.at>
Cc: Christoph Hellwig <hch@infradead.org>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: UBIFS with dma on 4.6 kernel is not working
Date: Fri, 21 Oct 2016 06:15:05 -0700 [thread overview]
Message-ID: <20161021131505.GA25942@infradead.org> (raw)
In-Reply-To: <c0b0098d-3a68-3a4a-0b7e-a1d95dd4aafc@nod.at>
On Fri, Oct 21, 2016 at 03:07:57PM +0200, Richard Weinberger wrote:
> Hmm, thought this is still problematic on VIVT architectures.
> Boris tried to provide a solution for that some time ago:
> http://www.spinics.net/lists/arm-kernel/msg494025.html
Things have been working fine for approx 10 years when using
flush_kernel_vmap_range before doing I/O using the physical addresses and
then invalidate_kernel_vmap_range when completing the I/O and going back
to using the virtual mapping for XFS.
Of course all this assumes at least the higher level that did the
vm_map_ram operation knows about this dance between virtually mapped and
physiscal addresses.
next prev parent reply other threads:[~2016-10-21 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:21 UBIFS with dma on 4.6 kernel is not working Naga Sureshkumar Relli
2016-10-21 9:29 ` Richard Weinberger
2016-10-21 11:57 ` Cyrille Pitchen
2016-10-21 12:53 ` Christoph Hellwig
2016-10-21 13:07 ` Richard Weinberger
2016-10-21 13:15 ` Christoph Hellwig [this message]
2016-10-24 7:08 ` Richard Weinberger
2016-10-25 5:52 ` Naga Sureshkumar Relli
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=20161021131505.GA25942@infradead.org \
--to=hch@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michal.simek@xilinx.com \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=punnaia@xilinx.com \
--cc=richard@nod.at \
/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