Thanks, Jason.
________________________________
From: gem5-users <gem5-users-boun...@gem5.org> on behalf of Jason Lowe-Power 
<ja...@lowepower.com>
Sent: Monday, April 15, 2019 6:35 PM
To: gem5 users mailing list
Subject: Re: [gem5-users] Debug prints in FS mode using script

That's ticks. You would have to divide by the cycle time to get cycles.

curCycle() should be curTick()/cyclePeriod() (cyclePeriod is the ticks per 
cycle. E.g., 500 for 2 GHz). See 
https://gem5.googlesource.com/public/gem5/+/refs/heads/master/src/sim/clocked_object.hh#65.

Jason

On Mon, Apr 15, 2019 at 1:47 PM ABHISHEK BHATTACHARYYA 
<abhattach...@wisc.edu<mailto:abhattach...@wisc.edu>> wrote:
Thanks, Jason. I followed your advice and I can see my debug prints now. 
However, I have one more question.

Do the debug prints here print out the ticks or cycles on the left 
(underlined)? If ticks, then how can I get the cycle value? I see there were 
similar questions asked earlier but I didn't understand the explanations 
provided. What does the call curCycle() return? I used it but the value 
returned matches the value on the left side of the print statements below.

500: system.ruby.l1_cntrl0: MESI_Two_Level-L1cache.sm:537: Issue GETS address: 
0x70000
78000: system.ruby.l1_cntrl0: MESI_Two_Level-L1cache.sm:845: Load complete 
address: 0x70000

Regards,
Abhishek Bhattcharyya
________________________________
From: gem5-users 
<gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>> on behalf of 
Jason Lowe-Power <ja...@lowepower.com<mailto:ja...@lowepower.com>>
Sent: Monday, April 15, 2019 11:12 AM
To: gem5 users mailing list
Subject: Re: [gem5-users] Debug prints in FS mode using script

Hi Abhishek,

Check --debug-help. You probably want --debug-file=<filename> and you may want 
--debug-start=<tick> when debugging Ruby protocols in FS mode. I've also found 
it useful to use a named pipe for the debug file and pipe it though `tail` to 
get only the last n lines (where n is usually megabytes to gigabytes).

PS: Using the Ruby random tester is a way to debug protocol issues without 
having to wait for hours (days if you have tracing on) for Linux to boot.

Cheers,
Jason

On Mon, Apr 15, 2019 at 9:01 AM ABHISHEK BHATTACHARYYA 
<abhattach...@wisc.edu<mailto:abhattach...@wisc.edu>> wrote:
Hi

I am running a full system simulation of gem5 with parsec benchmarks using an 
rcs script. I have added new debug prints to the gem5 code to trace RubySlicc 
request and response actions. How do I redirect the debug prints to a new file 
and collect the trace in this case?

Thanks,
Abhishek Bhattacharyya


Regards,


Abhishek Bhattacharyya

Graduate Research Assistant

Electrical and Computer Engineering Department

University of Wisconsin-Madison

_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto: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

Reply via email to