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

Merge branch 'master' of github.com:cirosantilli/linux-kernel-module-cheat

Browse Source
This commit is contained in:
Ciro Santilli
2018-02-22 17:45:21 +00:00
parent cd34810607 ecdded0316
commit 5a1d5ba7a9
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.adoc
View File

@@ -1199,11 +1199,9 @@ in which the boot appears to hang for a considerable time.
=== GEM5 === GEM5
==== GEM5 Introduction
GEM5 is a system simulator, much like QEMU: http://gem5.org/ GEM5 is a system simulator, much like QEMU: http://gem5.org/
Vs QEMU: ==== GEM5 vs QEMU
* advantage: simulates a generic more realistic pipelined and optionally out of order CPU cycle by cycle, including a realistic DRAM memory access model with latencies, caches and page table manipulations. This allows us to: * advantage: simulates a generic more realistic pipelined and optionally out of order CPU cycle by cycle, including a realistic DRAM memory access model with latencies, caches and page table manipulations. This allows us to:
** do much more realistic performance benchmarking with it, which makes absolutely no sense in QEMU, which is purely functional ** do much more realistic performance benchmarking with it, which makes absolutely no sense in QEMU, which is purely functional
@@ -1220,6 +1218,11 @@ Instead, we have only chip makers, who keep everything that really works closed,
+ +
** the documentation is more scarce ** the documentation is more scarce
** it takes longer to support new hardware features ** it takes longer to support new hardware features
* not sure: GEM5 has BSD license while QEMU has GPL
+
This suits chip makers that want to distribute forks with secret IP to their customers.
+
On the other hand, the chip makers tend to upstream less, and the project becomes more crappy in average :-)
==== GEM5 ARM ==== GEM5 ARM
@@ -1348,7 +1351,7 @@ I have also tried to copy the exact same kernel command line options used by QEM
===== GEM5 checkpoint ===== GEM5 checkpoint
Analogous to QEMU's <<snapshot>>. Analogous to QEMU's <<snapshot>>, but better since it can be started from inside the guest, so we can easily checkpoint after a specific guest event, e.g. just before `init` is done.
Documentation: http://gem5.org/Checkpoints Documentation: http://gem5.org/Checkpoints