From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6njp-0001nt-GG for qemu-devel@nongnu.org; Sat, 07 Nov 2009 11:02:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6njp-0001nf-19 for qemu-devel@nongnu.org; Sat, 07 Nov 2009 11:02:05 -0500 Received: from [199.232.76.173] (port=57208 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6njo-0001nc-T5 for qemu-devel@nongnu.org; Sat, 07 Nov 2009 11:02:04 -0500 Received: from fg-out-1718.google.com ([72.14.220.153]:38600) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N6njn-0006pC-Ti for qemu-devel@nongnu.org; Sat, 07 Nov 2009 11:02:04 -0500 Received: by fg-out-1718.google.com with SMTP id d23so969331fga.10 for ; Sat, 07 Nov 2009 08:02:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1257437115-22725-1-git-send-email-glommer@redhat.com> <20091106181153.GB12533@mothafucka.localdomain> <761ea48b0911061043i5dbaaab5td2e0d34cc4ed68a9@mail.gmail.com> <20091106204115.GE12533@mothafucka.localdomain> Date: Sat, 7 Nov 2009 17:02:01 +0100 Message-ID: <761ea48b0911070802p3cb1d501te1f1718a1b0e5280@mail.gmail.com> Subject: Re: [Qemu-devel] [PATCH] v3: don't call reset functions on cpu initialization From: Laurent Desnogues Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: Glauber Costa , aliguori@us.ibm.com, qemu-devel@nongnu.org On Sat, Nov 7, 2009 at 9:40 AM, Blue Swirl wrote: [...] > Thanks, applied. While testing I noticed that the poor x86 emulator > does not survive even five system_resets until BIOS refuses to boot. > This happens without your patch. In comparison, I see no problems > resetting Sparc32, Sparc64 or PPC. Unless I missed something you didn't commit Glauber's patch. So now in user mode cpu_reset differs for i386, SPARC and PPC, and all other targets. On top of that you didn't add a call to cpu_reset from cpu_copy which also calls cpu_init. Are you sure it's OK? Laurent