|
From: Julian S. <js...@ac...> - 2003-11-20 20:43:13
|
> Note that VG would be quite slow if it had to check if a write instruction > is about to change already instrumented code (Wasn't this the > case in the first days of VG?). Urk, uncooperative self-modifying code. That's horrible. I guess we _could_ reinstate the old-days check-every-write thing that Josef mentions, by default off but controlled by a command line flag. That way, normal runs are not slowed down but you can ask for s-m-c support if you really want. Or perhaps we can merge this with Jeremy's need to have precise exceptions to support full virtualisation, in a single flag --paranoid-vcpu=yes|no [no] ? J |