From: ning.n.jiang@gmail.com (Ning Jiang)
To: linux-arm-kernel@lists.infradead.org
Subject: Is it too strict for VIPT cache flushing in flush_cache_[mm|range]?
Date: Tue, 23 Oct 2012 10:55:23 +0800 [thread overview]
Message-ID: <CAH3Oq6Sd7OTyntiOpbiUBTcuXMNfjq17eACkN=f=91wG7BPJEw@mail.gmail.com> (raw)
In-Reply-To: <CAH3Oq6SRSeXfrW56j=brCOE5PJgfw31rOSCfm-CgJwGaiJYRsw@mail.gmail.com>
2012/10/16 Ning Jiang <ning.n.jiang@gmail.com>:
> I found that the implementation of flush_cache_mm() and
> flush_cache_range() for VIPT aliasing case is to clean + invalidate
> whole data cache, but for a physically tagged cache, why do we need to
> perform such an operation? Is it because we'll have aliasing issue?
>
> I searched through the git history and found it is brought in the
> commit "d7b6b358" "[ARM] Fix ARMv6 VIPT cache >= 32K", before that,
> there is indeed no flushing, why we "Fix ARMv6 VIPT cache >= 32K"?
>
> Sorry for asking such stupid question, but it really confuses me ;-)
>
> Thanks,
> Ning
Maybe someone in the mail list can give an answer ;-)
parent reply other threads:[~2012-10-23 2:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAH3Oq6SRSeXfrW56j=brCOE5PJgfw31rOSCfm-CgJwGaiJYRsw@mail.gmail.com>]
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='CAH3Oq6Sd7OTyntiOpbiUBTcuXMNfjq17eACkN=f=91wG7BPJEw@mail.gmail.com' \
--to=ning.n.jiang@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).