Hi Prakhar, A standard solution to 1 would be to use M5ops: https://www.gem5.org/documentation/general_docs/m5ops/. That small library enables you to call magic functions from your guest binary that will trigger events in the host simulation environment. Namely, the dumpresetstats op will likely do what you want.
As for 2, from what I know, each new SW thread statically maps to a HW thread (aka CPU core) until all CPUs are running a thread. At that point, you can’t spawn any extra SW threads. In particular, there is no thread scheduling in the sense of context switching support in SE mode and you can’t over commit your simulated platform with more SW threads than you have CPU threads. Best, Gabriel
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
