> On May 23, 2016, 9:48 a.m., Joel Hestness wrote: > > src/sim/simulate.cc, line 92 > > <http://reviews.gem5.org/r/3475/diff/1/?file=55459#file55459line92> > > > > It might be safer to use an initial PID that will definitely not be a > > valid PID (e.g. -1) rather than 0, which is a valid PID (just unlikely that > > it would ever be used for a user process). > > Jason Lowe-Power wrote: > Good point, I'll make this change. Although, I would hope that gem5 isn't > the init process ;).
There has been talk of merging gem5 into systemd. However, I just boot directly to gem5 and skip the kernel altogether. - Steve ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3475/#review8327 ----------------------------------------------------------- On May 20, 2016, 3:11 p.m., Jason Lowe-Power wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3475/ > ----------------------------------------------------------- > > (Updated May 20, 2016, 3:11 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11483:d7066cc30459 > --------------------------- > sim: Fix fork for multithreaded simulations > > Previously, when forking, the thread states were inconsistent. > Now, after a fork, we re-create all the needed threads. > This allows you to run in *single-threaded* mode after a fork. > There would need to be a way to migrate the threads to conintue > in threaded mode. > > > Diffs > ----- > > src/sim/simulate.cc fc247b9c42b6 > > Diff: http://reviews.gem5.org/r/3475/diff/ > > > Testing > ------- > > > Thanks, > > Jason Lowe-Power > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
