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

disk persistency: gem5 is not persistent

Browse Source
This commit is contained in:
Ciro Santilli
2018-05-31 14:57:43 +01:00
parent 85d3c3e74d
commit 3e626ccf8f
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.adoc
View File

@@ -865,9 +865,12 @@ the disk image gets overwritten by a fresh filesystem and you lose all changes.
Remember that if you forcibly turn QEMU off without `sync` or `poweroff` from inside the VM, e.g. by closing the QEMU window, disk changes may not be saved.
Persistency can be turned off by passing the `snapshot` option to `-drive` (not exposed on our scripts).
Persistency can be turned off by:
When booting from <<initrd>> however without a disk, persistency is lost.
* passing the `snapshot` option to `-drive` (not exposed on our scripts)
* booting from <<initrd>> with a CPIO instead of with a disk
gem5 does not write back to the disk image, which is a good thing to keep its reboots deterministic.
=== Kernel command line parameters
@@ -4995,7 +4998,9 @@ Memory access on vanilla seem impossible due to optimizations that QEMU does:
==== gem5 tracing
gem5 also has a tracing mechanism, as documented at: http://www.gem5.org/Trace_Based_Debugging
gem5 unlike QEMU is deterministic by default without needing to replay traces
But it also provides a tracing mechanism documented at: link:http://www.gem5.org/Trace_Based_Debugging[] to allow easily inspecting certain aspects of the system:
....
./run -a aarch64 -E 'm5 exit' -g -T Exec