From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"V, Hemanth" <hemanthv@ti.com>,
saeed bishara <saeed.bishara@gmail.com>,
"pierre@ossman.eu" <pierre@ossman.eu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Highmem issues with MMC filesystem
Date: Thu, 18 Mar 2010 14:19:30 +0000 [thread overview]
Message-ID: <20100318141930.GF19544@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C489CB4A@dbde02.ent.ti.com>
On Thu, Mar 18, 2010 at 07:00:06PM +0530, Shilimkar, Santosh wrote:
> Or could it be that there is appropriate cacheflush happening but data gets
> stuck in CPU writebuffers instead of reaching to main memory. In this case
> too DMA won't see the contents and a barrier (dsb) is necessary to ensure
> that write buffer is drained before DMA takes over the buffer.
That would imply that the data on the device is becoming corrupted.
What exactly is the problem that we're discussing? Is it that the data
on the block device is becoming corrupted, or is the data being read off
the block device corrupted?
next prev parent reply other threads:[~2010-03-18 14:19 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
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 [this message]
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=20100318141930.GF19544@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 \
--cc=saeed.bishara@gmail.com \
--cc=santosh.shilimkar@ti.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).