Actually, I intended to configure a ruby memory hierarchy with a mesh topology and full system support. I had no problem building "build/ALPHA_SE_MOESI_CMP_directory/m5.opt" at all.
But if I run "build/ALPHA_SE_MOESI_CMP_directory/m5.opt -re tests/run.py tests/quick/60.rubytest/ref/alpha/linux/rubytest-ruby-MOESI_CMP_directory -n 4 --topology=Mesh --mesh-rows=2", I would get the error of "assert(node.type == 'DMA_Controller')". I guess it might be due to that the FS model has the DMA module but SE model doesn't, since it is required that a DMA controller be attached to the node 0 in the mesh topology. So I tried to configure a ruby memory hierarchy with a mesh topology and FS support, and then I got the problems as described in previous emails. Sorry for posting the messages on m5-dev. Next time I will send my questions about the devel version of M5 on m5-users. Thanks, Leonard On Tue, Jan 11, 2011 at 11:00 PM, Gabe Black <[email protected]> wrote: > We should be discussing this on m5-users, and it's probably better to set > those parameters on the scons command line than in the file with the default > settings. If you run scons --help, or scons --help > build/ALPHA_SE_MOESI_CMP_directory/m5.opt in this case, it will print out > what setting it's using for those variables. The file you're modifying is > for the default values, and once those are in use I don't know exactly what > you need to do to get them to be read in again. > > Gabe > > > On 01/11/11 21:02, Sage wrote: > > Hi, Korey, > > Thanks for your reply. But even after I removed “InOrderCPU” from the > CPU_MODELS list and cleaned up the "build" folder, source files related to > the inorder model would still be compiled and the same errors would show up > again. > > Thanks, > Leonard > > > > On Tue, Jan 11, 2011 at 10:36 PM, Korey Sewell <[email protected]> wrote: > >> I'll check those errors out for you, but InOrder doesnt currently work in >> FS mode, so you would be OK to remove that from your build options if you so >> chose. >> >> On Tue, Jan 11, 2011 at 11:14 PM, Sage <[email protected]> wrote: >> >>> Hello, everyone, >>> >>> In the m5-dev version, I was trying to build >>> "ALPHA_FS_MOESI_CMP_directory" by just changing the >>> "ALPHA_SE_MOESI_CMP_directory" to the following script. >>> >>> FULL_SYSTEM = 1 >>> SS_COMPATIBLE_FP = 1 >>> CPU_MODELS = 'AtomicSimpleCPU,TimingSimpleCPU,O3CPU,InOrderCPU' >>> PROTOCOL = 'MOESI_CMP_directory' >>> RUBY = True >>> >>> >>> But I got the errors as follows when building it, which I believe >>> indicates certain bugs. >>> >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.cc: In member function >>> 'void InOrderCPU::processInterrupts(Fault)': >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.cc:633: error: >>> expected type-specifier before 'Impl' >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.cc:633: error: >>> conversion from 'int*' to non-scalar type 'ThePipeline::DynInstPtr' >>> requested >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.cc:633: error: >>> expected ',' or ';' before 'Impl' >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.cc:634: error: no >>> matching function for call to 'InOrderCPU::trap(Fault&, >>> ThePipeline::DynInstPtr&)' >>> build/ALPHA_FS_MOESI_CMP_directory/cpu/inorder/cpu.hh:344: note: >>> candidates are: void InOrderCPU::trap(Fault, ThreadID, >>> ThePipeline::DynInstPtr, int) >>> >>> >>> In line 633 of "src/cpu/inorder/cpu.cc", it complains that >>> "Impl::DynInst" is not a correct class name. The problem couldn't be worked >>> around by removing "Impl::". >>> In line 634 of the same file, only two variables are passed to the "trap" >>> function but apparently it needs another "ThreadID" type variable. >>> >>> >>> Since I am not quite familiar with the source code in the "cpu" folder, I >>> just raise my questions on the errors and hope someone can fix it. >>> >>> >>> >>> Thanks, >>> Leonard >>> >>> >>> -- >>> Give our ability to our work, but our genius to our life! >>> >>> _______________________________________________ >>> m5-dev mailing list >>> [email protected] >>> http://m5sim.org/mailman/listinfo/m5-dev >>> >>> >> >> >> -- >> - Korey >> >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev >> >> > > > -- > Give our ability to our work, but our genius to our life! > > > _______________________________________________ > m5-dev mailing [email protected]http://m5sim.org/mailman/listinfo/m5-dev > > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > -- Give our ability to our work, but our genius to our life!
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
