Ali,
Oops -- I had added the max_inst option that to se.py for some reason.
Here's a new (hopefully complete) diff.
-Vilas
On Fri, Feb 15, 2008 at 3:05 PM, Ali Saidi <[EMAIL PROTECTED]> wrote:
> Hi Vilas,
>
> Are the diffs complete? The max_inst option never appears in
> Options.py but it's
Hi Vilas,
Are the diffs complete? The max_inst option never appears in
Options.py but it's used in Simulation.py
Thanks,
ali
On Feb 15, 2008, at 2:00 PM, Vilas Sridharan wrote:
As an aside, if you want to fast forward 300M instructions and not
necessarily 300M cycles, it would be good to
> As an aside, if you want to fast forward 300M instructions and not
> necessarily 300M cycles, it would be good to be able to specify that
> directly... didn't we just have a thread on the mailing list about
> that? I don't think it's in the code right now, but did someone out
> there add it? If
But that won't create a checkpoint at 300M instructions, although
using that with a modified Simulation.py could result in the
checkpoint being generated.
Ali
On Jan 26, 2008, at 11:50 AM, Korey Sewell wrote:
I believe there was a thread about max instructions but that was in
reference to
I believe there was a thread about max instructions but that was in
reference to running simulations with multiple threads or instruction
streams.
If this is just a single-threaded simulation, I think he can just
specify "max_insts=X" on the command line to get his desired effect of
stopping at 30
First you might want to talk to Rick Strong about this a little bit,
since he has been doing the same thing and he might have added
parameters that take an instruction count to checkpoint on (also you
should make sure that you've patched your tree with the various
patches that have been pos
The basic clock rate is 1 ps (1 THz). I think you really want (1
THz/1 Ghz) * 300M, which would be 3x10^11 not 3x10^17 ticks.
As an aside, if you want to fast forward 300M instructions and not
necessarily 300M cycles, it would be good to be able to specify that
directly... didn't we just have a t
hi everybody,
this is my first time to fast forward instructions using
AtomicSimpleCPU. I want to fast forward to 300M instructions (for gzip
graphic-ref) so I fast forward to (1Ghz * 300M= 3x10^17 ticks), its now
been simulating for 29hrs now and I decided to attach 'm5term' and it
says "11