From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Hemanth V <hemanthv@ti.com>,
pierre@ossman.eu, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Highmem issues with MMC filesystem
Date: Thu, 18 Mar 2010 09:23:52 +0000 [thread overview]
Message-ID: <20100318092352.GD8267@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1003171050160.31128@xanadu.home>
On Wed, Mar 17, 2010 at 10:58:48AM -0400, Nicolas Pitre wrote:
> On Wed, 17 Mar 2010, Hemanth V wrote:
> > Nicolas, Russel are there any more details available which might help
> > in investigating this further.
>
> The only conclusion I came to so far is that ARMv5 where highmem works
> just fine in all cases has VIVT cache whereas ARMv6 has VIPT cache.
> And the problem with VIPT caches occurs when direct DMA is involved,
> otherwise there is no problem if PIO or NFS is used. Sprinkling some
> flush_cache_all() in a few places makes things work, but this is not a
> satisfactory solution.
This sounds like the problem we had with the DMA API. Since that's now
fixed, there shouldn't be a problem with the latest (-rc) kernels, or
a kernel with my old streaming DMA patches applied.
next prev parent reply other threads:[~2010-03-18 9:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 13:40 Highmem issues with MMC filesystem Hemanth V
2010-03-17 13:49 ` Nicolas Pitre
2010-03-17 14:40 ` Hemanth V
2010-03-17 14:58 ` Nicolas Pitre
2010-03-18 9:23 ` Russell King - ARM Linux [this message]
2010-03-18 11:15 ` saeed bishara
2010-03-18 11:24 ` Russell King - ARM Linux
2010-03-18 13:20 ` Nicolas Pitre
2010-03-18 13:30 ` Shilimkar, Santosh
2010-03-18 14:19 ` Russell King - ARM Linux
2010-03-18 14:41 ` Hemanth V
2010-03-18 16:17 ` Nicolas Pitre
2010-03-18 17:51 ` Russell King - ARM Linux
2010-03-18 19:24 ` Nicolas Pitre
2010-03-19 1:55 ` Jamie Lokier
2010-03-19 13:17 ` Nicolas Pitre
2010-03-19 13:27 ` Russell King - ARM Linux
2010-03-19 17:59 ` Nicolas Pitre
2010-03-19 18:26 ` Catalin Marinas
2010-03-19 18:56 ` Nicolas Pitre
2010-03-19 14:28 ` Hemanth V
2010-03-19 14:36 ` Shilimkar, Santosh
2010-03-19 14:45 ` Russell King - ARM Linux
2010-03-19 14:41 ` Catalin Marinas
2010-03-19 14:46 ` Russell King - ARM Linux
2010-03-19 14:52 ` Catalin Marinas
2010-03-19 14:54 ` Russell King - ARM Linux
2010-03-19 16:46 ` Catalin Marinas
2010-03-19 16:52 ` Russell King - ARM Linux
2010-03-19 17:47 ` Nicolas Pitre
2010-03-19 18:27 ` Nicolas Pitre
2010-03-19 18:38 ` Russell King - ARM Linux
2010-03-19 18:51 ` Nicolas Pitre
2010-03-22 11:45 ` Russell King - ARM Linux
2010-03-22 12:36 ` Nicolas Pitre
2010-03-19 20:14 ` Nicolas Pitre
2010-03-22 9:05 ` Hemanth V
2010-03-22 12:50 ` Nicolas Pitre
2010-03-18 13:42 ` saeed bishara
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=20100318092352.GD8267@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=hemanthv@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pierre@ossman.eu \
/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).