From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMNi7-00030K-6B for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:28:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMNi2-0002xK-FK for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:28:42 -0500 Received: from [199.232.76.173] (port=35919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMNi2-0002x3-9O for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:28:38 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:59803) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMNi1-0006Mw-D2 for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:28:37 -0500 Received: by gxk23 with SMTP id 23so4745181gxk.2 for ; Sun, 20 Dec 2009 07:28:36 -0800 (PST) Message-ID: <4B2E42A2.6030600@codemonkey.ws> Date: Sun, 20 Dec 2009 09:28:34 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1261134074-11795-1-git-send-email-kraxel@redhat.com> <20091220083857.GE4490@redhat.com> <4B2E381A.4080804@codemonkey.ws> <20091220145200.GA6706@redhat.com> <4B2E3BA0.7080004@codemonkey.ws> <20091220150751.GL4490@redhat.com> <4B2E3E96.7090708@codemonkey.ws> <20091220152346.GM4490@redhat.com> In-Reply-To: <20091220152346.GM4490@redhat.com> 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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Gerd Hoffmann , qemu-devel@nongnu.org Gleb Natapov wrote: > On Sun, Dec 20, 2009 at 09:11:18AM -0600, Anthony Liguori wrote: > >> Gleb Natapov wrote: >> >>> On Sun, Dec 20, 2009 at 08:58:40AM -0600, Anthony Liguori wrote: >>> >>>> No. You have to physically shut down and start up again. That's >>>> the right semantics IMHO. >>>> >>>> >>> Reset is equivalent (or should be) to shut down and start up again. >>> >> Not at all. Reset can happen in a lot of different ways, some that >> > We support only one way of reset: hard reset. It equivalent to full > HW power cycling. ACPI spec define ACPI reset as equivalent to HW power > cycling too BTW (see 4.7.3.6). > For every system periphereal? For instance, memory contents survive a reset whereas they won't survive a hard power down. More importantly though, what's the use-case here? > This will work only if we assume that rom file size doesn't shrink, Well the easy thing to do is hard code the rom size into qemu and throw an error if the rom size increases. That way, if a rom does shrink, we're safe and if a rom size increases, we get an immediate run time error that gives the contributor feed back that they need to bump the constant. Regards, Anthony Liguori > > > -- > Gleb. >