You should not add it there. O3CPU.py defines the variables (processor
parameters in this case) with their default values.
You should add it to your se.py or fe.py. After you instantiate your
processor, you can set this up. Something like:
system.cpu[?].numROBEntries = option.robsize
(Actually thi
Thanks Tao and Amin. I am able to add options, but I am not able to assign
it to numROBEntries. I mean when I use this in O3CPU.py:
numROBEntries = options.robsize
it doesn't work, since options module is not defined here. I tried
importing options, but still didn't work. Can you elaborate on how
Hi,
I am also curious about how to create new options as well. The numRobEntries in
O3CPU.py you mentioned has the following:
"numROBEntries = Param.Unsigned(192, "Number of reorder buffer entries")"
How is this related to options.robsize as mentioned?
In addition, what if I were to add anoth
Take the following from config.ini file, my understanding is here we
defined 2 function units, both of them can execute IntMult and IntDiv
type of instructions, and opLat defines how many ticks need to execute
that instruction. Please correct me if my understanding is wrong.
My confusion comes
The last thing that Tao forgot to mention is to use options.robsize to set
the value of numROBEntries (numROBEntries is defined in
src/cpu/o3/O3CPU.py).
Amin
On Tue, Jul 16, 2013 at 5:06 PM, Tao Zhang wrote:
> Hi Mahshid,
>
> ** **
>
> You can use the “add_option” to add any desired option
Hi Mahshid,
You can use the "add_option" to add any desired options in the command line.
To do this, you just add the line below (or something like it) at the
beginning of your fs.py.
parser.add_option("-rob", "--robsize", type="int", default=128,
help="specify the rob size");
Then, af
Hello,
I want to introduce a new option to the simulation script to define the ROB
size, since I am doing experiments with different ROB sizes and would like
to skip the procedure of rebuilding the gem5 again and again for different
ROB sizes. Basically, I need to do a similar thing as the thread
Hi all,
I am running Parsec on X86 and trying to use dumpresetstats periodically.
Since I am using the precompiled Parsec binaries, I use the m5op
dumpresetstats for this purpose. I am using the command line:
../build/X86/gem5.opt
--outdir=../RUNS/2core_fastfwd_dumpstats/m5out_canneal
../configs/e
On 07/15/2013 04:36 PM, Ali Saidi wrote:
On 10.07.2013 06:24, Hui Zhao wrote:
Hello
I am running multithreaded applications on Gem5. I want to stop the
simulation when the sum of all cores' executed instructions reaches
some million. But the current -I n will stop when any core reaches the
n
