Hi Mike, I'm the one who wrote the initial version of the simpoint collection/generation a few years ago. I enforced the "fastmem" option primarily because I didn't see it necessary to simulate caches during simpoint generation and it made simulation faster. You can simply disable this and it should all still work.
For the "--cpu-type=atomic" option, initially simpoints were hardcoded directly into the atomic CPU. Since then, they've been changed to use the "probe" system. However, a quick grep of the code shows the initialization for the SimPoint probe only exists in the atomic CPU. If you registered the probe point with the TimingCPU as well, then that should work (I think). On Mon, Jan 12, 2015 at 5:02 PM, mike upton via gem5-dev <[email protected]> wrote: > I am trying to enable simpoint generation with kvm enabled. > > Is there anything that inherently blocks this? > > Simpoints are currently enabled only with --fastmem and --cpu-type=atomic. > How fundamental are each of these restrictions? > > Thanks, > > Mike > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
