From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Query: ARM Cortex A9: Is invalidating L1 data cache mandatory before usage
Date: Sun, 18 Apr 2010 16:56:13 +0100 [thread overview]
Message-ID: <20100418155613.GC15452@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <j2nb0a4007f1004180843qdc3fc56bl418010257119d8e9@mail.gmail.com>
On Sun, Apr 18, 2010 at 09:13:55PM +0530, shiraz hashim wrote:
> On Sat, Apr 17, 2010 at 11:44 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Sat, Apr 17, 2010 at 03:26:13PM +0530, Shiraz HASHIM wrote:
> >> Hello,
> >>
> >> I am trying to port Linux on ARM Cortex A9 based platform and what
> >> I see is that if I don't invalidate the data cache before enabling
> >> and using it (in arch/arm/boot/compressed/head.S) the system crashes.
> >>
> >> I need to do the same for second core before calling secondary_startup.
> >>
> >> Is it normal? Why then other platforms (cortex A9 based) are not doing
> >> this. What am I missing?
> >
> > Yes, it's required. ?See:
> >
> > http://www.arm.linux.org.uk/developer/booting.php
>
> The only thing which is confusing me is that do we need to invalidate
> the data cache, even if it is disabled in bootloader.
If you don't, the cache will be in an undefined state when it is enabled,
which in turn means that when you enable it, you don't know whether the
instructions you're going to execute come from the cache or from the
memory - and the two may be different.
prev parent reply other threads:[~2010-04-18 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 9:56 Query: ARM Cortex A9: Is invalidating L1 data cache mandatory before usage Shiraz HASHIM
2010-04-17 10:07 ` Shilimkar, Santosh
2010-04-17 10:28 ` Shiraz HASHIM
2010-04-17 18:14 ` Russell King - ARM Linux
2010-04-18 14:35 ` shiraz hashim
2010-04-18 15:43 ` shiraz hashim
2010-04-18 15:56 ` Russell King - ARM Linux [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=20100418155613.GC15452@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).