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
