-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/277/#review419
-----------------------------------------------------------



src/mem/protocol/MESI_CMP_directory-L2cache.sm
<http://reviews.m5sim.org/r/277/#comment620>

    It looks like this call goes over 80 chars on the first line, and then uses 
up a lot of unnecessary lines by taking up a whole line for each arg.  If you 
want to keep the verbose labels, you should format it like this:
    
    DPRINTF(RubySlicc, "Address: %s, L2 Cache State: %s, Sender: %s, "
            "Response Type: %s, Destination: %s",
            in_msg.Address, getState(in_msg.Address), in_msg.Sender,
            in_msg.Type, in_msg.Destination);
    
    though my inclination would be to save more space by abbreviating or even 
eliminating some of the labels in the format string (since most of the fields 
will be self-evident, and they'll get pretty tiring in the trace output too, I 
expect).
    


- Steve


On 2010-10-25 07:54:18, Nilay Vaish wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.m5sim.org/r/277/
> -----------------------------------------------------------
> 
> (Updated 2010-10-25 07:54:18)
> 
> 
> Review request for Default and Ruby Reviewers.
> 
> 
> Summary
> -------
> 
> Ruby currently uses GEMS debug support with the enum character string map to 
> enable certain debug messages.  Meanwhile, M5 has debug print support that 
> works with scons. Compiling the m5.fast binary, the M5 debug statements are 
> removed, but the Ruby ones are not unless RUBY_DEBUG is not defined. This 
> patch moves Ruby to M5's debug print support.
> 
> 
> Diffs
> -----
> 
>   src/cpu/testers/rubytest/CheckTable.cc f166f8bd8818 
>   src/mem/SConscript f166f8bd8818 
>   src/mem/protocol/MESI_CMP_directory-L1cache.sm f166f8bd8818 
>   src/mem/protocol/MESI_CMP_directory-L2cache.sm f166f8bd8818 
>   src/mem/protocol/MESI_CMP_directory-dir.sm f166f8bd8818 
>   src/mem/protocol/MI_example-cache.sm f166f8bd8818 
>   src/mem/protocol/MI_example-dir.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_directory-L1cache.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_directory-L2cache.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_directory-dir.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_directory-perfectDir.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_token-L1cache.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_token-L2cache.sm f166f8bd8818 
>   src/mem/protocol/MOESI_CMP_token-dir.sm f166f8bd8818 
>   src/mem/protocol/MOESI_hammer-cache.sm f166f8bd8818 
>   src/mem/protocol/MOESI_hammer-dir.sm f166f8bd8818 
>   src/mem/ruby/SConsopts f166f8bd8818 
>   src/mem/ruby/buffers/MessageBuffer.cc f166f8bd8818 
>   src/mem/ruby/common/Debug.hh f166f8bd8818 
>   src/mem/ruby/common/Debug.cc f166f8bd8818 
>   src/mem/ruby/common/NetDest.hh f166f8bd8818 
>   src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc 
> f166f8bd8818 
>   src/mem/ruby/network/garnet/fixed-pipeline/Switch_d.cc f166f8bd8818 
>   src/mem/ruby/network/garnet/flexible-pipeline/NetworkInterface.cc 
> f166f8bd8818 
>   src/mem/ruby/network/garnet/flexible-pipeline/Router.cc f166f8bd8818 
>   src/mem/ruby/network/simple/PerfectSwitch.cc f166f8bd8818 
>   src/mem/ruby/network/simple/Throttle.cc f166f8bd8818 
>   src/mem/ruby/network/simple/Topology.cc f166f8bd8818 
>   src/mem/ruby/storebuffer/storebuffer.cc f166f8bd8818 
>   src/mem/ruby/system/CacheMemory.cc f166f8bd8818 
>   src/mem/ruby/system/DirectoryMemory.cc f166f8bd8818 
>   src/mem/ruby/system/SConscript f166f8bd8818 
>   src/mem/ruby/system/SparseMemory.cc f166f8bd8818 
>   src/mem/ruby/tester/RaceyPseudoThread.cc f166f8bd8818 
>   src/mem/slicc/ast/FuncCallExprAST.py f166f8bd8818 
>   src/mem/slicc/symbols/StateMachine.py f166f8bd8818 
> 
> Diff: http://reviews.m5sim.org/r/277/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Nilay
> 
>

_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to