From: ananaza@iki.fi (Antti Miettinen)
To: linux-arm-kernel@lists.infradead.org
Subject: L1 & L2 cache flush sequence on CortexA5 MPcore w.r.t low power modes
Date: Tue, 24 Dec 2013 19:52:48 +0200 [thread overview]
Message-ID: <87ha9yqgpb.fsf@iki.fi> (raw)
In-Reply-To: <20120514162150.GA4654@e102568-lin.cambridge.arm.com> (Lorenzo Pieralisi's message of "Mon, 14 May 2012 17:21:50 +0100")
Sorry to still bring up an old thread, but this still bothers me..
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> writes:
> [..] dirty cache lines can be migrated across
> processors caches. [..]
What are the conditions under which this can happen? Which CPUs in
reality migrate dirty lines between caches? And C==0 does prevent
migrations as well as local allocations?
--Antti
next prev parent reply other threads:[~2013-12-24 17:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 7:03 L1 & L2 cache flush sequence on CortexA5 MPcore w.r.t low power modes Murali N
2012-05-14 15:50 ` Lorenzo Pieralisi
2012-05-14 15:58 ` Russell King - ARM Linux
2012-05-14 16:21 ` Lorenzo Pieralisi
2012-05-14 16:39 ` Russell King - ARM Linux
2012-05-14 17:15 ` Lorenzo Pieralisi
2012-05-15 9:25 ` Murali N
2012-05-15 9:40 ` Russell King - ARM Linux
2012-05-15 10:09 ` Lorenzo Pieralisi
2012-05-15 10:15 ` Russell King - ARM Linux
2012-05-15 16:28 ` Lorenzo Pieralisi
2012-05-15 16:36 ` Russell King - ARM Linux
2012-05-15 17:05 ` Lorenzo Pieralisi
2012-09-19 8:55 ` Antti P Miettinen
2012-09-20 9:54 ` Lorenzo Pieralisi
2012-09-20 21:17 ` Antti P Miettinen
2012-09-23 21:32 ` Antti P Miettinen
2013-02-22 9:04 ` Antti P Miettinen
2013-02-22 9:39 ` Lorenzo Pieralisi
2013-02-23 20:41 ` Antti P Miettinen
2013-02-25 13:36 ` Lorenzo Pieralisi
2012-05-15 18:17 ` Will Deacon
2012-05-17 5:01 ` Murali N
2012-05-17 7:30 ` Shilimkar, Santosh
2013-12-24 17:52 ` Antti Miettinen [this message]
2014-01-06 12:43 ` Lorenzo Pieralisi
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=87ha9yqgpb.fsf@iki.fi \
--to=ananaza@iki.fi \
--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.