Looking a little more closely, this paragraph below refers to you config_as_param patch and not the tester_dma_extension patch that started off this thread. It was long enough ago that they got blurred in my mind. Sorry for the confusion. The question still stands though; in fact, with respect to that config_as_param patch, I'm interested in knowing more about how the Ruby config file gets specified currently (i.e., I don't really understand the problem that patch is trying to fix).
Steve On Fri, Sep 4, 2009 at 12:25 PM, Steve Reinhardt<[email protected]> wrote: > Another question I have is whether the DMA Sequencer really does > anything different from a CPU Sequencer, and what set of Ruby memory > configurations should be added to the regression test. Note that the > code in the tests directory is really only for regression tests, i.e., > things we want to run regularly and automatically and verify that the > detailed statistics have not changed. Certainly when I was working on > the M5 coherence protocol I ran far more tests (longer and more > varied) with MemTester than the one simple instance that's in the > regressions. I'm not clear on whether you're just trying to set up a > test for the DMA Sequencer for debugging purposes (which should be an > easy change to a config script somewhere) or trying to set up a test > to include in the regressions (which we generally only do once that > test is working outside the regressions). _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
