Searched hist:10109 (Results 1 - 1 of 1) sorted by relevance
| /gem5/src/arch/arm/ | ||
| H A D | table_walker.cc | 10109:b58c5c5854de Fri Mar 07 15:56:00 EST 2014 Geoffrey Blake <Geoffrey.Blake@arm.com> arm: Handle functional TLB walks properly The table walker code currently accounts for two types of walks, Atomic and Timing, and treats them differently. Atomic walks keep a single instance of WalkerState around for all walks to use in currState. Timing mode keeps a queue of in-flight WalkerStates and maintains currState as NULL between walks. If a functional walk is done during Timing mode, it is treated as an atomic walk and either creates a persistent WalkerState if in between Timing walks, or stomps an existing currState for an in-progress Timing walk. This patch distinguishes functional walks as being able to exist at any time and sets up a temporary WalkerState for its exclusive use and then cleans up when finished, leaving any in progress Atomic or Timing walks undisturbed. |
Completed in 24 milliseconds