From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/6] initial suspend support
Date: Wed, 8 Feb 2012 12:00:13 +0100 [thread overview]
Message-ID: <1328698819-31269-1-git-send-email-kraxel@redhat.com> (raw)
This patch series makes suspend support in qemu alot more useful. Right
now the guest can put itself into s3, but qemu will wakeup the guest
instantly. With this patch series applied the guest will stay suspended
instead and there are a few events which can kick the guest out of
suspend state: A monitor command, ps/2 input, serial input, rtc. Not
much yet, but it's a start with the low hanging fruits ;)
Changes in v3:
* Rename monitor command to 'system_wakeup'.
* Fix tyops in documentation.
Changes in v2:
* Add a suspend notifier.
* Replace the cmos_s3 qemu_irq with the notifier, zap a bunch of
hackish cmos_s3 windup code (this touches xen-all.c,
thus cc xen-devel).
* Add rtc wakeup support.
Gerd Hoffmann (6):
suspend: add infrastructure
suspend: switch acpi s3 to new infrastructure.
suspend: add system_wakeup monitor command
suspend: make ps/2 devices wakeup the guest
suspend: make serial ports wakeup the guest.
suspend: make rtc alarm wakeup the guest.
hmp-commands.hx | 14 ++++++++++++++
hmp.c | 5 +++++
hmp.h | 1 +
hw/acpi.c | 11 +----------
hw/acpi.h | 2 --
hw/acpi_piix4.c | 3 +--
hw/mc146818rtc.c | 17 +++++++++++++++++
hw/mips_malta.c | 2 +-
hw/pc.c | 11 -----------
hw/pc.h | 3 +--
hw/pc_piix.c | 8 +-------
hw/ps2.c | 6 ++++++
hw/serial.c | 6 ++++++
hw/vt82c686.c | 1 -
qapi-schema.json | 11 +++++++++++
qmp-commands.hx | 21 +++++++++++++++++++++
qmp.c | 5 +++++
sysemu.h | 3 +++
vl.c | 28 ++++++++++++++++++++++++++++
xen-all.c | 11 ++++++-----
20 files changed, 128 insertions(+), 41 deletions(-)
next reply other threads:[~2012-02-08 11:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 11:00 Gerd Hoffmann [this message]
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 1/6] suspend: add infrastructure Gerd Hoffmann
2012-02-09 8:48 ` Gleb Natapov
2012-02-09 10:45 ` Gerd Hoffmann
2012-02-09 11:19 ` Gleb Natapov
2012-02-09 12:02 ` Gerd Hoffmann
2012-02-09 12:37 ` Gleb Natapov
2012-02-09 12:46 ` Gerd Hoffmann
2012-02-09 13:17 ` Gleb Natapov
2012-02-09 13:29 ` Gerd Hoffmann
2012-02-09 16:00 ` Gerd Hoffmann
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-09 8:53 ` Gleb Natapov
2012-02-09 10:51 ` Gerd Hoffmann
2012-02-09 11:14 ` Gleb Natapov
2012-02-09 11:13 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2012-02-09 11:17 ` [Qemu-devel] " Paolo Bonzini
2012-02-09 12:31 ` Gleb Natapov
2012-02-09 12:47 ` Paolo Bonzini
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-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 ` [Qemu-devel] [PATCH v3 5/6] suspend: make serial ports " Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 6/6] suspend: make rtc alarm " Gerd Hoffmann
2012-02-09 8:56 ` Gleb Natapov
2012-02-09 12:00 ` Gerd Hoffmann
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=1328698819-31269-1-git-send-email-kraxel@redhat.com \
--to=kraxel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).