> UPDATE: I made the  close() syscall in SE mode gives a warning and ignores
> the call when the argument is between
>  0 and 2 (stdin, stdout, stderr).
Seems like a good idea.  If there is some sort of mapping in the
syscall layer that says that they're valid fds, you might want to
remove that.

> UPDATE: I made the exit() function in cpu/thread_context.hh checks to see if
> other CPUs (and/or threads) are alive
>  before returning 1 and telling the simulation to exit.  I had done
> something similar for O3. (although it just does this
> for the CPU so it probably doesnt work for non-SMT, multiprogrammed
> workloads that want to run to completion)
Seems that this should be a parameter to the workload object since
people might want both options.

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

Reply via email to