From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MwCVF-0002Qq-Qr for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:15:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MwCVA-0002K3-I5 for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:15:12 -0400 Received: from [199.232.76.173] (port=45520 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MwCVA-0002Jt-6O for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:15:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41368) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MwCV9-0000LV-Lv for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:15:07 -0400 Date: Fri, 9 Oct 2009 12:13:00 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant Message-ID: <20091009101259.GA12027@redhat.com> References: <20091008145241.GC12275@redhat.com> <4ACE0559.5040206@redhat.com> <20091008160623.GA13710@redhat.com> <4ACE0FC6.3050908@redhat.com> <20091008184011.GA6576@shareable.org> <20091009064359.GA9942@redhat.com> <20091009070049.GG19692@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091009070049.GG19692@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Anthony Liguori , Avi Kivity , kvm-devel , "qemu-devel@nongnu.org" On Fri, Oct 09, 2009 at 09:00:49AM +0200, Gleb Natapov wrote: > On Fri, Oct 09, 2009 at 08:43:59AM +0200, Michael S. Tsirkin wrote: > > On Thu, Oct 08, 2009 at 07:40:12PM +0100, Jamie Lokier wrote: > > > Avi Kivity wrote: > > > > On 10/08/2009 06:06 PM, Michael S. Tsirkin wrote: > > > > >On Thu, Oct 08, 2009 at 05:29:29PM +0200, Avi Kivity wrote: > > > > > > > > > >>On 10/08/2009 04:52 PM, Michael S. Tsirkin wrote: > > > > >> > > > > >>>PCI memory should be disabled at reset, otherwise > > > > >>>we might claim transactions at address 0. > > > > >>>I/O should also be disabled, although for cirrus > > > > >>>it is harmless to enable it as we do not > > > > >>>have I/O bar. > > > > >>> > > > > >>>Note: need bios fix for this patch to work: > > > > >>>currently pc-bios incorrently assumes that it does not > > > > >>>need to enable i/o unless device has i/o bar. > > > > >>> > > > > >>>Signed-off-by: Michael S. Tsirkin > > > > >> > > > > >>This needs to be conditional on the machine type. Old machines must > > > > >>retain this code for live migration to work (we need to live migrate the > > > > >>bios, so we can't assume the bios fix is in during live migration from > > > > >>older qemus). > > > > >> > > > > >No, if you migrate from older qemu you will be fine as command > > > > >is enabled there on init. > > > > > > > > > > > > > Right. > > > > > > No, I think Avi was right the first time. > > > > > > Migrating from an older qemu will be fine at first, but at the next > > > reset _following_ migration, it'll be running the old BIOS on a new > > > qemu and fail. > > > > > > -- Jamie > > > > I think this just means that there's another bug. > > On reset BIOS should be re-read from flash. > > qemu instead keeps it in RAM, this means that if > > guest corrupts it, or BIOS itself runs self-modifying > > code (which is not uncommon btw), bad things happen. > > > How do you know it is not uncommon (or happens at all?) I know memory corruptions are not uncommon, from experience :) > If BIOS is not shadowed it runs directly from ROM. Hard to use > self-modifying code there. Sorry I don't really know how this is handled in qemu. Can it run BIOS from ROM? Is ROM content sent over for migration? I see this ret = load_image(filename, qemu_get_ram_ptr(bios_offset)); which seems to always load BIOS into RAM. Maybe I misunderstand. Could you enlighten me please? > > We should fix qemu to re-read bios from flash. > > Makes sense? > > > We have option_rom_setup_reset() already. We don't, anymore :) > Don't we use it for BIOSes > too? > > > More long-term, we have duplication between reset and init > > routines. Maybe devices really should have init and cleanup, > > and on reset we'd cleanup all devices and then init them again? > > There are cases where state needs to be persistent across > > resets (VPD comes to mind) but these are rare, > > and probably need to be backed by writing to file anyway? > > > > > > -- > > MST > > > > -- > > To unsubscribe from this list: send the line "unsubscribe kvm" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > Gleb.