Hey Patrick, This isn't exactly an answer to your question, but you can find a similarly "simple" x86 FS configuration in the gem5-resources repository. E.g., https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/boot-exit/configs/system/ .
I'm sure that it's *possible* to do what you're suggesting and set up the replay mechanism's system to match that of FSConfig.makeLinuxX86System. However, it may be easier to use a different script that's not fs.py so you can better understand how the system is being constructed. Cheers, Jason On Mon, Nov 16, 2020 at 3:09 PM Patrick Sheridan (psheridan) via gem5-users <gem5-users@gem5.org> wrote: > Micron Confidential > > I am trying to replay an elastic trace taken with an X86 system (built > similarly as in fs.py – using common.FSConfig.makeLinuxX86System). > > > > However, when I try to replay the trace, using the same system, but > switching to the TraceCPU, I get the following assertion error: > > > > gem5.opt: build/X86/sim/system.hh:133: const System::Threads::Thread& > System::Threads::thread(ContextID) const: Assertion `id < size()' failed. > > > > In looking at the example etrace_replay.py, I see that, by contrast, the > system is constructed much more simply – using the System() constructor > directly. However, I was wondering if it is possible to make use of the > common.FSConfig.makeLinuxX86System function (which uses makeX86System) as > it does a lot with regard to setting up the bus hierarchy correctly. > > > > Thanks, > > Patrick > > Micron Confidential > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
