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,
In my program, I am needed to spawn and join a thread several hundred
times. Throughout the span of execution, there are two threads in total.
When I try to run my program I get following error --
*fatal: Out of memory, please increase size of physical memory.*
@ cycle 48472224
[allocPhysPag
Hi,
In my program, I am needed to spawn and join a thread several hundred
times. Throughout the span of execution, there are two threads in total.
When I try to run my program I get following error --
*fatal: Out of memory, please increase size of physical memory.*
@ cycle 48472224
[allocPhysPag
Hi all,
Instead of starting a new thread, I’d suggest to go ahead with the original
suggestion from this thread. The steps outlined should be enough to get you
going. Regarding the SW side of things it is not gem5 specific, as you would
have to get the OS to understand the implications.
Andrea
Hi Simon,
We already have a scratch pad memory for the compute GPU model
(src/gpu-compute/). Take a look at the LDS code and how the Compute Unit code
uses it. That should give you an idea how to implement a scratch pad for the
CPUs.
From: gem5-users on behal
Hello everyone,
I am new to the Gem5, so I got some questions about how to simulate a SPM in
gem5:1.The reason why I want to simulate a ScratchPad Memory in gem5 is that I
want to study some algorithm performance on the same data in the different
position. My plan is replacing the L1 DCache/ICac
Hi,
sorry it was 512MB the mem-size = 512 MB in build commands.
best regards,
Sharjeel
On 11 February 2017 at 15:33, SHARJEEL KHILJI wrote:
> HI,
> Thanks for your help, I have tried to figure out where is that
> uninitialized stat. Actually the assertion fails in safe_cast function in
> cast
HI,
Thanks for your help, I have tried to figure out where is that
uninitialized stat. Actually the assertion fails in safe_cast function in
cast.hh which is further called in prepare() in Statistics.h. I can not
figure out where is the list of all stats is populated and where is
prepare() is calle