Searched hist:9230 (Results 1 - 10 of 10) sorted by relevance
| /gem5/src/mem/ruby/common/ | ||
| H A D | Consumer.cc | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| H A D | Consumer.hh | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| /gem5/src/mem/slicc/ast/ | ||
| H A D | FuncCallExprAST.py | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| /gem5/src/mem/ruby/network/simple/ | ||
| H A D | Switch.hh | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| H A D | Throttle.hh | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| H A D | Throttle.cc | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| H A D | Switch.cc | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| H A D | PerfectSwitch.cc | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| /gem5/src/mem/ruby/slicc_interface/ | ||
| H A D | AbstractController.cc | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
| /gem5/src/mem/slicc/symbols/ | ||
| H A D | StateMachine.py | 9230:33eb3c8a98b9 Tue Sep 18 23:46:00 EDT 2012 Nilay Vaish <nilay@cs.wisc.edu> ruby: avoid using g_system_ptr for event scheduling This patch removes the use of g_system_ptr for event scheduling. Each consumer object now needs to specify upfront an EventManager object it would use for scheduling events. This makes the ruby memory system more amenable for a multi-threaded simulation. |
Completed in 98 milliseconds