Yes, I would try deleting the entire build (build/, not just build/SPARC) directory and recompiling from scratch.
I'm not familiar with the details of the T1's coherence protocol. If you really care about modeling the coherence protocol, then you should be using the Ruby memory model. You can look through all of the protocols for Ruby (in src/mem/protocol) and pick which one is most similar. Jason On Wed, Aug 10, 2016 at 11:35 AM Zaman, Monir <[email protected]> wrote: > Jason, > > You are right. Although I did put the option for “MinorCPU” in the > build_opts folder, in the ~/build/SPARC/minor folder there is no compiled > files other than just a “SConscript” file. As oppose to, in the “o3” > folder, there are a bunch of linked files for the CPU. So this means the > “Minor” cpu is not getting compiled as you suspected. > > > > What should be the way to go for this? Should I simply delete everything > again and recompile GEM5 completely from scratch or simply deleting the > ~/build/SPARC/* and then rebuilding may do the trick? Is there any other > way you think may be possible? > > > > I shall look into the SE script for multiple workload running on the CPU. > > > > Also are you familiar with the L1 Directory/L2 Directory, as that is how > the SPARC maintains the coherency. What options in GEM5 would give me these > numbers? > > > > Thanks again for your time. J > > > > Monir > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
