Searched hist:9496 (Results 1 - 8 of 8) sorted by relevance

/gem5/src/mem/ruby/network/
H A DTopology.hhdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
H A DTopology.ccdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
/gem5/src/mem/ruby/profiler/
H A DProfiler.hhdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
H A DProfiler.ccdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
/gem5/src/mem/ruby/network/simple/
H A DSimpleNetwork.ccdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
/gem5/src/mem/ruby/slicc_interface/
H A DAbstractController.ccdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
H A DAbstractController.hhdiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.
/gem5/src/mem/slicc/symbols/
H A DStateMachine.pydiff 9496:28d88a0fda74 Sun Feb 10 22:26:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: record fully busy cycle with in the controller
This patch does several things. First, the counter for fully busy cycles for a
controller is now kept with in the controller, instead of being part of the profiler.
Second, the topology class no longer keeps an array of controllers which was only
used for printing stats. Instead, ruby system will now ask each controller to print
the stats. Thirdly, the statistical variable for recording how many different types
were created is being moved in to the controller from the profiler. Note that for
printing, the profiler will collate results from different controllers.

Completed in 110 milliseconds