Hi,

Is there any way to only trace certain specific areas of interest in test application? I am currently using --debug-start and --debug-end but it is very difficult to find the exact time when region of interest is executed. Also, I looked at m5_work_begin() and m5_work_end() but that seems to be for a different thing altogether.

Thanks and Regards,
Gautam

Hi,

Thanks for the help! It works great.

Thanks and Regards,
Gautam

From: Hoa Nguyen hoanguyen@ucdavis.edu
Sent: Wednesday, June 8, 2022 2:51 AM
To: The gem5 Users mailing list gem5-users@gem5.org
Subject: [gem5-users] Re: Adding debug ROI to test application

Hi,

I think there are a couple of options.

One way is to do m5_exit() right before the ROI, record the current Tick, and rerun with --debug-start set to that number.

Another way is that, in the first run, you can do m5_exit() right before the ROI, then take a checkpoint. In the next run, you can enable the debug flags (and restore the checkpoint).

Regards,
Hoa Nguyen

On Tue, Jun 7, 2022, 15:53 Gautam Pathak <gautam.pathak@uwaterloo.camailto:gautam.pathak@uwaterloo.ca> wrote:
Hi,

Is there any way to only trace certain specific areas of interest in test application? I am currently using --debug-start and --debug-end but it is very difficult to find the exact time when region of interest is executed. Also, I looked at m5_work_begin() and m5_work_end() but that seems to be for a different thing altogether.

Thanks and Regards,
Gautam

gem5-users mailing list -- gem5-users@gem5.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@gem5.org