Hello again, I am having some problems with the execution of a simple
Hello World program in FS, I have been executing the program 20
minutes and I do not get the output so I believe that something is
going wrong. This is what I did I copied a HelloWorld program that
works in SE mode to
Since you have changed the name/location of your disk image - did you change
the simulator to actually point to it and use it?
Lisa
On Thu, Nov 20, 2008 at 3:12 PM, Eduardo Olmedo Sanchez
[EMAIL PROTECTED]wrote:
Hi Ali thanks for your answer, it says that it could not find the file
loading
Hi Lisa thanks for your answer, in the config.ini generated by the
simulator it is ponting right to the img path.
image_file=/m5-fs/disks/linux-latest.img
In the disk folder there are two imgages I only made changes to the
linux-latest, which one is the simulator using linux-latest or
On Tue, Nov 11, 2008 at 12:28 AM, srimugunthan dhandapani
[EMAIL PROTECTED] wrote:
hi,
Can somebody share the python script file to do the sampling for switching
between CPU models periodically
for the following way of simulation
hi,
I am trying to solve the problem but can't...
Where to change 12 ?... please specify the file name where this values
(opcode latency of square root) is stored .
thank you,
devraj
On Tue, Nov 18, 2008 at 11:48 AM, Rick Strong [EMAIL PROTECTED] wrote:
From my experience, this error
hi everyone,
I have encountered a problem while simulating a configuration(.py) file.
The error message is as:
*m5.opt: build/ALPHA_SE/mem/bus.cc:225: bool Bus::recvTiming(Packet*):
Assertio n `dest = 0 dest maxId' failed. *
what would be the problem with it..?
Help please!!
Thank you,
You are missing a #!/bin/sh at the top of your rcS file.
Yes, the disk image size shouldn't change. The disk image file is
always exactly the size of the disk that it represents. So, if you
want a 100GB disk, the image file would be 100GB. Some day, I'll add
the qemu qcow2 format, but not
Sorry for the late response, but there really isn't another disk
model. You should in theory be able to hang the disk device off
whatever bus memory hangs off of. You only need an io cache if you
want a separate IO bus.
Nate
On Wed, Nov 19, 2008 at 4:21 PM, Rick Strong [EMAIL PROTECTED]
Actually that's not true... you need an io cache to make sure block
writes are coherent regardless of where the device is attached. The
device by itself doesn't know how to make coherent accesses.
Steve
On Thu, Nov 20, 2008 at 7:51 PM, nathan binkert [EMAIL PROTECTED] wrote:
Sorry for the late