From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51122) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXoPt-0001vs-Kw for qemu-devel@nongnu.org; Tue, 17 Mar 2015 06:08:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YXoPq-00050k-FQ for qemu-devel@nongnu.org; Tue, 17 Mar 2015 06:08:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60999) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXoPq-00050g-9m for qemu-devel@nongnu.org; Tue, 17 Mar 2015 06:08:02 -0400 Message-ID: <1426586875.27188.56.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Tue, 17 Mar 2015 11:07:55 +0100 In-Reply-To: <1426515305-17766-6-git-send-email-somlo@cmu.edu> References: <1426515305-17766-1-git-send-email-somlo@cmu.edu> <1426515305-17766-6-git-send-email-somlo@cmu.edu> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 5/6] fw_cfg: insert fw_cfg file blobs via qemu cmdline List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Gabriel L. Somlo" Cc: matt.fleming@intel.com, mdroth@linux.vnet.ibm.com, rjones@redhat.com, jordan.l.justen@intel.com, qemu-devel@nongnu.org, gleb@cloudius-systems.com, gsomlo@gmail.com, pbonzini@redhat.com, lersek@redhat.com Hi, > +static struct FWCfgOption { > + const char *name; > + const char *file; > +} *fw_cfg_options; > +static int fw_cfg_num_options; > +void fw_cfg_option_add(QemuOpts *opts) > +static void fw_cfg_options_insert(FWCfgState *s) Hmm, when looking at this (and the existing fw_cfg init order issues we have) I get the feeling that we should simply separate the fw_cfg storage and the fw_cfg device, with the storage being initialized early as global service ... cheers, Gerd