3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

gem5 trace: explain A and D

Browse Source
This commit is contained in:
Ciro Santilli
2018-08-20 16:41:19 +01:00
parent b57baebe87
commit 72e135d2b2
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@@ -7259,7 +7259,11 @@ Breakdown:
* `.1` as in `@start_kernel.1`: index of the microop
* `stp`: instruction disassembly. Seems to use `.isa` files dispersed per arch, which is an in house format: http://gem5.org/ISA_description_system
* `strxi_uop x29, [ureg0]`: microop disassembly.
* `MemWrite : D=0x0000000000000000 A=0xffffff8008913f90`: TODO. Further description of the microops.
* `MemWrite : D=0x0000000000000000 A=0xffffff8008913f90`: a memory write microop:
** `D` stands for data, and represents the value that was written to memory or to a register
** `A` stands for address, and represents the address to which the value was written. It only shows when data is being written to memory, but not to registers.
The best way to verify all of this is to write some bare metal code: https://stackoverflow.com/questions/43682311/uart-communication-in-gem5-with-arm-bare-metal
Trace the source lines just like <<trace-source-lines,for QEMU>> with: