From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: setup_mm_for_reboot(): use flush_cache_louis()
Date: Wed, 7 Nov 2012 09:51:06 +0000 [thread overview]
Message-ID: <20121107095106.GA23305@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121106220458.GP28327@n2100.arm.linux.org.uk>
On Tue, Nov 06, 2012 at 10:04:58PM +0000, Russell King - ARM Linux wrote:
> On Tue, Nov 06, 2012 at 04:12:27PM -0500, Nicolas Pitre wrote:
> >
> > ... instead of flush_cache_all(). The later unconditionally flushes
> > the L2 cache on ARMv7 architectures such as Cortex A15 and A7 which
> > is costly and unnecessary in some scenarios where setup_mm_for_reboot()
> > is used. If L2 has to be flushed as well, it should already be done
> > separately on other architectures anyway.
>
> Why does the cost at reboot count? It's a relatively slow operation as
> it is anyway, because you have to wait for the system to shut down, call
> the boot loader, etc.
>
> However, the opposite argument is that the state of the L2 _shouldn't_
> matter - except for one small little detail. Dirty data, which could
> get evicted and overwrite something that matters. Generally there won't
> be any dirty data in the L2 cache on normal boot, so this is a situation
> which boot loaders probably don't expect.
Wouldn't the L2 flush in this case be included with the code that turns off
caching? For reboot, that's currently done in __sort_restart -- the cache
flush in setup_mm_for_reboot is just to ensure that the idmap tables are
visible to the hardware walker iirc.
Will
next prev parent reply other threads:[~2012-11-07 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 21:12 [PATCH] ARM: setup_mm_for_reboot(): use flush_cache_louis() Nicolas Pitre
2012-11-06 21:41 ` Will Deacon
2012-11-06 21:57 ` Santosh Shilimkar
2012-11-07 9:47 ` Lorenzo Pieralisi
2012-11-07 14:16 ` Santosh Shilimkar
2012-11-06 22:04 ` Russell King - ARM Linux
2012-11-06 22:53 ` Nicolas Pitre
2012-11-07 9:51 ` Russell King - ARM Linux
2012-11-07 9:51 ` Will Deacon [this message]
2012-11-07 9:56 ` Russell King - ARM Linux
2012-11-07 10:08 ` Will Deacon
2012-11-07 18:03 ` Nicolas Pitre
2012-11-07 18:41 ` Will Deacon
2012-11-07 20:10 ` Nicolas Pitre
2012-11-08 16:26 ` Will Deacon
2012-11-08 18:56 ` Nicolas Pitre
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=20121107095106.GA23305@mudshark.cambridge.arm.com \
--to=will.deacon@arm.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).