From: Gerd Hoffmann <kraxel@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 05/11] suspend: add infrastructure
Date: Tue, 14 Feb 2012 15:49:13 +0100 [thread overview]
Message-ID: <4F3A7469.3080604@redhat.com> (raw)
In-Reply-To: <20120214090827.GB18866@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Hi,
>> I see. I've expeced the the guest os putting them into a hlt loop or
>> some simliar idle state. Play save and expliticly pausing them all is
>> certainly good from a robustness perspective.
> Yes. We should not trust a guest to do the "right thing".
Updated patch attached.
>>> I think it is also important to reset all device
>>> immediately to ensure that no device will do DMA into main memory after
>>> suspend.
>>
>> Didn't investigate yet, but I suspect this could break wakeup from pci
>> devices (nic, usb-tablet via uhci) ...
>
> Yes. Can't say I fully understand how this works on real HW. I know
> that there are separate "power planes" for different system sates
> (this is defined in ACPI spec). So in S3 some devices (or even part of
> a device?) may be powered down, but others still have power. Not sure
> we should dive into emulating that in this patch series.
We'll do that later, one step at a time.
cheers,
Gerd
[-- Attachment #2: 0001-suspend-add-infrastructure.patch --]
[-- Type: text/plain, Size: 4515 bytes --]
>From fa91a3c496e1a3795622b91079dd588d38fe59b4 Mon Sep 17 00:00:00 2001
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed, 11 Jan 2012 13:09:38 +0100
Subject: [PATCH] suspend: add infrastructure
This patch adds some infrastructure to handle suspend and resume to
qemu. First there are two functions to switch state and second there
is a suspend notifier:
* qemu_system_suspend_request is supposed to be called when the
guest asks for being be suspended, for example via ACPI.
* qemu_system_wakeup_request is supposed to be called on events
which should wake up the guest.
* qemu_register_suspend_notifier can be used to register a notifier
which will be called when the guest is suspended. Machine types
and device models can hook in there to modify state if needed.
* qemu_register_wakeup_notifier can be used to register a notifier
which will be called when the guest is woken up. Machine types
and device models can hook in there to modify state if needed.
* qemu_system_wakeup_enable can be used to enable/disable wakeup
events.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
sysemu.h | 9 ++++++++
vl.c | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 76 insertions(+), 0 deletions(-)
diff --git a/sysemu.h b/sysemu.h
index 9d5ce33..af73813 100644
--- a/sysemu.h
+++ b/sysemu.h
@@ -38,7 +38,16 @@ void vm_start(void);
void vm_stop(RunState state);
void vm_stop_force_state(RunState state);
+typedef enum WakeupReason {
+ QEMU_WAKEUP_REASON_OTHER = 0,
+} WakeupReason;
+
void qemu_system_reset_request(void);
+void qemu_system_suspend_request(void);
+void qemu_register_suspend_notifier(Notifier *notifier);
+void qemu_system_wakeup_request(WakeupReason reason);
+void qemu_system_wakeup_enable(WakeupReason reason, bool enabled);
+void qemu_register_wakeup_notifier(Notifier *notifier);
void qemu_system_shutdown_request(void);
void qemu_system_powerdown_request(void);
void qemu_system_debug_request(void);
diff --git a/vl.c b/vl.c
index 63dd725..bfdcb7c 100644
--- a/vl.c
+++ b/vl.c
@@ -1283,6 +1283,13 @@ static int shutdown_requested, shutdown_signal = -1;
static pid_t shutdown_pid;
static int powerdown_requested;
static int debug_requested;
+static int suspend_requested;
+static bool is_suspended;
+static NotifierList suspend_notifiers =
+ NOTIFIER_LIST_INITIALIZER(suspend_notifiers);
+static NotifierList wakeup_notifiers =
+ NOTIFIER_LIST_INITIALIZER(wakeup_notifiers);
+static uint32_t wakeup_reason_mask = ~0;
static RunState vmstop_requested = RUN_STATE_MAX;
int qemu_shutdown_requested_get(void)
@@ -1325,6 +1332,13 @@ int qemu_reset_requested(void)
return r;
}
+static int qemu_suspend_requested(void)
+{
+ int r = suspend_requested;
+ suspend_requested = 0;
+ return r;
+}
+
int qemu_powerdown_requested(void)
{
int r = powerdown_requested;
@@ -1398,6 +1412,56 @@ void qemu_system_reset_request(void)
qemu_notify_event();
}
+static void qemu_system_suspend(void)
+{
+ pause_all_vcpus();
+ notifier_list_notify(&suspend_notifiers, NULL);
+ is_suspended = true;
+}
+
+void qemu_system_suspend_request(void)
+{
+ if (is_suspended) {
+ return;
+ }
+ suspend_requested = 1;
+ cpu_stop_current();
+ qemu_notify_event();
+}
+
+void qemu_register_suspend_notifier(Notifier *notifier)
+{
+ notifier_list_add(&suspend_notifiers, notifier);
+}
+
+void qemu_system_wakeup_request(WakeupReason reason)
+{
+ if (!is_suspended) {
+ return;
+ }
+ if (!(wakeup_reason_mask & (1 << reason))) {
+ return;
+ }
+ notifier_list_notify(&wakeup_notifiers, &reason);
+ reset_requested = 1;
+ qemu_notify_event();
+ is_suspended = false;
+}
+
+void qemu_system_wakeup_enable(WakeupReason reason, bool enabled)
+{
+ if (enabled) {
+ wakeup_reason_mask |= (1 << reason);
+ } else {
+ wakeup_reason_mask &= ~(1 << reason);
+ }
+}
+
+void qemu_register_wakeup_notifier(Notifier *notifier)
+{
+ notifier_list_add(&wakeup_notifiers, notifier);
+}
+
void qemu_system_killed(int signal, pid_t pid)
{
shutdown_signal = signal;
@@ -1438,6 +1502,9 @@ static bool main_loop_should_exit(void)
if (qemu_debug_requested()) {
vm_stop(RUN_STATE_DEBUG);
}
+ if (qemu_suspend_requested()) {
+ qemu_system_suspend();
+ }
if (qemu_shutdown_requested()) {
qemu_kill_report();
monitor_protocol_event(QEVENT_SHUTDOWN, NULL);
--
1.7.1
next prev parent reply other threads:[~2012-02-14 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 17:05 [Qemu-devel] [PATCH v4 00/11] initial suspend support Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 01/11] acpi: move around structs Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 02/11] acpi: add ACPIREGS Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 03/11] acpi: don't pass overflow_time to acpi_pm1_evt_get_sts Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 04/11] acpi: add acpi_pm1_evt_write_en Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 05/11] suspend: add infrastructure Gerd Hoffmann
2012-02-13 9:21 ` Gleb Natapov
2012-02-14 8:18 ` Gerd Hoffmann
2012-02-14 8:37 ` Gleb Natapov
2012-02-14 8:57 ` Gerd Hoffmann
2012-02-14 9:08 ` Gleb Natapov
2012-02-14 14:49 ` Gerd Hoffmann [this message]
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 06/11] suspend: switch acpi s3 to new infrastructure Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 07/11] suspend: add system_wakeup monitor command Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 08/11] suspend: make ps/2 devices wakeup the guest Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 09/11] suspend: make serial ports " Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 10/11] suspend: make rtc alarm " Gerd Hoffmann
2012-02-09 17:05 ` [Qemu-devel] [PATCH v4 11/11] suspend: pmtimer s3 wakeup Gerd Hoffmann
2012-02-10 12:43 ` [Qemu-devel] [PATCH 12/11] suspend: add qmp events Gerd Hoffmann
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=4F3A7469.3080604@redhat.com \
--to=kraxel@redhat.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).