linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: ARM Boot standard for passing device tree blob
Date: Fri, 26 Mar 2010 13:52:24 -0600	[thread overview]
Message-ID: <fa686aa41003261252u7dc31bb6nca2e77ae8feb4355@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003261435460.694@xanadu.home>

On Fri, Mar 26, 2010 at 1:30 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Fri, 26 Mar 2010, Grant Likely wrote:
>
>> On Fri, Mar 26, 2010 at 11:43 AM, Mitch Bradley <wmb@firmworks.com> wrote:
>> > Catalin Marinas wrote:
>> >> On Thu, 2010-03-25 at 21:04 +0000, Russell King - ARM Linux wrote:
>> >>> On Wed, Mar 24, 2010 at 09:11:56AM -0600, Grant Likely wrote:
>> >>>> *IRQs disabled
>> >>>> *MMU off
>> >>>> *Instruction cache either on or off
>> >>>> *Data cache turned off
>> >>>
>> >>> Would recommend saying "Data cache(s) turned off" so that L2 cache is
>> >>> included.
>> >>
>> >> There are platforms where the L2 cache is turned on by the boot monitor
>> >> (secure monitor) and Linux has no control over it (I think OMAP).
>> >
>> > What is the reason for turning off the data caches? ?Leaving all caches
>> > turned on and coherent with one another has always worked well for me at the
>> > interface from firmware to a booted program.
>>
>> Data cache off is specified in Documentation/arm/Booting in the Linux
>> source tree and I used that document as a starting point to get
>> discussion going. ?I don't have a technical argument either way.
>>
>> Russell, what is the reason for having the data cache off?
>
> At least on machines with a VIVT cache, you need to have the MMU enabled
> for the data cache to be enabled. ?That means a page table set up
> somewhere in memory, and then the kernel would need to know where that
> page table is not to overwrite it until the kernel has set its own page
> table, etc. ?This makes the booting requirements more complex for very
> little gain.
>
> So by mandating that the MMU be off (implying that the dcache has to be
> disabled too) then the kernel can set it up without restrictions.

I could change the statement to something like, "virtually tagged or
indexed data cache(s) must be off", or drop the statement entirely
since it is implied by the requirement that the MMU must be off.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2010-03-26 19:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 15:11 RFC: ARM Boot standard for passing device tree blob Grant Likely
2010-03-25 21:04 ` Russell King - ARM Linux
2010-03-25 23:40   ` David Gibson
2010-03-26  0:23     ` Jeremy Kerr
2010-03-26  3:24   ` Grant Likely
2010-03-26 13:37   ` Catalin Marinas
2010-03-26 17:43     ` Mitch Bradley
2010-03-26 18:13       ` Grant Likely
2010-03-26 19:30         ` Nicolas Pitre
2010-03-26 19:52           ` Grant Likely [this message]
2010-03-26 23:03             ` Russell King - ARM Linux
2010-03-29 11:24               ` Dave P. Martin
2010-03-30  0:26                 ` Jamie Lokier
2010-03-30 13:32                   ` Dave P. Martin
2010-03-26 23:00       ` Russell King - ARM Linux
2010-03-31  1:10       ` Ben Dooks

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=fa686aa41003261252u7dc31bb6nca2e77ae8feb4355@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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).