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

readme: qemu todos: show instructions and multicore trace

Browse Source
This commit is contained in:
Ciro Santilli
2018-05-02 00:14:51 +01:00
parent b992163d4e
commit 6a1e98fab2
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
README.adoc
View File

@@ -3511,6 +3511,23 @@ Patches were merged in post v2.12.0-rc2 but it crashed for me and I opened a min
Alternatively, https://github.com/mozilla/rr[`mozilla/rr`] claims it is able to run QEMU: but using it would require you to step through QEMU code itself. Likely doable, but do you really want to? Alternatively, https://github.com/mozilla/rr[`mozilla/rr`] claims it is able to run QEMU: but using it would require you to step through QEMU code itself. Likely doable, but do you really want to?
==== QEMU trace multicore
TODO: is there any way to distinguish which instruction runs on each core? Doing:
....
./run -a x86_64 -c 2 -E '/poweroff.out' -T exec_tb
./qemu-trace2txt
....
just appears to output both cores intertwined without any clear differentiation.
==== QEMU trace decode instructions
TODO: is is possible to show which instructions ran at each point in time, in addition to the address of the instruction with `exec_tb` shows? Hopefully dissembled, not just the instruction memory.
PANDA can list memory addresses, so I bet it can also decode the instructions: https://github.com/panda-re/panda/blob/883c85fa35f35e84a323ed3d464ff40030f06bd6/panda/docs/LINE_Censorship.md I wonder why they don't just upstream those things to QEMU's tracing.
==== gem5 tracing ==== gem5 tracing
gem5 also has a tracing mechanism, as documented at: http://www.gem5.org/Trace_Based_Debugging gem5 also has a tracing mechanism, as documented at: http://www.gem5.org/Trace_Based_Debugging