From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Leisner, Martin" <Martin.Leisner@xerox.com>,
linux-pm@lists.linux-foundation.org,
Andrew Morton <akpm@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: document open(/dev/snapshot) sideeffects -- was Re: [linux-pm] syncing the disks when entering sleep
Date: Mon, 5 Apr 2010 08:38:52 +0200 [thread overview]
Message-ID: <20100405063852.GA1924@elf.ucw.cz> (raw)
In-Reply-To: <201001281143.08993.rjw@sisk.pl>
Hi!
> > > Please note that merely _opening_ /dev/snapshot has side effects, so that's
> > > not just "three ioctls".
> >
> > I search Doc*/power/userland-swsusp.txt, and could not find mentions
> > of sideeffects. Perhaps that should be fixed?
>
> Please feel free to make the docs more complete, then.
Yes, something like this?
Signed-off-by: Pavel Machek <pavel@ucw.cz>
--- a/Documentation/power/userland-swsusp.txt
+++ b/Documentation/power/userland-swsusp.txt
@@ -24,6 +24,10 @@ assumed to be in the resume mode. The device cannot be open for simultaneous
reading and writing. It is also impossible to have the device open more than
once at a time.
+Even opening the device has side effects. Data structures are
+allocated, and PM_HIBERNATION_PREPARE / PM_RESTORE_PREPARE chains are
+called.
+
The ioctl() commands recognized by the device are:
SNAPSHOT_FREEZE - freeze user space processes (the current process is
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next parent reply other threads:[~2010-04-05 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <76FA3B279DD9DA48896E2B404944957204E0B241@USA7061MS02.na.xerox.net>
[not found] ` <201001272150.05846.rjw@sisk.pl>
[not found] ` <20100128072658.GB25633@atrey.karlin.mff.cuni.cz>
[not found] ` <201001281143.08993.rjw@sisk.pl>
2010-04-05 6:38 ` Pavel Machek [this message]
2010-04-23 18:28 ` Rafael J. Wysocki
2010-04-24 5:42 ` Pavel Machek
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=20100405063852.GA1924@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Martin.Leisner@xerox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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
Powered by JetHome