From: Rafal Wojtczuk <rafal@invisiblethingslab.com>
To: xen-devel@lists.xensource.com
Subject: PV driver domains and S3 sleep
Date: Thu, 16 Sep 2010 13:44:24 +0200 [thread overview]
Message-ID: <20100916114424.GE2621@email> (raw)
Hello,
The topic is self-explanatory: how to ensure that a PV driver domain correctly
prepares its PCI devices for S3 sleep?
If I do "pm-suspend" in dom0, and the driver domain has active network interfaces,
suspend hangs the system. Yes, in case of this particular machine, suspend works
fine when there is no driver domain.
It is possible to manually invoke scripts from /usr/lib64/pm-utils/sleep.d/ in driver
domain. In the test case, "ifconfig down wlan0" in the driver domain allows
the suspend to go smoothly. But generally, is it enough ? The kernel device driver should
prepare the PCI device properly for S3, shouldn't it ?
Would it be more proper to [somehow] notify a driver domain _kernel_ that we are
going to S3 (just like dom0 kernel is notified), and let it execute all necessary actions
(including, but not only, launching of usermode pm-utils scripts), just like dom0 kernel
does ? Would it work at all, considering that driver domain kernel has no access to
ACPI tables ?
Currently, how are these issues taken care of in the mainstream Xen?
Thanks in advance,
Rafal Wojtczuk
next reply other threads:[~2010-09-16 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 11:44 Rafal Wojtczuk [this message]
2010-09-16 11:52 ` PV driver domains and S3 sleep Keir Fraser
2010-09-16 19:04 ` Joanna Rutkowska
2010-09-17 0:22 ` Jeremy Fitzhardinge
2010-09-24 14:30 ` Rafal Wojtczuk
2010-09-24 18:06 ` Jeremy Fitzhardinge
2010-09-24 14:24 ` PCI hotplug problem [was: PV driver domains and S3 sleep] Rafal Wojtczuk
2010-09-27 17:07 ` Konrad Rzeszutek Wilk
2010-10-01 14:24 ` PCI hotplug problem Rafal Wojtczuk
2010-10-01 15:23 ` Jan Beulich
2010-09-20 20:45 ` PV driver domains and S3 sleep Konrad Rzeszutek Wilk
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=20100916114424.GE2621@email \
--to=rafal@invisiblethingslab.com \
--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).