gem5: vs qemu, implements more low level functionality

This commit is contained in:
Ciro Santilli
2018-08-11 21:50:10 +01:00
parent 71a5ab31a2
commit e5e68750ce

View File

@@ -7375,6 +7375,7 @@ but the approximation is reasonable.
+ +
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. 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.
** 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 ** 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
** 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
* disadvantage of gem5: slower than QEMU, see: <<benchmark-linux-kernel-boot>> * disadvantage of gem5: slower than QEMU, see: <<benchmark-linux-kernel-boot>>
+ +
This implies that the user base is much smaller, since no Android devs. This implies that the user base is much smaller, since no Android devs.