Re: [gem5-users] Dumping stats in gem5

2017-07-10 Thread Jason Lowe-Power
Hi Muhammad, You don't have to use checkpoint. You can either use dumpreset stats or the m5_roi_begin/end magic instructions. For how to change the config scripts... I encourage you to trace through the Python config scripts' execution in configs/. This will help you understand how the configurat

Re: [gem5-users] Dumping stats in gem5

2017-07-09 Thread SHARJEEL KHILJI
Hi Jason, I am running ARM NoC and running splash2 benchmark on it. Now I want the stats to be dumped from all of the kernels in the benchmark without exiting (ending the simulation). According to your reply. I have understood it such that I have to annotate my application with check points at the

Re: [gem5-users] Dumping stats in gem5

2017-07-04 Thread Jason Lowe-Power
Hi Sharjeel, Here's an example script that I've used: https://github.com/powerjg/gem5/blob/features/tardis/configs/myconfigs/runkvm.py#L99. In that same branch (features/tardis) there are also more complicated scripts that fast-forward, switch CPUs, and reset stats. In general, I strongly encoura

Re: [gem5-users] Dumping stats in gem5

2017-07-04 Thread SHARJEEL KHILJI
Hi Jason, I am sorry but this is very old conversation but still if you please help. You said that I can modify the python script to dump stats and restart simulation. How can I do that and where in simulation.py I can do that. Thanks for your help. regards, sharjeel On 6 June 2017 at 19:11, Jas

Re: [gem5-users] Dumping stats in gem5

2017-06-06 Thread Jason Lowe-Power
Hi Sharjeel, There is a python function (dumpStats() IIRC), that will do what you want. Therefore, you need to exit the simulation loop at the end of each kernel. An easy way to do this is to annotate your benchmark with ROI begin/end m5 magic instructions. You then modify the Python config script

[gem5-users] Dumping stats in gem5

2017-06-06 Thread SHARJEEL KHILJI
Hi, I want to dump stats at the end of every kernel that I run from the splash2 benchmark. How to dump stats from each kernel from splash2 at the end of execution of that particular kernel program and then again dump stats for the next program without exiting the simulation. any suggestions ? best