Hi Ali and GEM5 Users
I have tried again and could boot both ALPHA and X86, as follows:
> Time to shell prompt at ALPHA: 0m38.826s (running on [Intel i7
Extreme]@[3.33GHz+16GB RAM])
$ cd /home/user/gem5; export M5_PATH=/home/user/gem5; time
./build/ALPHA/gem5.opt --outdir=/tmp/output ./configs/e
Hi Ali
I am a very new user and after your answer I tried the following
simulations:
1) I have tried to simulate X86 boot in FS mode using --cpu-type=atomic all
the time, and running only a "hello program", for 1165m59.515s with no
success or any error message.
2) I have also tried to simulate A
Hi, Romulo.
It is the problem with X86.
Anderson
On Mon, Jul 23, 2012 at 12:22 AM, Romulo Curty Cerqueira wrote:
> Hi Anderson
>
> I think that now I understand your question because I have tried to
> simulate the "hello" test program (that comes with GEM5) using gem5.opt for
> the first time a
Hello
Please As I am trying to run X86 FS from a long time and i am blocked
So I have some questions:
Do you type any commands (e.g. for mounting the disk image) before starting
booting (build/X86/gem5.opt configs/example/fs.py
--kernel=x86_64-vmlinux-2.6.
22.9.smp --cpu-type=detailed --l2cache --c
A: ... Normally people boot linux with a atomic simple CPU, take a
checkpoint and then switch to the O3 cpu to run their application of
interest.
..., so it seems like there is something wrong on your end.
Ok. I will do that boot and check my end.
Thank you Ali :-)
On Mon, Jul 23, 2012 at 12:3
All models should boot in <1h, although there is no particularly good reason to
boot the OS with the O3 cpu. Normally people boot linux with a atomic simple
CPU, take a checkpoint and then switch to the O3 cpu to run their application
of interest.
We have regression tests that run weekly using
Hi Anderson
I think that now I understand your question because I have tried to
simulate the "hello" test program (that comes with GEM5) using gem5.opt for
the first time at FS Alpha and FS x86, and the surprising results are:
Architecture Simulation Time(*)
-
Hi Anderson
Q.: I really want to understand: why doesn't a configuration with 4 O3CPU
boot the system? But other works fine.
A.: It seems a problem related to x86 simulation and I don´t use to do
that, but make sure that it doesn´t work with both 32 and 64 bit kernels as
a way to try to isolate t
Hi, Romulo.
I didn't explain correct my problem, in my last message. There is no
problem with ALPHA.
But, X86 doesn't boot with 4 O3CPU, the other cpus work fine, but 03CPU
doesn't.
Yesterday, I started a boot:
build/X86/gem5.opt configs/example/fs.py
--kernel=x86_64-vmlinux-2.
Hi, Romulo.
I didn't explain correct my problem, in my last message. There is no
problem with ALPHA.
But, X86 doesn't boot with 4 O3CPU, the other cpus work fine, but 03CPU
doesn't.
Yesterday, I started a boot:
build/X86/gem5.opt configs/example/fs.py
--kernel=x86_64-vmlinux-2.
Hi Anderson
Because of Alpha was the basis architecture for M5, I suppose it is also
valid for any cpu architecture:
(from FAQ at
http://www.m5sim.org/Frequently_Asked_Questions#How_many_CPUs_can_M5_run.3F)
How many CPUs can M5 run?
- There is no inherent limit in M5 (other than simulation s
The boot process works fine until 4 cpus (in my case O3CPU), in X86 and
ALPHA.
But when I used more than 4, the boot don't finish (in X86 and ALPHA).
I used the last gem5-stable version, and the last gem5 avaliables.
The last time that I tried to boot 8 03CPU, the boot took 15 hours to boot
only
On Fri, 13 Jul 2012, Anderson Faustino wrote:
Hi,
I'd like to boot a 03CPU on X86-FS, but the boot stops with the messages:
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
SMP alternatives: switching to UP code
Freein
Hi,
I'd like to boot a 03CPU on X86-FS, but the boot stops with the messages:
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
SMP alternatives: switching to UP code
Freeing SMP alternatives: 34k freed
--
14 matches
Mail list logo
