Hi, @Humza or @Farbin: Can you please push the spec-2017 change that worked for you to the mainline gem5 as well?
Thanks, -Ayaz On Thu, Apr 6, 2023 at 9:03 PM Ayaz Akram <yazak...@ucdavis.edu> wrote: > Hi Farbin, > > However, now they're taking so much time to run. I'm trying to run >> perlbench, gcc, bwaves, and mcf with the "test" size, and they're running >> for more than 10 hours and still, none of them aren't finished. Is this >> normal? Could you tell me how long they usually take? > > > I would expect these benchmarks (with test input) to take days to simulate > completely. The actual simulation time would depend on the CPU type you are > simulating and the hardware platform where the simulations are run. I think > for Timing/Minor CPU you can expect a simulation rate of 400K-500K > (simulated) instructions per host second. > > -Ayaz > > On Thu, Apr 6, 2023 at 10:36 AM Farbin Fayza via gem5-users < > gem5-users@gem5.org> wrote: > >> Hi Humza, >> Thank you so much for your help. I added the processor.switch() command >> as you said and now the simulations are running. >> >> However, now they're taking so much time to run. I'm trying to run >> perlbench, gcc, bwaves, and mcf with the "test" size, and they're running >> for more than 10 hours and still, none of them aren't finished. Is this >> normal? Could you tell me how long they usually take? >> >> Also, is there any way to verify that they are indeed running correctly? >> Because in the m5out folder, there are no logs or something that I can >> verify. >> >> About the index error, yes, I had the same issue too. Unfortunately, we >> only have spec2017 currently and we urgently need to get things running. I >> believe the index issue doesn't cause any other problems or affect the >> stats, am I correct? >> >> Thanks so much again! >> Farbin. >> >> >> On Wed, Apr 5, 2023 at 7:52 PM Humza Ikram via gem5-users < >> gem5-users@gem5.org> wrote: >> >>> Hi, >>> >>> I believe the reason for this is that the >>> "x86-spec-cpu2017-benchmarks.py" file does not have a "process.switch()" >>> statement and, as such, the processor remains in "CPUTypes.KVM" mode. >>> >>> If there is no other error when your script finishes, you could try >>> adding "processor.switch()" infront of line number 290 in this file and >>> trying again (before "yield False"). >>> >>> I encountered the same issue in the spec-2006 benchmarks. >>> >>> Another issue I encountered in the spec-2006 benchmarks was related to >>> an error you *may* face at the end that relates to accessing an out of >>> bounds index of a python list. (This is because "ExitEvent.WORKBEGIN" and >>> "ExitEvent.WORKEND" may not be defined in the workload.) >>> >>> Both of these are fixed in the spec-2006 benchmarks file (link below) in >>> the develop branch and you could try moving them over to the spec-2017 >>> benchmarks file. >>> >>> https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/configs/example/gem5_library/x86-spec-cpu2006-benchmarks.py >>> >>> Thanks. >>> Humza Ikram. >>> >>> ------------------------------ >>> *From:* Farbin Fayza via gem5-users <gem5-users@gem5.org> >>> *Sent:* Thursday, April 6, 2023 12:20 AM >>> *To:* gem5-users@gem5.org <gem5-users@gem5.org> >>> *Cc:* Farbin Fayza <ffa...@bu.edu> >>> *Subject:* [gem5-users] SPEC2017 - Most of the metrics in >>> m5.out/stats.txt are 0 or undefined >>> >>> Hi, >>> I'm trying to run spec2017 benchmark in full system mode with gem5. I >>> followed this tutorial to build the disk image file for spec >>> https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/ >>> . >>> The only difference with the tutorial is that I have spec version, 1.1.9 >>> and in the tutorial they use 1.1.0. So I just changed the version in >>> their scripts. >>> The build was successful although it had some errors for some peak >>> benchmarks. >>> >>> When I'm trying to run gem5 with this command: >>> build/X86/gem5.opt \ >>> configs/example/gem5_library/x86-spec-cpu2017-benchmarks.py \ >>> --image ../disk-image/spec-2017/spec-2017-image/spec-2017 \ >>> --partition 1 \ >>> --benchmark <benchmark_program> \ >>> --size <workload_size> >>> >>> The simulation is ending within minutes regardless of the workload size >>> and all of the contents of the stat file (m5out/stats.txt) after hostOprate >>> are 0 or undefined. >>> Could anyone help with this issue? >>> >>> _______________________________________________ >>> gem5-users mailing list -- gem5-users@gem5.org >>> To unsubscribe send an email to gem5-users-le...@gem5.org >>> >> _______________________________________________ >> gem5-users mailing list -- gem5-users@gem5.org >> To unsubscribe send an email to gem5-users-le...@gem5.org >> >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
