Hi：
I have more question:
Can I run a program with dynamic link on SE?
My host machine is aarch64, and my program is also an aarch64 ELF,
the program can find all library on this host machine according to the result
of “ldd”.
发件人: RTL Insn via gem5-users [mailto:[email protected]]
发送时间: 2022年1月26日 14:07
收件人: gem5 users mailing list <[email protected]>
抄送: RTL Insn <[email protected]>
主题: [gem5-users] Re: Multithread simulation using gem5 SE mode
It is not possible to run a multithreaded program in Gem5-SE mode as you need
an operating system that handles the threads at kernel level. So, full-system
mode should be used for running any multithreaded programs.
On Wed, Jan 26, 2022 at 3:40 AM Andronicus Samsundar Rajasukumar via gem5-users
<[email protected]<mailto:[email protected]>> wrote:
Hi,
I'm trying to run a multithreaded c++ application in SE mode using O3 CPU +
classic caches + DRAMSim3.
The single thread version of this application runs correctly producing desired
results.
When I increase the number of threads, I see indeterministic behavior in the
simulations.
I've gone through many of the queries sent before about simulating
multithreaded applications and it looks like the SE mode isn't best suited to
do this. Is this true in the latest 21.2 release as well?
Can I use FS mode for a system with O3CPU+classic caches+DRAMSim3 to test
multithreaded/multicore applications? I also noticed that it was mentioned in
one of the posts that classic caches do not support multicore simulation. If
that is the case, what would be the best methodology to simulate such a system.
Thank you,
Andronicus
_______________________________________________
gem5-users mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to
[email protected]<mailto:[email protected]>
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
