2 is
active for less cycles than CPU 3. This would indicate to me that the
application just isn't running on CPU 2 for the time you expect it to be.
Jason
On Mon, Feb 13, 2017 at 10:05 AM Alsuwaiyan, Ali Saleh
mailto:as...@pitt.edu>> wrote:
Dear all,
I ran a full system simulation wit
Hi everyone,
The -I option (or --maxinsts) of the fs.py script specifies
the max number of committed instructions. Assuming
a multicore system, this option works as follows: if any
core commits this number of instructions, the simulation
stops.
I need to change this behavior to the followin
Dear all,
I ran a full system simulation with four cores CPU, in which each core is
hardcoded (using taskset command) to run a specific SPEC CPU2006 benchmarks
(leslie3d, leslie3d, mcf, and mcf). The architecture of the simulated system
can be inferred from the simulation command below:
build/
Hi all,
I compiled the latest revision of gem5.fast (rev 11830) for X86 (with
-Wno-error CCFLAGS to avoid unused-vars being treated as error). Then I tried
full system simulation using the following command:
build/X86/gem5.fast configs/example/fs.py --caches
--disk-image=linux-x86-large.img
Hi everyone,
Is there any tutorial on how to use KVM with gem5, especially for X86?
I'm asking because I need to perform a lot of gem5 full system simulation runs
with detailed cpu-type and with NVMainMemory as a memory controller. Using a
regular non-KVM gem5 image, only 10M instructions wit
gt;).
My scripts fast-forward with KVM instead of restoring from a checkpoint, but
the skeletons for the code are similar either way.
Let me know if you have more questions.
Jason
On Thu, Feb 2, 2017 at 5:41 AM Alsuwaiyan, Ali Saleh
mailto:as...@pitt.edu>> wrote:
Hi everyone,
I'
Hi everyone,
I'm relatively new to gem5 and came across a problem where I need to perform
the following:
1. reset the stats and checkpoint, both after 10M instructions
2. restore the checkpoint with detailed CPU type and run for 1B instructions
then stop
The problem is that both resetstats