dibakar gope wrote: > Hi Gabe, > > Thanks. Do you mean that X86 is working for SimpleCPU(both atomic & > timing) model for syscall emulation mode, but not for full simulation > O3CPU model? >
I know it's working in both atomic and timing mode SimpleCPU in syscall emulation mode and in the atomic mode SimpleCPU in full system. I think it's also working in the timing SimpleCPU in full system now too, but that was fixed fairly recently and I'm not 100% certain that's in the repository. If I had to guess I'd say it is. I does not work for the other CPU models (O3 InOrder) in either syscall emulation or full system modes. > The other issue is, I am trying to build the X86 disk-image for FS > run. In order to compile the linux kernel for X86, I got the configs > from your earlier posts. The steps I followed in order to make the x86 > disk image using PtxDIST:- > (1) clone the linux-dist/projects-example/generic-i586-glibc project > in a particular workspace & select this ptxconfig > (2) select a possible h/w platform to build for. I selected the > platform-i586. This platformconfig lets me set up all target specific > settings.Major parts are: > • Toolchain (architecture and revision) > • boot loader > • root filesystem image type > • Linux kernel > (3) select the toolchain to be used to build everything for the target > /opt/OSELAS.Toolchain-1.99.3/i586-unknown-linux-gnu/gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/bin/ > > then PtxDist go command builds everything & PtxDist image command make > the final disk-image. > > BUT, the disk image it made for me is of size 150 MB only. It should > be about 2GB. I guess definitely the image has not been built > properly. I am getting following error messages using that built x86 disk > image. > > command-line:-build/X86_FS/m5.opt configs/example/fs.py > --kernel=/dist/m5/system/binaries/vmlinux > > Global frequency set at 1000000000000 ticks per second > info: kernel located at: /dist/m5/system/binaries/vmlinux > 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012 > Listening for pc connection on port 3456 > warn: Reading current count from inactive timer. > For more information see: http://www.m5sim.org/warn/1ea2be46 > 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > panic: Segment not present. > @ cycle 10000 > [execute:build/X86_FS/arch/x86/atomic_simple_cpu_exec.cc, line 8476] > Memory Usage: 262956 KBytes > For more information see: http://www.m5sim.org/panic/bc153f92 > Program aborted at cycle 10000 > Aborted > > Now I am trying with BusyBox, instead of PtxDIST. Is there any other > way that you can suggest me for building the image?please let me know. > I haven't used PtxDIST myself and don't know what you'd need to do to get it to work, but using a Gentoo image has generally worked out. You'll probably want to use a 64 bit kernel as well which may be the source of the error you're seeing. Gabe _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
