Hi Akram,
I was trying to get traces using the communication monitor. I have edited
the /configs/common/CacheConfig.py this way reading from other people's
questions in this forum.
system.L2monitor = CommMonitor(trace_file = "L2_trace_tr.tr")
system.tol2bus.master = system.L2monitor.slave
#system.l2.cpu_side = system.tol2bus.master
system.l2.cpu_side = system.L2monitor.master
I have then built gem5 and tried this command to see if I can get some
traces:
build/X86/gem5.opt configs/example/se.py
--cmd=tests/test-progs/hello/bin/x86/linux/hello
But I see no trace files in the /m5out/ folder. I don't know what wrong I
am doing here.
I have started working on gem5 pretty recently(2 weeks back), so I think I
am working with the latest version of gem5.
Thanks,
Rubel Ahmed
USF-CSE
Tampa, FL
On Wed, Jan 29, 2020 at 4:07 PM Ayaz Akram <yazak...@ucdavis.edu> wrote:
> Hi Mohammad,
>
> As far as params are concerned, in gem5 params are passed from python to
> C++ objects. For example, all parameters of CommMonitor are defined in
> src/mem/CommMonitor.py. Once you compile gem5, you can view the generated
> header file for these parameters: build/X86/params/CommMonitor.hh (for X86
> e.g.).
> Look here (
> http://www.gem5.org/documentation/learning_gem5/part2/parameters/) for
> more details on parameters of SimObjects.
>
> Based on this document (http://old.gem5.org/General_Memory_System.html),
> you might have to also connect MemTraceProbe to CommMonitor. Though
> src/mem/CommMonitor.py does not have a trace_file parameter, you can find
> this parameter in src/mem/probes/MemTraceProbe.py. Btw, which gem5 version
> are you using?
>
> Regards,
> Ayaz
>
> On Tue, Jan 28, 2020 at 8:04 PM Mohammad Ahmadi <mahm...@mail.usf.edu>
> wrote:
>
>> hello everyone,
>>
>> I am trying to use communication monitor to generate trace from system
>> simulation. When I'm trying to pass the *trace_file* argument to the
>> constructor, I get the following error:
>>
>> "AttributeError: Class CommMonitor has no parameter trace_file"
>>
>> I also looked into the communication monitor header file, comm_monitor.hh
>> and I see that there is an include line:
>>
>> #include "params/CommMonitor.hh"
>>
>> but there are no *params* directory in the gem5 source code. Do you know
>> where the problem might be?
>>
>> Thanks,
>> Mohammad Ahmadi
>> _______________________________________________
>> 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
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
