From e38c9f2641540bd3a4b8eea2f26fd29d244fbcc8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Sat, 7 Sep 2019 00:00:01 +0000 Subject: [PATCH] gem5: fix link on readme --- README.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index 58dd47e..b4baca9 100644 --- a/README.adoc +++ b/README.adoc @@ -10391,7 +10391,7 @@ Getting started at: xref:gem5-buildroot-setup[xrefstyle=full]. === gem5 vs QEMU * advantages of gem5: -** simulates a generic more realistic <> 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 <> 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 <>.