I did look into Renode a couple months ago and it seems like it definitely has the potential to be a better simulator than QEMU (at least for seL4-related purposes). However, I found that the support for ARM was lacking, e.g there is no 64-bit Cortex-A CPU support. For RISC-V, the support seems to be better but I found it difficult to just get sel4test working and eventually gave up. Is your Renode script public anywhere? I'd be very keen to have a look!
Ivan ________________________________ From: Sam Leffler <[email protected]> Sent: Wednesday, 11 January 2023 4:06 PM To: Ivan Velickovic <[email protected]> Cc: devel <[email protected]> Subject: Re: [seL4] sel4test:nested timeout fault test flaky? Thanks. FWIW our riscv32 mcs tests run reliably under renode should you be interested in using a different simulator. It appears the 64-bit aarch64/raspi qemu runs only fail on the cited test so I'll probably just disable the test. On Tue, Jan 10, 2023 at 6:58 PM Ivan Velickovic <[email protected]<mailto:[email protected]>> wrote: Hello Sam Myself and Gerwin attempted to get simulation platforms working with MCS for the CI and noticed that the MCS tests were not consistently passing. I don’t think it’s a bug with the kernel but rather to do with how QEMU emulates timers. There’s more details here: https://github.com/seL4/ci-actions/pull/233. Ivan On 6/01/2023, at 5:13 AM, Sam Leffler via Devel <[email protected]<mailto:[email protected]>> wrote: We run sel4test regularly for a 64-bit raspi target under qemu and occasionally see failures like this: Starting test 129: TIMEOUTFAULT0003 Running test TIMEOUTFAULT0003 (Nested timeout fault) Error: Check badge(3) == expected_badge(2) failed. at line 9 This is a stock sel4test <https://github.com/AmbiML/sparrow-sel4test> + dep libs but an older kernel <https://github.com/AmbiML/sparrow-kernel>. Anyone know if this is an old (presumably fixed) bug or known issue? -Sam _______________________________________________ Devel mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
