05.02.2013 Views

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Application Level Memory Model<br />

Example A3-2 to Example A3-4 describe the three possible ways of implementing a system with three<br />

levels of cache, L1 to L3. L1 is the level closest to the processor, see Memory hierarchy on page A3-52.<br />

Example A3-2 Implementation with two inner <strong>and</strong> one outer cache levels<br />

Implement the three levels of cache in the system, L1 to L3, with:<br />

the Inner cacheability attribute applied to L1 <strong>and</strong> L2 cache<br />

the Outer cacheability attribute applied to L3 cache.<br />

Example A3-3 Implementation with three inner <strong>and</strong> no outer cache levels<br />

Implement the three levels of cache in the system, L1 to L3, with the Inner cacheability attribute applied to<br />

L1, L2, <strong>and</strong> L3 cache. Do not use the Outer cacheability attribute.<br />

Example A3-4 Implementation with one inner <strong>and</strong> two outer cache levels<br />

Implement the three levels of cache in the system, L1 to L3, with:<br />

the Inner cacheability attribute applied to L1 cache<br />

the Outer cacheability attribute applied to L2 <strong>and</strong> L3 cache.<br />

A3.5.5 Device memory<br />

The Device memory type attribute defines memory locations where an access to the location can cause side<br />

effects, or where the value returned for a load can vary depending on the number of loads performed.<br />

Memory-mapped peripherals <strong>and</strong> I/O locations are examples of memory regions normally marked as being<br />

Device memory.<br />

For explicit accesses from the processor to memory marked as Device:<br />

all accesses occur at their program size<br />

the number of accesses is the number specified by the program.<br />

An implementation must not repeat an access to a Device memory location if the program has only one<br />

access to that location. In other words, accesses to Device memory locations are not restartable.<br />

The architecture does not permit speculative accesses to memory marked as Device.<br />

The architecture permits an Advanced SIMD element or structure load instruction to access bytes in Device<br />

memory that are not explicitly accessed by the instruction, provided the bytes accessed are within a 16-byte<br />

window, aligned to 16-bytes, that contains at least one byte that is explicitly accessed by the instruction.<br />

Address locations marked as Device are never held in a cache.<br />

<strong>ARM</strong> DDI 0406B Copyright © 1996-1998, 2000, 2004-2008 <strong>ARM</strong> Limited. All rights reserved. A3-33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!