I'm not sure if this is your ultimate problem, but if it only works on the CPU for the first N instructions, is N simply representing the point where you need a 64-bit counter instead of a 32-bit counter?
Unfortunately I don't know the answer to your other questions, sorry. Perhaps you are thinking of the m5ops, which people often use for things like resetting stats: https://www.gem5.org/documentation/general_docs/m5ops/ ? Matt On Tue, May 26, 2020 at 2:12 PM Rajeev Pal via gem5-users < gem5-users@gem5.org> wrote: > Hi All, > > Is it possible to dump and reset statistics after each N instructions for > CPU and/or AMD GPU. > I see that there is a *max_insts_any_thread* var for cpus. I was able to > use it to stop simulation, dump and reset stats (from apu_se.py), but it > only works for the *first* N instructions. > > (1) Is there any existing mechanism which I can leverage ? > There is a comInstEventQueue which I think is used to stop the > simulation after first N instructions. Can I somehow use this ? > > (2) If not, then where and what sort of modifications will I need ? I need > to do this for both CPU and AMD GPU. > > Thank you, > Rajeev Pal > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
