Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hi, Trivikram, Do you maintain this Repo now, I have one issue? #10

Open
cyberspicecai opened this issue Apr 18, 2022 · 2 comments
Open

Comments

@cyberspicecai
Copy link

cyberspicecai commented Apr 18, 2022

Hi, Triv
I follow the script in your repo and prepare one self-contained testing disk image and find some strange error.
I write the steps:
1,checkout the branch V20.1 of Gem5, and compile it as in launch_spec2006_experiments.py
scons build/X86_MESI_Two_Level/gem5.opt --default=X86 PROTOCOL=MESI_Two_Level SLICC_HTML=True -j8
2, I prepare the linux kernel and disk image as the official document. sure your script also shows the steps.
3, I modified the script run_mysql_fs.py
run_mysql_fs.py.txt
as shown in the attached.(and I modify the ruby_system.py slightly and add one "." for cache, core, fs_tools, otherwise will show "module not found errors")
4, and run the cmd in shell will the error will pop out :
build/X86_MESI_Two_Level/gem5.fast configs/gem5-configs/run_mysql_fs.py /data/gem5-skylake-config/gem5v20/vmlinux-4.19.83 /data/gemv20image/mysql_8p23_ubuntu1804_gem5_16_warehouse_bk_2022_4_13.img Tuned MESI_Two_Level

fatal: Number of ISAs (0) assigned to the CPU does not equal number of threads (1).
5, and I search the error above and find that one reason is createThreads() issue. But I check the code and find the script has this operation:map(lambda c: c.createThreads(), self.cpu).

 Pls help check this issue.

 Thanks a lot .
 Cyberspice.
@powerjg
Copy link
Member

powerjg commented Apr 18, 2022

Unfortunately, I don't think this repo is maintained. I can do my best to answer your questions, though!

That error is definitely because somewhere is missing the createThreads(). It's probably the KVM CPUs whose threads are not being created.

It may be easier to start with the new x86 board in the standard library (https://www.gem5.org/documentation/gem5-stdlib/overview) which was released in 21.2 (a much more recent version of gem5). This board is tested every night with mainline gem5, so it should be working. It should work with the same disk image you're using now.

@cyberspicecai
Copy link
Author

Hi, Jason,
Thanks for your kindly reply.
I am checking your recommendation. I will feedback soon.
BR
Cyberspice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants