Good morning all, I am attempting to measure the performance of the ARM HPI model shipped with gem5 (in SE mode) using the XSBench (https://github.com/ANL-CESAR/XSBench) benchmark program. gem5 appears to exit normally ("existing with last active thread context @ n") without the benchmark completing (XSBench prints benchmark results to stdout that are not present). I am using gem5.opt 2.0 with the command-line `build/ARM/gem5.opt configs/example/arm/starter_se.py --cpu="hpi" --num-cores=1 --mem-size=8GB ~/XSBench/src/XSBench`. I don't have a core dump, stack trace, or source code location (e.g. if an assertion was violated) that I can use, and the simulation takes several days to reach the failure point, which appears to be in the main benchmark loop (XSBench/src/Simulation.c:run_history_based_simulation()), so I can't step through it in GDB. What can I do to debug this? Cheers, Grant Vesely

Have you tried logging with build/ARM/gem5.opt --debug-flags ExecAll ? On Fri, Aug 2, 2019 at 4:32 PM Grant Vesely <vesely(a)pdx.edu> wrote: > > Good morning all, > > I am attempting to measure the performance of the ARM HPI model > shipped with gem5 (in SE mode) using the XSBench > (https://github.com/ANL-CESAR/XSBench) benchmark program. > > gem5 appears to exit normally ("existing with last active thread > context @ n") without the benchmark completing (XSBench prints > benchmark results to stdout that are not present). > > I am using gem5.opt 2.0 with the command-line `build/ARM/gem5.opt > configs/example/arm/starter_se.py --cpu="hpi" --num-cores=1 > --mem-size=8GB ~/XSBench/src/XSBench`. > > I don't have a core dump, stack trace, or source code location (e.g. > if an assertion was violated) that I can use, and the simulation takes > several days to reach the failure point, which appears to be in the > main benchmark loop > (XSBench/src/Simulation.c:run_history_based_simulation()), so I can't > step through it in GDB. What can I do to debug this? > > Cheers, > > Grant Vesely > _______________________________________________ > gem5-users mailing list > gem5-users(a)gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Thank you, this helped me find the problem: the benchmark program was invoking pthread_create(), and SE mode doesn't support threading. On Fri, Aug 2, 2019 at 5:15 PM Ciro Santilli <ciro.santilli(a)gmail.com> wrote: > > Have you tried logging with build/ARM/gem5.opt --debug-flags ExecAll ? > > On Fri, Aug 2, 2019 at 4:32 PM Grant Vesely <vesely(a)pdx.edu> wrote: > > > > Good morning all, > > > > I am attempting to measure the performance of the ARM HPI model > > shipped with gem5 (in SE mode) using the XSBench > > (https://github.com/ANL-CESAR/XSBench) benchmark program. > > > > gem5 appears to exit normally ("existing with last active thread > > context @ n") without the benchmark completing (XSBench prints > > benchmark results to stdout that are not present). > > > > I am using gem5.opt 2.0 with the command-line `build/ARM/gem5.opt > > configs/example/arm/starter_se.py --cpu="hpi" --num-cores=1 > > --mem-size=8GB ~/XSBench/src/XSBench`. > > > > I don't have a core dump, stack trace, or source code location (e.g. > > if an assertion was violated) that I can use, and the simulation takes > > several days to reach the failure point, which appears to be in the > > main benchmark loop > > (XSBench/src/Simulation.c:run_history_based_simulation()), so I can't > > step through it in GDB. What can I do to debug this? > > > > Cheers, > > > > Grant Vesely > > _______________________________________________ > > gem5-users mailing list > > gem5-users(a)gem5.org > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Grant, there is some support on ARM actually, but there are some known bugs that we have to fix. I'll try to ping you if we manage to solve it, or let us know if you do, it should not be very hard. On Thu, Aug 15, 2019 at 9:52 PM Grant Vesely <vesely(a)pdx.edu> wrote: > > Thank you, this helped me find the problem: the benchmark program was > invoking pthread_create(), and SE mode doesn't support threading. > > On Fri, Aug 2, 2019 at 5:15 PM Ciro Santilli <ciro.santilli(a)gmail.com> wrote: > > > > Have you tried logging with build/ARM/gem5.opt --debug-flags ExecAll ? > > > > On Fri, Aug 2, 2019 at 4:32 PM Grant Vesely <vesely(a)pdx.edu> wrote: > > > > > > Good morning all, > > > > > > I am attempting to measure the performance of the ARM HPI model > > > shipped with gem5 (in SE mode) using the XSBench > > > (https://github.com/ANL-CESAR/XSBench) benchmark program. > > > > > > gem5 appears to exit normally ("existing with last active thread > > > context @ n") without the benchmark completing (XSBench prints > > > benchmark results to stdout that are not present). > > > > > > I am using gem5.opt 2.0 with the command-line `build/ARM/gem5.opt > > > configs/example/arm/starter_se.py --cpu="hpi" --num-cores=1 > > > --mem-size=8GB ~/XSBench/src/XSBench`. > > > > > > I don't have a core dump, stack trace, or source code location (e.g. > > > if an assertion was violated) that I can use, and the simulation takes > > > several days to reach the failure point, which appears to be in the > > > main benchmark loop > > > (XSBench/src/Simulation.c:run_history_based_simulation()), so I can't > > > step through it in GDB. What can I do to debug this? > > > > > > Cheers, > > > > > > Grant Vesely > > > _______________________________________________ > > > gem5-users mailing list > > > gem5-users(a)gem5.org > > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users