On Tue, Jan 19, 2016 at 02:06:27PM +0100, Igor Mammedov wrote: > Signed-off-by: Igor Mammedov <imamm...@redhat.com> > --- > include/hw/boards.h | 1 + > vl.c | 4 ++++ > 2 files changed, 5 insertions(+) > > diff --git a/include/hw/boards.h b/include/hw/boards.h > index 0f30959..d495611 100644 > --- a/include/hw/boards.h > +++ b/include/hw/boards.h > @@ -90,6 +90,7 @@ struct MachineClass { > const char *default_machine_opts; > const char *default_boot_order; > const char *default_display; > + GlobalProperty *default_props; > GlobalProperty *compat_props;
Could you explain (in a comment?) the purpose of each field? They seem to do exactly the same thing, so why couldn't they become a single linked list, where the compat classes just append new items to the existing default_props list? (If we build default_props by appending instead of overwriting the parent class list, we will be able to finally eliminate PC_COMPAT_* macro nesting) -- Eduardo