Re: [gem5-users] enum header file

2018-05-11 Thread Ciro Santilli
Immediately we suspect that the file is auto-generated during build. So we do a shell find in the output directory: ``` find . -name OpClass.hh ``` This leads us to: ./build/ARM/enums/OpClass.hh Open the file, look for interesting unique identifiers, and git grep that on main source. So: ```

[gem5-users] enum header file

2018-05-11 Thread Tariq Azmy
Some of cpu source codes include header files that begin with enum/.. such as: #include "enums/OpClass.hh" #include "enums/StaticInstFlags.hh" Where are these sources located so that I can see 'em? Thanks ___ gem5-users mailing list gem5-users@gem5.org

[gem5-users] gem5 gpu-compute tutorials

2018-05-11 Thread Yu Chao
Hi all, Is there any tutorials on the use of gem5 gpu-compute? I'm going to use the gpu-compute in gem5, but i cannot find any tutorials on how to use it.Thanks in advance. Regards, Chao ___ gem5-users mailing list gem5-users@gem5.org http://m5sim.or

Re: [gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread TungHoang_GMail
Ali, Did you use aarch64 cross compiler when compiling Parsec. By default, Parsec just supports x86 GCC. You will need to modify gcc.bldconf of Parsec to make use of aarch64. See ARM pdf file from my link. I do not have any problem with parsec. You can eventually try with Hello compiled by aa

Re: [gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread Hadouda Ali
i compiled and run parsec 3.0 in my linux operating system after i copied parsec in the linaro-minimal-aarch64.img image and i tried in gem5. 2018-05-11 18:44 GMT+02:00 TungHoang_GMail : > Ali, > > Have you statically compile PARSEC using aarch64-linux-gnu-gcc cross > compiler or qemu-aarch64 bef

Re: [gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread TungHoang_GMail
Ali, Have you statically compile PARSEC using aarch64-linux-gnu-gcc cross compiler or qemu-aarch64 before copying into disk-image file ? See helps in https://github.com/arm-university/arm-gem5-rsk /Tung On 05/11/2018 09:40 AM, Hadouda Ali wrote: hiĀ hoang; yes I did this step; I have upload

[gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread Hadouda Ali
hi hoang; yes I did this step; I have uploaded PARSEC 3.0 here is the download link: https://github.com/connorimes/parsec-3.0 and I followed these steps: *cp linaro-minimal-aarch64.img expanded-linaro-minimal-aarch64.img* *$ dd if = / dev / zero bs = 1G count = 20 >> ./expanded-linaro-minimal

Re: [gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread TungHoang_GMail
Ali, You need to provide disk image vi "--disk-image" option. And you also need to copy PARSEC (e.g. blacksholes) binary file into disk image file. The disk image file will be /media/ali/ali/gem5/aarch-system-20180409/disks. I suppose its name is "linaro-minimal-aarch64.img". To copy Parsec b

[gem5-users] kernel execution problem armv8 for mode fs_big.LITTLE

2018-05-11 Thread Hadouda Ali
hi all; I executed the armv8 kernel in big.LITTLE mode, I used the following command: sudo build / ARM / gem5.opt configs / example / arm / fs_bigLITTLE.py --kernel = / media / ali / ali / gem5 / aarch-system-20180409 / binaries / vmlinux.vexpress_gem5_v1_64 --dtb = / media / ali / ali / gem5 / aa

Re: [gem5-users] No working init found

2018-05-11 Thread Ciro Santilli
My setup works for both gem5 and QEMU with the same raw ext2 image. Don't forget to always reply to both me and the mailing list to share knowledge. On Fri, May 11, 2018 at 1:47 AM, Li Zhao wrote: > do you think there is any restriction on the disk image that Gem5 can > recognize? > when I use Q