From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NLfnK-0000PT-2X
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 11:35:10 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NLfnF-0000Os-IQ
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 11:35:09 -0500
Received: from [199.232.76.173] (port=39606 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NLfnF-0000Op-4l
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 11:35:05 -0500
Received: from mx1.redhat.com ([209.132.183.28]:28901)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1NLfnE-0004fF-Nd
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 11:35:04 -0500
Message-ID: <4B2BAF25.2070800@redhat.com>
Date: Fri, 18 Dec 2009 17:34:45 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <1261134074-11795-1-git-send-email-kraxel@redhat.com>
	<4B2B9340.1020001@codemonkey.ws>
In-Reply-To: <4B2B9340.1020001@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [SeaBIOS] [PATCH 0/8] option rom loading overhaul.
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>, seabios@seabios.org, qemu-devel@nongnu.org

On 12/18/09 15:35, Anthony Liguori wrote:

> I know this series carries a good bit of risk but I'd like to bring it
> in 0.12.0. Because this has a guest visible change to the PCI devices,
> we cannot carry it in stable-0.12 post release and I think the
> functionality it brings it's very important.

The guest visible change automatically raises the question:
Do we need to do something for -M pc-0.11?  Like loading the pci roms 
via fw_cfg too so the guest doesn't see the new pci rom bar?

Oh, and while thinking about compatibility issues:  What about 
migration?  I think we have to save rom_offset in case $pcidevice has a 
rom bar, otherwise your roms are gone after migration.  Which you 
wouldn't notice until reboot though.

Is 0.11 -> 0.12 migration supposed to work?  That could become quite 
nasty too.  But maybe that is impossible anyway due to the switch to 
seabios?

cheers,
   Gerd