On 03/22/2011 03:26 PM, Anthony Liguori wrote:
Here's how I propose we tackle this. This patch adds a -dump-savevm
option that takes a version. It spits out all of the fields we save
for a particular version (well, not really, but it should). We also
can add type information. The idea is that we'd write a simple test
case (using gtester) that ran through and dumped the schema for each
version. We'd store the schema's in the tree and the test can
compare old schema's to the current schema to check for failure.
Instead of generating the schema and comparing, what about the other
way round? Write vmstate in a formal schema, and generate the code at
runtime.