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: fix link on readme

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-09-07 00:00:01 +00:00
parent e1ceb85934
commit e38c9f2641
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.adoc
View File

@@ -10391,7 +10391,7 @@ Getting started at: xref:gem5-buildroot-setup[xrefstyle=full].
=== gem5 vs QEMU
* advantages of gem5:
** simulates a generic more realistic <<gem5-cpu-models,optionally pipelined and 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:
** simulates a generic more realistic <<gem5-cpu-types,optionally pipelined and 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
@@ -12306,7 +12306,7 @@ Python 3 is then automatically used when running if you use that build.
=== gem5 CPU types
gem5 has a few in tree CPU models for different purposes, here is an overview of the most interesting ones:
gem5 has a few in tree CPU models for different purposes. In fs.py and se.py, those are selectable with the `--cpu-type` option. Here is an overview of the most interesting ones:
* `BaseSimpleCPU` descendants. Have no CPU pipeline.
** `AtomicSimpleCPU`: the default one. Memory accesses happen instantaneously. The fastest simulation except for KVM, but not realistic at all. Useful to <<gem5-restore-checkpoint-with-a-different-cpu>>.