If no address prefix is used (p:, l: or v:), the address is interpreted as virtual when used with a processor or else as a physical address.
The currently selected frontend processor is used unless the obj argument selects a specific processor or map target object in the system.
The inquiry argument, which defaults to TRUE, sets the inquiry flag of the transaction that is used when probing. Transactions in inquiry mode must have no side-effects and may bypass certain access restrictions.
The -port flag only applies to processor and selects the port space instead of the memory address space if it exists.
Transaction atoms can be used for routing rules and access rights in a platform. The -add-atoms flag opens up the capability to set transaction atoms on the command line: once the flag is set the command accepts additional arguments that have names starting with ATOM_ prefix. Tab complete after setting the -add-atoms flag to see the available atoms. These arguments are used by the command to pass in atom values to the translators it passes through during the transaction probing.
Please note that the ATOM_... arguments can be used only to specify values for transaction atoms that have integer values and provide Python wrappings. Complex atoms such as pointers and structures are not available from CLI.
All memory spaces that the access will traverse are listed, with the local address in each. The command warns for overlapping mappings with the same priority.
The Notes column indicates what type of operation took place on the transaction:
| translator: * |
| transaction_translator: ~ |
| translate: + |
| Unknown: ? |
| Loop: @ |
| Miss: miss |