> On May 18, 2012, 6:09 a.m., Nilay Vaish wrote: > > configs/common/FSConfig.py, line 311 > > <http://reviews.gem5.org/r/1191/diff/1/?file=26300#file26300line311> > > > > I would prefer if we can just make amends to the existing function for > > classic memory system to support Ruby as well, instead of this entire new > > function.
So pretty much mimic how Ruby is setup with X86 instead of Alpha? > On May 18, 2012, 6:09 a.m., Nilay Vaish wrote: > > src/dev/arm/RealView.py, line 222 > > <http://reviews.gem5.org/r/1191/diff/1/?file=26302#file26302line222> > > > > Why do we need these new functions? Can't we make changes to the > > existing ones? Yes, just need to pass in an unattached bridge to the attachOnChipIO function when using Ruby. Same can be said with the attachIORuby function...adding the dma_ports array. - Andrew ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/1191/#review2707 ----------------------------------------------------------- On May 12, 2012, 4:36 p.m., Andrew Cebulski wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1191/ > ----------------------------------------------------------- > > (Updated May 12, 2012, 4:36 p.m.) > > > Review request for Default. > > > Description > ------- > > These are the changes I made to get ARM FS working with Ruby. Most notably, > I had to make the memory contiguous by putting the physmem and nvmem > together, otherwise Ruby would not handle them correctly. Details here on > the mailing list: > http://permalink.gmane.org/gmane.comp.emulators.m5.users/10440 > > This required shrinking physmem from 256MB to 172MB, then placing nvmem at > address 172MB. Next, the boot loader has to be recreated with the Makefile > under the system directory, changing the address to 0x0C000000. > > Hopefully, at the very least, this will help others start testing out ARM FS > with Ruby. > > > Diffs > ----- > > build_opts/ARM_MESI_CMP_directory PRE-CREATION > build_opts/ARM_MOESI_CMP_directory PRE-CREATION > build_opts/ARM_MOESI_CMP_token PRE-CREATION > build_opts/ARM_MOESI_hammer PRE-CREATION > configs/common/Benchmarks.py f681719e2e99 > configs/common/FSConfig.py f681719e2e99 > configs/example/ruby_fs.py f681719e2e99 > src/dev/arm/RealView.py f681719e2e99 > system/arm/simple_bootloader/Makefile f681719e2e99 > > Diff: http://reviews.gem5.org/r/1191/diff/ > > > Testing > ------- > > Currently, I've tested this successfully with the SPEC CPU2006 libquantum > benchmark with the Timing CPU. I'm still running tests with the ARM O3CPU. > They seem to be hanging during boot at "sched_clock: 32 bits at 24MHz, > resolution 41ns, wraps every 178956ms". Note that I have not tested this > with Android, only Ubuntu. > > > Thanks, > > Andrew Cebulski > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
