gem5: update to 200281b08ca21f0d2678e23063f088960d3c0819

Fixes Linux kernel boot on arm and aarch64 due to:
d84a0714220ffcc10eed0530ec01ed1a01a4ad4b Was failing with:

    /build/ARM/cpu/simple/atomic.cc:377: virtual Fault AtomicSimpleCPU::readMem(Addr, uint8_t*, unsigned int, Request::Flags): Assertion
-`!pkt.isError()' failed
This commit is contained in:
Ciro Santilli
2018-08-22 10:31:49 +01:00
parent 72e135d2b2
commit 737fd32352
2 changed files with 1 additions and 26 deletions

View File

@@ -7310,31 +7310,6 @@ To get a terminal, either open a new shell and run:
or use `./run -u` if you are using tmux, which I highly recommend: <<tmux-gem5>>.
TODO `arm` and `aarch64` boot are failing at b585590fc089ec8918fc7853be8cef3de77e9c6a on kernel v4.17 with:
....
gem5.opt: /home/ciro/bak/git/linux-kernel-module-cheat/out/common/gem5/default/build/ARM/cpu/simple/atomic.cc:377: virtual Fault AtomicSimpleCPU::readMem(Addr, uint8_t*, unsigned int, Request::Flags): Assertion
`!pkt.isError()' failed.
....
Work around it for now by using v4.16 with <<gem5-build-variants>>:
....
git -C linux checkout v4.16
./configure -g && ./build -a arm -g -L v4.16 && ./run -a aarch64 -g -L v4.16
git -C linux checkout -
....
Bisected down to Linux kernel commit link:https://github.com/torvalds/linux/commit/c5e1035c9687025373b7c48a08efb37f5329916b[c5e1035c9687025373b7c48a08efb37f5329916b].
If we check out gem5 to a previous revision 60600f09c25255b3c8f72da7fb49100e2682093a, which is when I first noticed that v4.17 was not working, then there is another error instead:
....
panic: Tried to write GIC CPU at offset 0xd0
....
This is also fixed by using the Linux kernel v4.16, I'm not sure if it is the same error for both or not.
=== gem5 vs QEMU
* advantages of gem5: