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.

The translate <strong>and</strong> lock model<br />

<strong>ARM</strong>v4 <strong>and</strong> <strong>ARM</strong>v5 Differences<br />

This mechanism uses explicit TLB operations to translate <strong>and</strong> lock specific addresses into the TLB. Entries<br />

are unlocked on a global basis using the unlock operations. Addresses are loaded using their MVA. The<br />

following actions are UNPREDICTABLE:<br />

accessing these functions with read (MRC) comm<strong>and</strong>s<br />

using functions when the MMU is disabled<br />

trying to translate <strong>and</strong> lock an address that is already present in the TLB.<br />

Any abort generated during the translation is reported as a lock abort in the FSR. Only external aborts <strong>and</strong><br />

Translation faults are guaranteed to be detected. Any access permission, domain, or alignment checks on<br />

these functions are IMPLEMENTATION DEFINED. Operations that generate an abort do not affect the target<br />

TLB.<br />

Where this model is applied to a unified TLB, the data TLB operations must be used.<br />

Invalidate_all (I,D, or I <strong>and</strong> D) operations have no effect on locked entries.<br />

TLB lockdown procedure, using the translate <strong>and</strong> lock model<br />

All previously locked entries can be unlocked by issuing the appropriate unlock operation, I or D side.<br />

Explicit lockdown operations are then issued with the required MVA in register Rt.<br />

TLB unlock procedure, using the translate <strong>and</strong> lock model<br />

Issuing the appropriate unlock (I or D) TLB operation unlocks all locked entries. It is IMPLEMENTATION<br />

DEFINED whether an invalidate by MVA TLB operation removes the lock condition.<br />

Note<br />

The invalidate behavior is different in the TLB locking by entry model, where the invalidate by MVA<br />

operation is guaranteed to occur.<br />

H.7.14 c13, VMSA FCSE support<br />

The FCSE described in Appendix E Fast Context Switch Extension (FCSE) is an IMPLEMENTATION DEFINED<br />

option in <strong>ARM</strong>v4 <strong>and</strong> <strong>ARM</strong>v5. The feature is supported by the FCSEIDR as described in c13, FCSE<br />

Process ID Register (FCSEIDR) on page B3-152. The Context ID <strong>and</strong> Software Thread ID registers listed<br />

for <strong>ARM</strong>v7 are not supported in <strong>ARM</strong>v4 <strong>and</strong> <strong>ARM</strong>v5.<br />

H.7.15 c15, IMPLEMENTATION DEFINED<br />

CP15 c15 is reserved for IMPLEMENTATION DEFINED use. It is typically used for processor-specific runtime<br />

<strong>and</strong> test features.<br />

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

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

Saved successfully!

Ooh no, something went wrong!