From: anfei.zhou@gmail.com (anfei)
To: linux-arm-kernel@lists.infradead.org
Subject: flush_dcache_page does too much?
Date: Mon, 18 Jan 2010 22:53:07 +0800 [thread overview]
Message-ID: <20100118145307.GA14306@desktop> (raw)
In-Reply-To: <20100118144418.GE2695@n2100.arm.linux.org.uk>
On Mon, Jan 18, 2010 at 02:44:18PM +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 18, 2010 at 10:15:30PM +0800, anfei wrote:
> > On Mon, Jan 18, 2010 at 02:00:05PM +0000, Russell King - ARM Linux wrote:
> > > On Mon, Jan 18, 2010 at 09:54:31PM +0800, anfei wrote:
> > > > Do you mean this implementation can ensure the coherence between write
> > > > and shared mmapings? But it's easy to reproduce the alias problem by
> > > > this simple testcase (w/o error handler) on omap2430 with VIPT cache:
> > >
> > > Your program doesn't do anything to identify any problem. You don't
> > > even say _what_ problem you see with this program.
> > >
> > Sorry for that.
> >
> > > If you have a specific case which fails, please show the problem, please
> > > describe exactly the behaviour that you see, and what you expect to see.
>
> Are you using a write allocate cache?
I'm not sure, I can get more information tomorrow.
next prev parent reply other threads:[~2010-01-18 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:13 flush_dcache_page does too much? anfei
2010-01-18 13:33 ` Russell King - ARM Linux
2010-01-18 13:54 ` anfei
2010-01-18 14:00 ` Russell King - ARM Linux
2010-01-18 14:15 ` anfei
2010-01-18 14:44 ` Russell King - ARM Linux
2010-01-18 14:53 ` anfei [this message]
2010-01-18 14:57 ` anfei
2010-01-18 15:01 ` Russell King - ARM Linux
2010-01-19 0:16 ` anfei
2010-01-19 13:05 ` anfei
2010-01-19 17:44 ` Russell King - ARM Linux
2010-01-19 18:33 ` Jamie Lokier
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=20100118145307.GA14306@desktop \
--to=anfei.zhou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.