python: Remove 'scheduleTickExit' in favor of 'exitSimLoop'
The commit https://gem5-review.googlesource.com/c/public/gem5/+/66231 added an API to m5 for scheduling to-tick exit events. This added the function `schedule_tick_exit`. It was later pointed out that this `schedule_tick_exit` event is redundant given the existance of `exitSimLoop`. This patch therefore removes `schedule_tick_exit` in favor of `exitSimLoop`. Change-Id: Ibecf00b98256a5da2868427d766bdc93f03c3f97 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/66451 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Tested-by: kokoro <noreply+kokoro@google.com> Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>
This commit is contained in:
committed by
Bobby Bruce
parent
9d1cc1bcc9
commit
ae20719576
@@ -266,11 +266,6 @@ Tick get_max_tick()
|
||||
return simulate_limit_event->when();
|
||||
}
|
||||
|
||||
void schedule_tick_exit(Tick tick, std::string exit_string)
|
||||
{
|
||||
new GlobalSimLoopExitEvent(tick, exit_string, 0);
|
||||
}
|
||||
|
||||
void
|
||||
terminateEventQueueThreads()
|
||||
{
|
||||
|
||||
@@ -67,16 +67,6 @@ void set_max_tick(Tick tick);
|
||||
*/
|
||||
Tick get_max_tick();
|
||||
|
||||
/**
|
||||
* @brief Schedule an exit event at a particular tick.
|
||||
*
|
||||
* Schedule a tick with a particular exit string.
|
||||
*
|
||||
* @param tick The tick at which the simulation loop should exit.
|
||||
* @param exit_string The exit string explaining the exit.
|
||||
*/
|
||||
void schedule_tick_exit(Tick tick, std::string exit_string);
|
||||
|
||||
/**
|
||||
* Terminate helper threads when running in parallel mode.
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user