60 likes | 165 Vues
Join Paul E. West as he discusses his progress on running multiprocessor systems with M5 simulation, focusing on challenges with cycle counts, caches, and running different programs on each core. Explore the process of compiling and running Full System on M5, with insights into system calls and boot image creation.
E N D
M5 – a <5 min. update that will be stretched to 15 min. Paul E West
Where other people are at • Trying to get traces to work (on multipcore) • Can run muilt-processor, but problems like cycle count. • Can run different programs on each core. • Other people are trying to modify the caches. • Some success on running Splash-2
Where Paul is at • System call level? • Full System runs (on summit). • To run in Full system mode, a boot image must be created. This boot image requires a kernel. • I got the kernel to compile, but then I had to write this presentation... (excuses, excuses)
Compiling/Running FS • All of this is on M5's website • To compile: '% scons build/ALPHA_FS/m5.opt' • (That should already be done) • Edit System settings: 'vim configs/common/SysPaths.py' • Run the simulation: './build/ALPHA_FS/m5.opt configs/example/fs.py -b NetperfMaerts' • Connect with m5term (Not installed yet...) • Do it.
Comments on m5term • Again, I'll hopefully have it installed today. • It appears that logging in through m5term is what starts the full system simulation. • Very minimal shell • Yes, load up is long. It almost appears to hang.
The End • Questions? Comments? Screams of angst?