For my defined system, I am using debug-flags = RubyNetwork and debug-file = <output_file.txt>. And then I'm extracting the [flit:: ...] data from this <output_file.txt>. But, the problem is, <output_file.txt> is very big when I'm running the parsec benchmarks on it. Are there any better ways to capture these flits? Do I need to modify the NetworkInterface.cc or Router.cc to capture these files? flit.cc has a print function defined in it. Who exactly is calling this flit::print function to print the flits while capturing debug files? Also, will modifying these files affect the correctness of my simulations? Regards, Ojas Sharma

Hi Ojas, If you are using Garnet network then you can print it from Network Interface. If not, you could replace the debug flag to something custom for the specific DPRINT that you want and build again to reduce the size of your output log. Thanks, Srikant On Fri, Mar 1, 2024 at 11:20 AM Ojas Sharma via gem5-users < gem5-users@gem5.org> wrote: > For my defined system, I am using debug-flags = RubyNetwork and debug-file > = <output_file.txt>. And then I'm extracting the [flit:: ...] data from > this <output_file.txt>. But, the problem is, <output_file.txt> is very big > when I'm running the parsec benchmarks on it. Are there any better ways to > capture these flits? Do I need to modify the NetworkInterface.cc or > Router.cc to capture these files? > flit.cc has a print function defined in it. Who exactly is calling this > flit::print function to print the flits while capturing debug files? Also, > will modifying these files affect the correctness of my simulations? > > Regards, > Ojas Sharma > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-leave@gem5.org >