cirosantilli2 / issues

Hello! If you have anything to say to me, feel free to open an issue, and I will reply. For gem5 issues, prefer asking on Stack Overflow or the mailing list: https://www.gem5.org/mailing_lists/ or: https://github.com/cirosantilli2/gem5-issues
1 stars 0 forks source link

gem5gpu_fs mode_running benchmark #22

Open twilight1996 opened 2 years ago

twilight1996 commented 2 years ago

Hi I hope you are well I ran this command : ./build/X86_VI_hammer_GPU/gem5.opt configs/example/fs.py --kernel=/home/gem5gpu/base/gem5/binaries/vmlinux-5.4.49 --disk-image=/home/gem5gpu/base/gem5/disks/x86root.img and I saw this error: warn: instruction 'fninit' unimplemented stack smashing detected : terminated Program aborted at cycle 3915499000 Aborted (core dumped) (also i update m5 path to gem5 directory)

would you please if you know what i should do, tell me I stopped at this step thanks regard twilight

cirosantilli2 commented 2 years ago

Hi, I don't know about that instruction in particular, but the general solution algorithm for missing instruction is that there are three options:

The first step is to find the exact place in the kernel source code that is running the instruction. This will allow you to understand if you can afford to skip it somehow or not, and possibly how. This is possible by logging the instructions, then looking at the address of the blowup, and comparing that with the kernel binary. I forgot exact options, but wasn't hard. You then likely want gdb disas. A helper at: