I'm interested in the cache warm up overhead after thread migrated to other core. After the trigger of thread migration, it seems an easy way to measure this overhead is to reset the cache to initial state and continue execution.
Can we do this in gem5 and how to do it?

Thanks
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to