Re: [Qemu-devel] [PATCH 01/18] migration: dump vmstate info as a json file for static analysis

[Amit Shah]

On (Wed) 21 May 2014 [13:47:44], Markus Armbruster wrote:
> Amit Shah <address@hidden> writes:
> 
> > On (Wed) 21 May 2014 [11:03:04], Dr. David Alan Gilbert wrote:
> >> * Amit Shah (address@hidden) wrote:
> >
> >> > The idea is to be able to take a qemu binary and compare with another
> >> > binary; if only fields that are instantiated are used, various
> >> > invocations will have to be tried to find devices that may have
> >> > broken.
> >> > 
> >> > An alternative way of checking only devices which have been added to
> >> > the running machine can be done via a monitor command (or a parameter
> >> > to the existing cmdline option).  But I'm not sure if that'll be more
> >> > useful than the current one.
> >> 
> >> Or perhaps a way to dump that info and mask your checker with it if wanted?
> >
> > A 'blacklist' file, which stores names of sections that you're not
> > interested in?
> 
> An error message format that lets me grep -v for sections I'm not
> interested in?  Stupidest solution that could possibly work...

The discusison had overfown onto IRC, and I think what David was
looking for was to weed out certain sections altogether, like 'fdc',
if the machines he's interested in do not have floppy drives at all.

The error message format is quite consistent in that regard, I feel,
but opinions on improving it are welcome.  Currently, errors/warnings
are reported like this:

Section "usb-kbd" Description "usb-kbd" Field "kbd.keycodes" size mismatch: 4 , 
2
Section "PIIX3-xen" Description "PIIX3": minimum version error: 1 < 2
Section "PIIX3-xen" Description "PIIX3": Entry "Subsections" missing

... and so on.

                Amit