----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3388/#review8096 -----------------------------------------------------------
Ship it! - Alexandru Dutu On March 16, 2016, 5:44 p.m., Andreas Sandberg wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3388/ > ----------------------------------------------------------- > > (Updated March 16, 2016, 5:44 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11374:74c2b67b2684 > --------------------------- > kvm: Add an option to force context sync on kvm entry/exit > > This changeset adds an option to force the kvm-based CPUs to always > synchronize the gem5 thread context representation on entry/exit into > the kernel. This is very useful for debugging. Unfortunately, it is > also the only way to get reliable register contents when using remote > gdb functionality. The long-term solution for the latter would be to > implement a kvm-specific thread context. > > Signed-off-by: Andreas Sandberg <andreas.sandb...@arm.com> > > > Diffs > ----- > > src/cpu/kvm/BaseKvmCPU.py 3234b429fe04 > src/cpu/kvm/base.hh 3234b429fe04 > src/cpu/kvm/base.cc 3234b429fe04 > > Diff: http://reviews.gem5.org/r/3388/diff/ > > > Testing > ------- > > Used extensively for debugging. > > > Thanks, > > Andreas Sandberg > > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
