A5.6
Specific behaviors on aborts and memory attributes
This section describes specific behaviors caused by aborts and also describes memory attributes.
MMU responses
When one of the following translation is completed, the MMU generates a response to the requester:
• A L1 TLB hit.
• A L2 TLB hit.
• A translation table walk.
The response from the MMU contains the following information:
• The PA corresponding to the translation.
• A set of permissions.
• Secure or Non-secure.
• All the information required to report aborts. See the
Arm
®
Architecture Reference Manual Armv8, for
Armv8-A architecture profile
for more details.
A5.6.1
External aborts
External aborts are defined as those that occur in the memory system rather than those that the MMU
detects. Normally, external memory aborts are rare. External aborts are caused by errors flagged to the
external interface.
When an external abort to the external interface occurs on an access for a translation table walk access,
the MMU returns a synchronous external abort. For a load multiple or store multiple operation, the
address captured in the fault address register is that of the address that generated the synchronous
external abort.
See the
Arm
®
Architecture Reference Manual Armv8, for Armv8-A architecture profile
for more
information.
A5.6.2
Mis-programming contiguous hints
In the case of a mis-programming contiguous hint, when there is a descriptor that contains a set CH bit,
all contiguous VAs contained in this block should be included in the input VA address space that is
defined for stage 1 by TxSZ for TTBx or for stage 2 by {SL0, T0SZ}.
The Cortex-A76 core treats such a block as not causing a translation fault.
A5.6.3
Memory attributes
The memory region attributes specified in the TLB entry, or in the descriptor in case of translation table
walk, determine if the access is:
• Normal Memory or Device type.
• One of the four different device memory types that are defined for Armv8:
Device-nGnRnE
Device non-Gathering, non-Reordering, No Early Write Acknowledgment.
Device-nGnRE
Device non-Gathering, non-Reordering, Early Write Acknowledgment.
Device-nGRE
Device non-Gathering, Reordering, Early Write Acknowledgment.
Device-GRE
Device Gathering, Reordering, Early Write Acknowledgment.
In the Cortex-A76 core, a page is cacheable only if the inner memory attribute and outer memory
attribute are Write Back. In all other cases, all pages are downgraded to Non-cacheable Normal memory.
When the MMU is disabled at stage 1 and stage 2, and SCTLR.I is set to 1, instruction prefetches are
cached in the instruction cache but not in the unified cache. In all other cases, normal behavior on
memory attribute applies.
A5 Memory Management Unit
A5.6 Specific behaviors on aborts and memory attributes
100798_0300_00_en
Copyright © 2016–2018 Arm Limited or its affiliates. All rights
reserved.
A5-68
Non-Confidential
Summary of Contents for Cortex-A76 Core
Page 4: ......
Page 22: ......
Page 23: ...Part A Functional description ...
Page 24: ......
Page 119: ...Part B Register descriptions ...
Page 120: ......
Page 363: ...Part C Debug descriptions ...
Page 364: ......
Page 401: ...Part D Debug registers ...
Page 402: ......
Page 589: ...Part E Appendices ...
Page 590: ......