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.

Virtual Memory System <strong>Architecture</strong> (VMSA)<br />

— The operation generates an IMPLEMENTATION DEFINED Data Abort exception if it operates on<br />

an entry that is locked down, or might be locked down. A fault status code is provided in the<br />

CP15 c5 fault status registers for cache <strong>and</strong> TLB lockdown faults, see Table B3-11 on<br />

page B3-50 <strong>and</strong> Table B3-12 on page B3-51.<br />

Any implementation that uses an abort mechanism for entries that might be locked must:<br />

document the IMPLEMENTATION DEFINED code sequences that then performs the required operations<br />

on entries that are not locked down<br />

implement one of the other specified alternatives for the locked entries.<br />

<strong>ARM</strong> recommends that architecturally-defined operations are used wherever possible in such sequences, to<br />

minimize the number of customized operations required.<br />

In addition, if an implementation uses an abort mechanisms for entries that might be locked it must also must<br />

provide a mechanism that ensures that no TLB entries are locked.<br />

Similar rules apply to cache lockdown, see The interaction of cache lockdown with cache maintenance on<br />

page B2-18.<br />

An unlocked entry in the TLB is not guaranteed to remain in the TLB. This means that, as a side effect of a<br />

TLB maintenance operation, any unlocked entry in the TLB might be invalidated.<br />

The effect of the Security Extensions on the TLB maintenance operations<br />

If an implementation includes the Security Extensions, the TLB maintenance operations must take account<br />

of the current security state. Table B3-13 summarizes how the Security Extensions affect these operations.<br />

Table B3-13 TLB maintenance operations when the Security Extensions are implemented<br />

TLB maintenance operation TLB entries guaranteed to be invalidated<br />

Invalidate all entries All TLB entries accessible in the current security state.<br />

Invalidate single entry by MVA Targeted TLB entry, only if all of these apply:<br />

the MVA value matches<br />

the ASID value matches, for a non-global entry<br />

the entry applies to the current security state.<br />

Invalidate entries by ASID match All non-global TLB entries for which both:<br />

the ASID value matches<br />

the entry applies to the current security state.<br />

Invalidate entries by MVA, all ASID All targeted TLB entries for which both:<br />

the MVA value matches<br />

the entry applies to the current security state.<br />

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

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

Saved successfully!

Ooh no, something went wrong!