Hi Mike,
When you say KVM enabled, I presume you mean running the KvmCPU? As Mitch
points out the problem is that you need something to attach the SimPoint
probe to, and the KvmCPU does not have that functionality.
Andreas
On 13/01/2015 00:36, Mitch Hayenga via gem5-dev gem5-dev@gem5.org
wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2546/#review5750
---
I suspect I am the only one annoyed by this...unless someone else feels
On Jan. 13, 2015, 10:53 p.m., Andreas Hansson wrote:
I suspect I am the only one annoyed by this...unless someone else feels the
same I will discard the patch.
If this is what I think it is, it can be pretty annoying when running
regressions. The param stuff swamps the console and its
On Jan. 13, 2015, 10:53 p.m., Andreas Hansson wrote:
I suspect I am the only one annoyed by this...unless someone else feels the
same I will discard the patch.
Gabe Black wrote:
If this is what I think it is, it can be pretty annoying when running
regressions. The param stuff
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2603/
---
Review request for Default.
Repository: gem5
Description
---
Changeset
Oh, Bummer.
I was hoping to be able to get simpoints out of a KvmCPU run.
It seems like that is not possible.
Is it possible to generate checkpoints using the KvmCPU?
If so, I can run the benchmark once with the kvm, generating checkpoints
every N billion instructions.
I can then run each of
That is doable. You can created checkpoints, there is just no way to
instrument every basic-block.
Ali
On 1/13/15, 3:13 PM, mike upton via gem5-dev gem5-dev@gem5.org wrote:
Oh, Bummer.
I was hoping to be able to get simpoints out of a KvmCPU run.
It seems like that is not possible.
Is it
