Hi,
This helped me to create a 16GB disk image:
https://www.mail-archive.com/gem5-users@gem5.org/msg09928.html
Best
Jae-Eon
2014-10-01 16:33 GMT+09:00 babak aghaei via gem5-users
:
> Hi M.Y.
> You must change the disk image size with /gem5/util/gem5img.py as you want.
> I hope that help you.
>
Hi Edward,
1) In configs/example/se.py or fs.py, you can directly manipulate the
parameters.
Find
(CPUClass, test_mem_mode, FutureClass) = Simulation.setCPUClass(options)
And append
CPUClass.branchPred.localCtrBits = 4
Note that FutureClass should be used instead of CPUClass if you're
fas
the bus busy also leads
>> to cpu’s fatal error. So maybe I need a directory protocol between L1 and
>> L2. That’s why I want to have a try at the ruby system.
>>
>> So can I get a cache system which has a snooping protocol between the
>> multiple-cpu and l1 and a direc
tween L1 and
>> L2. That’s why I want to have a try at the ruby system.
>>
>> So can I get a cache system which has a snooping protocol between the
>> multiple-cpu and l1 and a directory protocol between L1 and L2 in ruby
>> system? What’s your comment to implement my
ping protocol between the
> multiple-cpu and l1 and a directory protocol between L1 and L2 in ruby
> system? What’s your comment to implement my design?
>
> Thanks a lot for your response.
>
> Chao
>
> On Sep 18, 2014, at 9:48 AM, Jae-Eon Jo via gem5-users <
> gem5-users@gem5.
Hi, Chao,
As far as I know, each protocol of Ruby is tightly coupled with the memory
hierarchy.
That is, you should modify the protocol implementation
(src/mem/protocol/MESI_Two_Level*) to change the memory hierarchy, which is
not trivial.
My recommendation is to use the classic memory system (th
Hi,
1. If you stick to use SE mode to run Parsec, which relies on pthread,
m5threads library should be linked statically instead of pthread.
https://www.mail-archive.com/gem5-dev@m5sim.org/msg07129.html
2. You can use Ruby with SE mode.
https://www.mail-archive.com/gem5-users@gem5.org/msg00202.ht
Dear all,
I'm trying to simulate PARSEC 2.0 workload using gem5 (x86, linux smp
version, FS mode).
As I need to change cache coherence protocol and topology, Ruby is used
instead of classic memory system.
However, with this setting I had several problems.
1. Cannot use atomic CPU, which is useful
