From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
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: Re: document open(/dev/snapshot) sideeffects -- was Re: [linux-pm] syncing the disks when entering sleep
Date: Fri, 23 Apr 2010 20:28:55 +0200 [thread overview]
Message-ID: <201004232028.56005.rjw@sisk.pl> (raw)
In-Reply-To: <20100405063852.GA1924@elf.ucw.cz>
On Monday 05 April 2010, Pavel Machek wrote:
> 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?
Yes, looks reasonable.
I've applied it to suspend-2.6/linux-next (added a changelog).
Rafael
> 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
>
>
>
>
next prev parent reply other threads:[~2010-04-23 18:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 15:59 syncing the disks when entering sleep Leisner, Martin
2010-01-22 20:49 ` Rafael J. Wysocki
2010-01-22 21:31 ` Nigel Cunningham
2010-01-22 21:33 ` Leisner, Martin
2010-01-22 21:38 ` Rafael J. Wysocki
2010-01-22 21:40 ` Leisner, Martin
2010-01-22 21:55 ` Nigel Cunningham
2010-01-22 22:06 ` Nigel Cunningham
2010-01-22 21:35 ` Rafael J. Wysocki
2010-01-26 13:59 ` Pavel Machek
2010-01-26 18:17 ` Rafael J. Wysocki
2010-01-26 14:51 ` Pavel Machek
2010-01-27 0:51 ` Rafael J. Wysocki
2010-01-27 6:45 ` Pavel Machek
2010-01-27 7:29 ` Nigel Cunningham
2010-01-27 20:50 ` Rafael J. Wysocki
2010-01-28 7:26 ` Pavel Machek
2010-01-28 10:43 ` Rafael J. Wysocki
2010-04-05 6:38 ` document open(/dev/snapshot) sideeffects -- was Re: [linux-pm] " Pavel Machek
2010-04-23 18:28 ` document open(/dev/snapshot) sideeffects -- was " Rafael J. Wysocki
2010-04-23 18:28 ` Rafael J. Wysocki [this message]
2010-04-24 5:42 ` Pavel Machek
2010-04-24 5:42 ` document open(/dev/snapshot) sideeffects -- was Re: [linux-pm] " Pavel Machek
2010-04-05 6:38 ` document open(/dev/snapshot) sideeffects -- was " Pavel Machek
2010-01-27 9:55 ` Pavel Machek
2010-01-27 20:46 ` Rafael J. Wysocki
2010-01-31 8:52 ` Pavel Machek
2010-01-31 12:33 ` Rafael J. Wysocki
2010-02-01 10:49 ` Pavel Machek
2010-02-01 17:13 ` Leisner, Martin
2010-02-01 21:09 ` Pavel Machek
2010-02-02 4:13 ` Nigel Cunningham
2010-02-10 8:13 ` Pavel Machek
2010-02-10 10:34 ` Rafael J. Wysocki
2010-02-10 10:38 ` Oliver Neukum
2010-02-10 10:58 ` Rafael J. Wysocki
2010-02-10 11:02 ` Oliver Neukum
2010-02-10 18:42 ` Rafael J. Wysocki
2010-02-15 20:28 ` Matthew Garrett
2010-02-16 6:38 ` Pavel Machek
2010-02-10 13:31 ` Pavel Machek
2010-02-10 19:19 ` Rafael J. Wysocki
2010-02-10 21:17 ` Leisner, Martin
2010-02-11 14:49 ` Pavel Machek
2010-02-11 15:00 ` Pavel Machek
2010-02-11 17:28 ` Rafael J. Wysocki
2010-02-11 20:17 ` Nigel Cunningham
2010-02-10 20:58 ` Leisner, Martin
2010-02-01 20:55 ` Nigel Cunningham
2010-02-01 21:07 ` Pavel Machek
2010-02-01 22:03 ` Nigel Cunningham
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=201004232028.56005.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Martin.Leisner@xerox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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.