Hi Hossam, If you're using the stdlib, you can override the default ROI begin handler. See the documentation here: https://github.com/gem5/gem5/blob/stable/src/python/gem5/simulate/simulator.py#L145
If you're not using the stdlib, then look for where the code you're using calls m5.stats.dump() and comment it out :) Cheers, Jason On Wed, Feb 21, 2024 at 4:59 PM Hossam ElAtali <hossam.elat...@uwaterloo.ca> wrote: > Hi Jason, > > Thanks for the very quick response! > > I managed to surround the ROI with m5op instructions to issue WORKBEGIN > and WORKEND events, but now the stats.txt file is getting out of hand. > It dumps stats every time the simulation pauses. Is there a way to make it > not dump on every event or disable it altogether? I tried using the > --stats-file command line option with an empty string but that caused a > crash. I also tried truncating and/or deleting the file in the event > handler in the config script (using the open and truncate python > functions), but that did nothing (my guess is because the file is already > open elsewhere). > > Thanks again! > > Best, > Hossam > ------------------------------ > *From:* Jason Lowe-Power <ja...@lowepower.com> > *Sent:* Wednesday, February 21, 2024 1:59 PM > *To:* The gem5 Users mailing list <gem5-users@gem5.org> > *Cc:* Hossam ElAtali <hossam.elat...@uwaterloo.ca> > *Subject:* Re: [gem5-users] Limit debug output to certain instruction > address range > > Hi Hossam, > > > Yet another option is a way to enable/disable debugging in the config > script mid-simulation. This would allow me to exit the simulation using an > m5op before the instructions, enable debugging in the config script, > continue, exit using an m5op after the instructions, disable debugging, etc. > > You can definitely do this. > > You can use the m5.trace.enable() and m5.trace.disable() functions in > python to enable and disable the debug output. You can use m5 ops to exit > the simulation as you mentioned as well and then call these functions. > > Cheers, > Jason > > On Wed, Feb 21, 2024 at 10:46 AM Hossam ElAtali via gem5-users < > gem5-users@gem5.org> wrote: > > Hi, > > I'm currently experimenting with Spectre on gem5, and I'm dumping > debugging output using the O3PipeView flag. However, I get a lot of output > for instructions that are not relevant to the attack sequence. I was > wondering if it's possible to limit the debugging output to a certain > instruction address range. I know I can limit it to a tick range, but I'd > like to dump every instance of the attack, not just a specific one. I have > the instruction addresses for the attack and it would be great if I can > just use that. > > Another option would be to dynamically enable and disable debugging output > (or the O3PipeView flag, at least) using an m5op. > > Yet another option is a way to enable/disable debugging in the config > script mid-simulation. This would allow me to exit the simulation using an > m5op before the instructions, enable debugging in the config script, > continue, exit using an m5op after the instructions, disable debugging, etc. > > Any help is greatly appreciated. Thank you. > > Best, > Hossam > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
