Hi Everyone, There has been quite a lot of people asking about Ruby on ARM for a while, so I thought I’d have a quick look to see how much work it would take to get it up and running. It turns out that getting a single-core system up and running wasn’t all that hard. I have just posted a series of patches that implement all the Ruby and configuration changes needed to get it to work:
• ruby: Implement support for functional accesses to PIO ranges [1] • arm, dev: Add support for listing DMA ports in new platforms [2] • arm, config: Add initial support for Ruby [2] • ruby: Size the MI_example directory to cover all phys mem [3] Keep in mind that Ruby on ARM still doesn’t /really/ work. I’m mainly posting them to get feedback from people with Ruby experience. There are currently a few big limitations that I’m aware of: 1. Only the new VExpress_GEM5_V1 platform is supported. 2. Multiple CPUs are not supported. (Yes, really!) 3. We can’t assume that memory starts at zero in most cases, which breaks assumptions in Ruby. We currently work around it by making the directories in Ruby cover all physical memory (see the last patch below) I don’t know exactly what’s breaking multi-core at the moment, but I suspect there might be issues related to uncacheable accesses or potentially exclusive monitors. Please let me know if you think you know what’s causing it. Cheers, Andreas [1] http://reviews.gem5.org/r/3575/ [2] http://reviews.gem5.org/r/3576/ [3] http://reviews.gem5.org/r/3577/ [4] http://reviews.gem5.org/r/3578/ IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
