[Gems-users] How to understand the dump-stats?

[sun xihuang <sxhshare@xxxxxxxxx>]

Hello,
        I'm new to simics and gems and now I have some problems when analyzing the dump-stats result. Any useful help will be appreciated.

1. when I try to understand the network topology by analyzing the network latencies,I find it hard to understand for me.For example,when I set the topology as HIERARCHICAL_SWITCH,I get some the topology print like this:
   L1Cache-0 Network Latencies
     L1Cache-0 -> L1Cache-1 net_lat: 9
     L1Cache-0 -> L1Cache-2 net_lat: 9
     L1Cache-0 -> L1Cache-3 net_lat: 9
     L1Cache-0 -> L2Cache-0 net_lat: 9
     L1Cache-0 -> L2Cache-1 net_lat: 9
     L1Cache-0 -> L2Cache-2 net_lat: 9
     L1Cache-0 -> L2Cache-3 net_lat: 9
     L1Cache-0 -> Directory-0 net_lat: 9
     L1Cache-0 -> Directory-1 net_lat: 9
     L1Cache-0 -> Directory-2 net_lat: 9
     L1Cache-0 -> Directory-3 net_lat: 9
   
   L1Cache-1 Network Latencies
     L1Cache-1 -> L1Cache-0 net_lat: 9
     L1Cache-1 -> L1Cache-2 net_lat: 9
     L1Cache-1 -> L1Cache-3 net_lat: 9
     L1Cache-1 -> L2Cache-0 net_lat: 9
     L1Cache-1 -> L2Cache-1 net_lat: 9
     L1Cache-1 -> L2Cache-2 net_lat: 9
     L1Cache-1 -> L2Cache-3 net_lat: 9
     L1Cache-1 -> Directory-0 net_lat: 9
     L1Cache-1 -> Directory-1 net_lat: 9
     L1Cache-1 -> Directory-2 net_lat: 9
     L1Cache-1 -> Directory-3 net_lat: 9
   
   L1Cache-2 Network Latencies
     L1Cache-2 -> L1Cache-0 net_lat: 9
     L1Cache-2 -> L1Cache-1 net_lat: 9
     L1Cache-2 -> L1Cache-3 net_lat: 9
     L1Cache-2 -> L2Cache-0 net_lat: 9
     L1Cache-2 -> L2Cache-1 net_lat: 9
     L1Cache-2 -> L2Cache-2 net_lat: 9
     L1Cache-2 -> L2Cache-3 net_lat: 9
     L1Cache-2 -> Directory-0 net_lat: 9
     L1Cache-2 -> Directory-1 net_lat: 9
     L1Cache-2 -> Directory-2 net_lat: 9
     L1Cache-2 -> Directory-3 net_lat: 9
   
   L1Cache-3 Network Latencies
     L1Cache-3 -> L1Cache-0 net_lat: 9
     L1Cache-3 -> L1Cache-1 net_lat: 9
     L1Cache-3 -> L1Cache-2 net_lat: 9
     L1Cache-3 -> L2Cache-0 net_lat: 9
     L1Cache-3 -> L2Cache-1 net_lat: 9
     L1Cache-3 -> L2Cache-2 net_lat: 9
     L1Cache-3 -> L2Cache-3 net_lat: 9
     L1Cache-3 -> Directory-0 net_lat: 9
     L1Cache-3 -> Directory-1 net_lat: 9
     L1Cache-3 -> Directory-2 net_lat: 9
     L1Cache-3 -> Directory-3 net_lat: 9
   
   L2Cache-0 Network Latencies
     L2Cache-0 -> L1Cache-0 net_lat: 18
     L2Cache-0 -> L1Cache-1 net_lat: 18
     L2Cache-0 -> L1Cache-2 net_lat: 18
     L2Cache-0 -> L1Cache-3 net_lat: 18
     L2Cache-0 -> L2Cache-1 net_lat: 18
     L2Cache-0 -> L2Cache-2 net_lat: 18
     L2Cache-0 -> L2Cache-3 net_lat: 18
     L2Cache-0 -> Directory-0 net_lat: 18
     L2Cache-0 -> Directory-1 net_lat: 18
     L2Cache-0 -> Directory-2 net_lat: 18
     L2Cache-0 -> Directory-3 net_lat: 18
   
   L2Cache-1 Network Latencies
     L2Cache-1 -> L1Cache-0 net_lat: 18
     L2Cache-1 -> L1Cache-1 net_lat: 18
     L2Cache-1 -> L1Cache-2 net_lat: 18
     L2Cache-1 -> L1Cache-3 net_lat: 18
     L2Cache-1 -> L2Cache-0 net_lat: 18
     L2Cache-1 -> L2Cache-2 net_lat: 18
     L2Cache-1 -> L2Cache-3 net_lat: 18
     L2Cache-1 -> Directory-0 net_lat: 18
     L2Cache-1 -> Directory-1 net_lat: 18
     L2Cache-1 -> Directory-2 net_lat: 18
     L2Cache-1 -> Directory-3 net_lat: 18
   
   L2Cache-2 Network Latencies
     L2Cache-2 -> L1Cache-0 net_lat: 18
     L2Cache-2 -> L1Cache-1 net_lat: 18
     L2Cache-2 -> L1Cache-2 net_lat: 18
     L2Cache-2 -> L1Cache-3 net_lat: 18
     L2Cache-2 -> L2Cache-0 net_lat: 18
     L2Cache-2 -> L2Cache-1 net_lat: 18
     L2Cache-2 -> L2Cache-3 net_lat: 18
     L2Cache-2 -> Directory-0 net_lat: 18
     L2Cache-2 -> Directory-1 net_lat: 18
     L2Cache-2 -> Directory-2 net_lat: 18
     L2Cache-2 -> Directory-3 net_lat: 18
   
   L2Cache-3 Network Latencies
     L2Cache-3 -> L1Cache-0 net_lat: 18
     L2Cache-3 -> L1Cache-1 net_lat: 18
     L2Cache-3 -> L1Cache-2 net_lat: 18
     L2Cache-3 -> L1Cache-3 net_lat: 18
     L2Cache-3 -> L2Cache-0 net_lat: 18
     L2Cache-3 -> L2Cache-1 net_lat: 18
     L2Cache-3 -> L2Cache-2 net_lat: 18
     L2Cache-3 -> Directory-0 net_lat: 18
     L2Cache-3 -> Directory-1 net_lat: 18
     L2Cache-3 -> Directory-2 net_lat: 18
     L2Cache-3 -> Directory-3 net_lat: 18
   
   Directory-0 Network Latencies
     Directory-0 -> L1Cache-0 net_lat: 18
     Directory-0 -> L1Cache-1 net_lat: 18
     Directory-0 -> L1Cache-2 net_lat: 18
     Directory-0 -> L1Cache-3 net_lat: 18
     Directory-0 -> L2Cache-0 net_lat: 18
     Directory-0 -> L2Cache-1 net_lat: 18
     Directory-0 -> L2Cache-2 net_lat: 18
     Directory-0 -> L2Cache-3 net_lat: 18
     Directory-0 -> Directory-1 net_lat: 18
     Directory-0 -> Directory-2 net_lat: 18
     Directory-0 -> Directory-3 net_lat: 18
   
   Directory-1 Network Latencies
     Directory-1 -> L1Cache-0 net_lat: 18
     Directory-1 -> L1Cache-1 net_lat: 18
     Directory-1 -> L1Cache-2 net_lat: 18
     Directory-1 -> L1Cache-3 net_lat: 18
     Directory-1 -> L2Cache-0 net_lat: 18
     Directory-1 -> L2Cache-1 net_lat: 18
     Directory-1 -> L2Cache-2 net_lat: 18
     Directory-1 -> L2Cache-3 net_lat: 18
     Directory-1 -> Directory-0 net_lat: 18
     Directory-1 -> Directory-2 net_lat: 18
     Directory-1 -> Directory-3 net_lat: 18
   
   Directory-2 Network Latencies
     Directory-2 -> L1Cache-0 net_lat: 18
     Directory-2 -> L1Cache-1 net_lat: 18
     Directory-2 -> L1Cache-2 net_lat: 18
     Directory-2 -> L1Cache-3 net_lat: 18
     Directory-2 -> L2Cache-0 net_lat: 18
     Directory-2 -> L2Cache-1 net_lat: 18
     Directory-2 -> L2Cache-2 net_lat: 18
     Directory-2 -> L2Cache-3 net_lat: 18
     Directory-2 -> Directory-0 net_lat: 18
     Directory-2 -> Directory-1 net_lat: 18
     Directory-2 -> Directory-3 net_lat: 18
   
   Directory-3 Network Latencies
     Directory-3 -> L1Cache-0 net_lat: 18
     Directory-3 -> L1Cache-1 net_lat: 18
     Directory-3 -> L1Cache-2 net_lat: 18
     Directory-3 -> L1Cache-3 net_lat: 18
     Directory-3 -> L2Cache-0 net_lat: 18
     Directory-3 -> L2Cache-1 net_lat: 18
     Directory-3 -> L2Cache-2 net_lat: 18
     Directory-3 -> L2Cache-3 net_lat: 18
     Directory-3 -> Directory-0 net_lat: 18
     Directory-3 -> Directory-1 net_lat: 18
     Directory-3 -> Directory-2 net_lat: 18
   I can't understand the result, can anyone help me understand this and show me how the HIERARCHICAL_SWITCH topology made by the result above?
2. the dump-stats gives me too many stats and I find many hard to understand,can anyone give me a guide in detail?
   
3. I'm simulating the process of running a tpcc program on the solaris operating system,but when I read the same checkpoint of the solaris and the same ruby settings but set different network topology,the stats instruction_executed of each return a quite different result, Shouldn't the instruction_executed be the same?
4. The tpcc program need some inputs to continue and I really can't know when it finishes.Does any command can solve the problem? Or Does simics can listening some changes in memory created by the tpcc program?