From: hzpeterchen@gmail.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: Why flush_cache_all() not including flushing L2 cache if the system has L2 cache?
Date: Tue, 03 Nov 2009 11:10:41 +0800 [thread overview]
Message-ID: <4AEF9F31.5000008@gmail.com> (raw)
In-Reply-To: <20091102110007.GC1133@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Mon, Nov 02, 2009 at 10:32:13AM +0800, Peter Chen wrote:
>> I met a problem if the address is first used by cachable, then
>> uncachable. After that, the address will be filled with cachable value
>> after that L2 cache line is evicted.
>
> What _exactly_ are you trying to do? Why are you apparantly mapping
> something in as cacheable, and then making it uncacheable?
>
This is 3rd party released code
This problem happens at device driver wants to alloc uncachable memory,
but it doesn't alloc it using dma_ API.
--
Best regards,
Peter Chen
prev parent reply other threads:[~2009-11-03 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 2:32 Why flush_cache_all() not including flushing L2 cache if the system has L2 cache? Peter Chen
2009-11-02 3:42 ` Eric Miao
2009-11-02 10:43 ` Peter Chen
2009-11-02 11:00 ` Russell King - ARM Linux
2009-11-03 3:10 ` Peter Chen [this message]
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=4AEF9F31.5000008@gmail.com \
--to=hzpeterchen@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 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).