From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvTPZ-0008O8-9u for qemu-devel@nongnu.org; Thu, 09 Feb 2012 07:47:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvTPT-0003gd-Ey for qemu-devel@nongnu.org; Thu, 09 Feb 2012 07:47:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvTPT-0003gU-8R for qemu-devel@nongnu.org; Thu, 09 Feb 2012 07:47:35 -0500 Message-ID: <4F33C062.5080302@redhat.com> Date: Thu, 09 Feb 2012 13:47:30 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1328698819-31269-1-git-send-email-kraxel@redhat.com> <1328698819-31269-3-git-send-email-kraxel@redhat.com> <4F33AB4D.9070904@redhat.com> <20120209123157.GJ18866@redhat.com> In-Reply-To: <20120209123157.GJ18866@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org On 02/09/2012 01:31 PM, Gleb Natapov wrote: > Real HW may have other ways to notify BIOS that system was S3 suspended > (special chipset register for instance). I think we can write DSDT magic > to write RTC for us, but I prefer to do it from inside QEMU. Heh, I would prefer DSDT magic, but I wouldn't want to write it. ;) > > RTC memory is nvram, what happens if I remove the mains plug while > > the system is in S3? > > RTC is battery backed, but what do you expect will happen to main memory > where all your data resides during S3 in this case anyway? Ah, I confused the ACPI resume vector with the BIOS vector at 0040:0067. No ACPI tables -> no resume vector, and S3 resume will fail. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure. Date: Thu, 09 Feb 2012 13:47:30 +0100 Message-ID: <4F33C062.5080302@redhat.com> References: <1328698819-31269-1-git-send-email-kraxel@redhat.com> <1328698819-31269-3-git-send-email-kraxel@redhat.com> <4F33AB4D.9070904@redhat.com> <20120209123157.GJ18866@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120209123157.GJ18866@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Gleb Natapov Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org List-Id: xen-devel@lists.xenproject.org On 02/09/2012 01:31 PM, Gleb Natapov wrote: > Real HW may have other ways to notify BIOS that system was S3 suspended > (special chipset register for instance). I think we can write DSDT magic > to write RTC for us, but I prefer to do it from inside QEMU. Heh, I would prefer DSDT magic, but I wouldn't want to write it. ;) > > RTC memory is nvram, what happens if I remove the mains plug while > > the system is in S3? > > RTC is battery backed, but what do you expect will happen to main memory > where all your data resides during S3 in this case anyway? Ah, I confused the ACPI resume vector with the BIOS vector at 0040:0067. No ACPI tables -> no resume vector, and S3 resume will fail. Paolo