From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCvNg-0003ku-OQ for qemu-devel@nongnu.org; Tue, 05 Mar 2013 12:10:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCvNc-0001wd-3j for qemu-devel@nongnu.org; Tue, 05 Mar 2013 12:10:24 -0500 Received: from mail-qe0-f41.google.com ([209.85.128.41]:51357) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCvNb-0001wX-W3 for qemu-devel@nongnu.org; Tue, 05 Mar 2013 12:10:20 -0500 Received: by mail-qe0-f41.google.com with SMTP id 6so4857947qeb.28 for ; Tue, 05 Mar 2013 09:10:19 -0800 (PST) Sender: Paolo Bonzini Message-ID: <513626F5.6030106@redhat.com> Date: Tue, 05 Mar 2013 18:10:13 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1362499403-16514-1-git-send-email-pbonzini@redhat.com> <1362502791.32301.13.camel@i7.infradead.org> In-Reply-To: <1362502791.32301.13.camel@i7.infradead.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 4/3] wakeup: only reset the CPU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Woodhouse Cc: peter@stuge.se, aliguori@us.ibm.com, Kevin O'Connor , lersek@redhat.com, qemu-devel@nongnu.org Il 05/03/2013 17:59, David Woodhouse ha scritto: > On Tue, 2013-03-05 at 17:03 +0100, Paolo Bonzini wrote: >> > Resuming from suspend-to-RAM should not reset all devices. Only the >> > CPU should get a reset signal. > Hm... on reflection, I don't actually know if this is true. > > Perhaps we *should* reset all devices. After all, in a real machine > they'll all have been turned off and the RAM will have been in > self-refresh. Surely they have to be reset? > > So maybe we should *let* the i440FX PAM registers get reset to point to > ROM. And fix the firmware to *cope* with that, check to see if the > shadow RAM already holds an image of a started-up firmware with the > correct checksum, and jump back to it. > > That is: perhaps it's a *SeaBIOS* bug that suspend/resume doesn't work > if the PAM configuration is reset? Yeah, it sounded a bit weird when I wrote that commit message. This could be the case. How does it work on Coreboot? Paolo