On 08/25/2011 10:04 PM, Avi Kivity wrote:
Also fuzzing from an actual guest is useful to test the real backend
functions. What problem did you encounter? The new testsuite scheme
seems a good fit for that (with the exception of being locked to 32-bit
mode).
Mostly that I forgot it exists. Other issues are that it's harder to
force random values through it - though I could allocate a couple GB
and fill it with random values. We also lose the ability to test
inputs to callbacks (not that I do much of that here).
Further issues would be:
- much slower - heavyweight exit on every insn, KVM_SET_SREGS, etc.
- need to set up GDT/LDT, I guess we can do this once and fill it with
random entries
- much more care in setting up registers so we can get a context that runs
- need to figure out where %rip EA is so we can put insn there, hope it
doesn't conflict with other code
So it will probably work, but the result will be of lower quality.
--
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
