On Wed, 5 Aug 2015, Joel Hestness wrote:
Hi Nilay,
One major concern is that we just pushed fixes for Ruby checkpointing to
mainline (i.e. http://repo.gem5.org/gem5?cmd=changeset;node=72781d410e48). Tim
Jones suggested that gem5 changeset 10524 was the origin of some
checkpointing bugs, so gem5-stable might not currently support Ruby
checkpointing in a stable way. However, it would be nice to be able to rely
on gem5-stable for correct checkpointing (I believe checkpointing in Ruby
was still broken at changeset 10875?).
Perhaps we could merge the Ruby checkpointing patches into gem5-stable?
Or it might make sense to wait a bit longer before updating stable, and at
that time, update past gem5 10991? The former would avoid introducing any
latent bugs from recent changesets.
Joel
On Tue, Aug 4, 2015 at 10:04 AM, Nilay Vaish <[email protected]> wrote:
Hello everyone
Nearly four months have passed since we updated gem5-stable. I am
planning to move it forward on 15th August. The changeset I have on my
mind is:
changeset: 10875:60eb3fef9c2d
user: Jason Power <[email protected]>
date: Thu Jun 25 11:58:28 2015 -0500
summary: Ruby: Remove assert in RubyPort retry list logic
This would add about 208 patches to gem5-stable. Since we no longer
maintain the same changeset order between gem5 and gem5-stable, I am
willing to entertain requests for cherry picking bug fixes that were pushed
after the changeset suggested.
I have updated gem5-stable to the changeset I mentioned.
Joel, I tried merging the patches that fix checkpointing, but they do not
apply cleanly on top of 10875:60eb3fef9c2d. So those patches would be
merged with gem5-stable next time we update it.
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
