Hi, > Perhaps the suggestion to move the file loading from fw_cfg_init1() -- > ie. device initialization -- to the earlier option parsing phase will > appease Gerd too :) But, admittedly, I don't know what the "existing > fw_cfg init order issues" that he referenced are.
Basically fw_cfg init picks up information from a bunch of places, instead of the having the places where the information is generated store the information in fw_cfg. Which would be nice as it would make the fw_cfg dependency more visible in the code. Due to parsing and using command line switches being separated (via QemuOpts) this doesn't create that many init order issues though. Which reminds me: Going for QemuOpts would be very useful (gives -readconfig support), and it would solve the init order issue too. Instead of having your custom storage you just let QemuOpts parse and store the command line switch, then process them after fw_cfg device initialization. cheers, Gerd
