Skip to content

Commit d6905e2

Browse files
committed
readme: minor fixes
1 parent 70d26c7 commit d6905e2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2869,7 +2869,7 @@ cd linux-kernel-module-cheat
28692869
sudo ./setup -y
28702870
....
28712871

2872-
and then proceed exactly as in <<prebiult>>.
2872+
and then proceed exactly as in <<prebuilt>>.
28732873

28742874
We don't want to build the full Buildroot image inside the VM as that would be way too slow, thus the recommendation for the prebuilt setup.
28752875

@@ -8538,7 +8538,7 @@ but the approximation is reasonable.
85388538
+
85398539
It is used mostly for microarchitecture research purposes: when you are making a new chip technology, you don't really need to specialize enormously to an existing microarchitecture, but rather develop something that will work with a wide range of future architectures.
85408540
** runs are deterministic by default, unlike QEMU which has a special <<qemu-record-and-replay>> mode, that requires first playing the content once and then replaying
8541-
** gem5 ARM at least appears to implement more low level CPU functionality than QEMU, e.g. QEMU only added EL2 in 2018, and EL3 is yet unimplemented: https://stackoverflow.com/questions/42824706/qemu-system-aarch64-entering-el1-when-emulating-a53-power-up gem5 `fs.py` can enable EL3 with `-V` and EL2 with `--enable-security-extensions`
8541+
** gem5 ARM at least appears to implement more low level CPU functionality than QEMU, e.g. QEMU only added EL2 in 2018: https://stackoverflow.com/questions/42824706/qemu-system-aarch64-entering-el1-when-emulating-a53-power-up See also: <<arm-exception-level>>
85428542
* disadvantage of gem5: slower than QEMU, see: <<benchmark-linux-kernel-boot>>
85438543
+
85448544
This implies that the user base is much smaller, since no Android devs.

0 commit comments

Comments
 (0)