Hi Rubel, The command you execute does not simulate the system that you put in the image. There is no l2 bus and l2 cache in the system that you simulate. If you want to have l2 cache you need to add --l2cache as an argument to the script.
In order to see what's on the system you execute, you should check m5out/ *config.ini* after you make the simulation. To see all the options you have, you can run build/X86/gem5.opt configs/example/se.py --help Cheers, Muhammet -- Md Rubel Ahmed <mdrubelah...@mail.usf.edu>, 24 Mar 2020 Sal, 20:13 tarihinde şunu yazdı: > Hi all, > Lets say I am using the following command to simulate a system on gem5: > > build/X86/gem5.opt configs/example/se.py > --cmd=tests/test-progs/hello/bin/x86/linux/hello > --cpu-type=TimingSimpleCPU --l1d_size=64kB --l1i_size=16kB --caches > > How can I get a high-level view/diagram of the system that is being > simulated here? *I am interested in knowing the architecture of the > system on which the binary is being executed as sys-calls.* For example, > I assume this command runs the hello binary on a system that looks like the > following: > > > My assumption is L2 bus is implicit here, same as membus and mem_ctrl. > Please advise me on how to interpret the command line *architecture > arguments* to get the high-level view of the system, if possible with > example. > > Thank you, > *Rubel Ahmed* > *USF-CSE* > *Tampa, FL* > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
