From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afhAp-0002Ds-OQ for qemu-devel@nongnu.org; Tue, 15 Mar 2016 01:05:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1afhAm-0004e6-DO for qemu-devel@nongnu.org; Tue, 15 Mar 2016 01:05:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47944) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afhAm-0004e2-6x for qemu-devel@nongnu.org; Tue, 15 Mar 2016 01:05:36 -0400 Date: Tue, 15 Mar 2016 07:05:31 +0200 From: "Michael S. Tsirkin" Message-ID: <20160315065901-mutt-send-email-mst@redhat.com> References: <1456340356-17147-1-git-send-email-minyard@acm.org> <1456340356-17147-3-git-send-email-minyard@acm.org> <20160313160206-mutt-send-email-mst@redhat.com> <56E6BD13.6000303@acm.org> <56E6C7CE.1080006@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56E6C7CE.1080006@redhat.com> Subject: Re: [Qemu-devel] [PATCH 2/5] pc: Postpone SMBIOS table installation to post machine init List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Igor Mammedov , qemu-devel@nongnu.org, minyard@acm.org, Corey Minyard On Mon, Mar 14, 2016 at 03:16:46PM +0100, Paolo Bonzini wrote: > > > On 14/03/2016 14:30, Corey Minyard wrote: > > On 03/13/2016 09:03 PM, Michael S. Tsirkin wrote: > >> On Wed, Feb 24, 2016 at 12:59:13PM -0600, minyard@acm.org wrote: > >>> From: Corey Minyard > >>> > >>> This is the same place that the ACPI SSDT table gets added, so that > >>> devices can add themselves to the SMBIOS table. > >>> > >>> Signed-off-by: Corey Minyard > >> This changes the order of fw cfg files, which > >> is guest visible. > >> Need to make it depend on either machine type > > Didn't Gerd have a patch to sort fw_cfg files? > > ... yes, here it is: > https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg05238.html > > Paolo Yes but the messy part is the compatibility. Specifically we need to find out the current list of fw cfg files, and their order, and use that existing order with old machine types. -- MST