> > It's not obvious to me why this looks so different from the code in > parse_type_int64(). Should we be using qemu_strtoi64() in the > pre-existing function, instead of what's there now?
The existing function has to be that complicated because it calls into the same function used to parse ranges. We don't need ranges (or create/modify) any, so this is not necessary. This function is similar to the other parse functions (not parsing ranges), e.g. parse_type_bool(). Thanks! > >> >> static void parse_type_size(Visitor *v, const char *name, uint64_t *obj, > -- Thanks, David / dhildenb
