I was wondering if anyone is running into the same problem or if anyone has any suggestions on how to proceed with debugging this problem.
On Mon, Jul 29, 2019 at 4:57 PM Shehab Elsayed <shehaby...@gmail.com> wrote: > Sorry for the spam. I just forgot to mention that the system configuration > I am using is mainly from > https://github.com/darchr/gem5/tree/jason/kvm-testing/configs/myconfigs. > <https://github.com/darchr/gem5/tree/jason/kvm-testing/configs/myconfigs> > > > Shehab Y. Elsayed, MSc. > PhD Student > The Edwards S. Rogers Sr. Dept. of Electrical and Computer Engineering > University of Toronto > E-mail: shehaby...@gmail.com > <https://webmail.rice.edu/imp/message.php?mailbox=INBOX&index=11#> > > > On Mon, Jul 29, 2019 at 4:08 PM Shehab Elsayed <shehaby...@gmail.com> > wrote: > >> I have set up a repo with gem5 that demonstrates the problem. The repo >> includes the latest version of gem5 from gem5's github repo with a few >> patches applied to get KVM working together with the kernel binary and disk >> image I am using. You can get the repo at >> https://github.com/ShehabElsayed/gem5_debug.git. >> <https://github.com/ShehabElsayed/gem5_debug.git> >> >> These steps should reproduce the problem: >> 1- scons build/X86/gem5.opt >> 2- ./scripts/get_fs_stuff.sh >> 3- ./scripts/run_fs.sh 8 >> >> I have also included sample m5term outputs for both a 2 thread run >> (m5out_2t) and an 8 thread run (m5out_8t) >> >> Any help is really appreciated. >> >> >> >> On Tue, Jul 23, 2019 at 11:01 AM Shehab Elsayed <shehaby...@gmail.com> >> wrote: >> >>> When I enable the Exec debug flag I can see that it seems to be stuck in >>> a spin lock (queued_spin_lock_slowpath) >>> >>> On Fri, Jul 19, 2019 at 5:28 PM Shehab Elsayed <shehaby...@gmail.com> >>> wrote: >>> >>>> Hello All, >>>> >>>> I have a gem5 X86 full system set up that starts with KVM cores and >>>> then switches to O3 cores once the benchmark reaches the region of >>>> interest. Right now I am testing with a simple multithreaded hello >>>> world benchmark. Sometimes the benchmark completes successfully while >>>> others gem5 just seems to hang after starting the benchmark. I believe it >>>> is still executing some instructions but without making any progress. The >>>> chance of this behavior (indeterminism) happening increases as the >>>> number of simulated cores or the number of threads created by the benchmark >>>> increases. >>>> >>>> Any ideas what might be the reason for this or how I can start >>>> debugging this problem? >>>> >>>> Note: I have tried the patch in https://gem5-review.googlesource >>>> .com/c/public/gem5/+/19568 but the problem persists. >>>> >>>> Thanks! >>>> >>>
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
