Jan Kiszka wrote:
Introduce next_cflags as part of CPUState. It controls the compile flags of the next newly generated TB. After use, it will automatically be reset to zero. This allows the caller to simply set and then forget about it, e.g. to ensure that the next, and only the next TB will contain just a single instruction. To avoid that next_cflags hits the wrong TB, interrupt delivery is suppressed when this field is non-zero.
That's a little unfortunate, in that it affects how the guest runs. I don't see an alternative though.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
