All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure.
Date: Thu, 9 Feb 2012 14:31:57 +0200	[thread overview]
Message-ID: <20120209123157.GJ18866@redhat.com> (raw)
In-Reply-To: <4F33AB4D.9070904@redhat.com>

On Thu, Feb 09, 2012 at 12:17:33PM +0100, Paolo Bonzini wrote:
> On 02/08/2012 12:00 PM, Gerd Hoffmann wrote:
> >+/* set CMOS shutdown status register (index 0xF) as S3_resume(0xFE)
> >+   BIOS will read it and start S3 resume at POST Entry */
> >+static void rtc_notify_suspend(Notifier *notifier, void *data)
> >+{
> >+    RTCState *s = container_of(notifier, RTCState, suspend_notifier);
> >+    rtc_set_memory(&s->dev, 0xF, 0xFE);
> >+}
> >+
> 
> Out of curiosity, who would set this on real hardware?  And since
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.

> 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?

--
			Gleb.

WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure.
Date: Thu, 9 Feb 2012 14:31:57 +0200	[thread overview]
Message-ID: <20120209123157.GJ18866@redhat.com> (raw)
In-Reply-To: <4F33AB4D.9070904@redhat.com>

On Thu, Feb 09, 2012 at 12:17:33PM +0100, Paolo Bonzini wrote:
> On 02/08/2012 12:00 PM, Gerd Hoffmann wrote:
> >+/* set CMOS shutdown status register (index 0xF) as S3_resume(0xFE)
> >+   BIOS will read it and start S3 resume at POST Entry */
> >+static void rtc_notify_suspend(Notifier *notifier, void *data)
> >+{
> >+    RTCState *s = container_of(notifier, RTCState, suspend_notifier);
> >+    rtc_set_memory(&s->dev, 0xF, 0xFE);
> >+}
> >+
> 
> Out of curiosity, who would set this on real hardware?  And since
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.

> 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?

--
			Gleb.

  reply	other threads:[~2012-02-09 12:32 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 11:00 [Qemu-devel] [PATCH v3 0/6] initial suspend support Gerd Hoffmann
2012-02-08 11:00 ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 1/6] suspend: add infrastructure Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:48   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:48     ` Gleb Natapov
2012-02-09 10:45     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 10:45       ` Gerd Hoffmann
2012-02-09 11:19       ` [Qemu-devel] " Gleb Natapov
2012-02-09 11:19         ` Gleb Natapov
2012-02-09 12:02         ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:02           ` Gerd Hoffmann
2012-02-09 12:37           ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:37             ` Gleb Natapov
2012-02-09 12:46             ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:46               ` Gerd Hoffmann
2012-02-09 13:17               ` [Qemu-devel] " Gleb Natapov
2012-02-09 13:17                 ` Gleb Natapov
2012-02-09 13:29                 ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 13:29                   ` Gerd Hoffmann
2012-02-09 16:00                   ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 16:00                     ` Gerd Hoffmann
2012-02-09 16:05                     ` [Qemu-devel] " Gleb Natapov
2012-02-09 16:05                       ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:53   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:53     ` Gleb Natapov
2012-02-09 10:51     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 10:51       ` Gerd Hoffmann
2012-02-09 11:14       ` [Qemu-devel] " Gleb Natapov
2012-02-09 11:14         ` Gleb Natapov
2012-02-09 11:13   ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2012-02-09 11:13     ` Stefano Stabellini
2012-02-09 11:17   ` [Qemu-devel] " Paolo Bonzini
2012-02-09 11:17     ` Paolo Bonzini
2012-02-09 12:31     ` Gleb Natapov [this message]
2012-02-09 12:31       ` Gleb Natapov
2012-02-09 12:47       ` [Qemu-devel] " Paolo Bonzini
2012-02-09 12:47         ` Paolo Bonzini
2012-02-09 12:53         ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:53           ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 3/6] suspend: add system_wakeup monitor command Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:54   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:54     ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 4/6] suspend: make ps/2 devices wakeup the guest Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 5/6] suspend: make serial ports " Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 6/6] suspend: make rtc alarm " Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:56   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:56     ` Gleb Natapov
2012-02-09 12:00     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:00       ` Gerd Hoffmann
2012-02-09 12:24       ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:24         ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120209123157.GJ18866@redhat.com \
    --to=gleb@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.