I found a couple of bugs in ruby. Both of them deal with the size of the address space in ruby. I have posted a patch for one them on the review board. The other bug deals with setting of the physical address space size for ruby. As of now, it is simply set to the size of the physical memory in the system. I think this works correctly only when the physical memory starts from address 0 and is contiguous. I think this is not true for x86 architecture where the address space from 3GB to 4GB is reserved for devices. Physical memory larger than 3GB has to be mapped in a discontinuous fashion. As a solution, I think we should let ruby be aware of the entire address space that exists in the system. There is check in RubyPort class which prevents ruby from touching addresses belonging to the io address space.
-- Nilay _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
