From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] swsusp: userland interface (rev 2)
Date: Tue, 24 Jan 2006 22:30:10 +0100 [thread overview]
Message-ID: <20060124213010.GA1602@elf.ucw.cz> (raw)
In-Reply-To: <20060124131312.0545262d.akpm@osdl.org>
Hi!
> > This patch introduces a user space interface for swsusp.
>
> How will we know if/when this feature is ready for mainline? What criteria
> can we use to judge that?
It was stable for me last time I tested. I do not think it needs
longer -mm testing than usual patches.
> Will you be developing and long-term maintaining the userspace tools? Is
> it your expectation/hope that distros will migrate onto using them?
> etc.
It looks like I'll do it, or Rafael can have it as an original
author. They are currently hosted at sf.net/projects/suspend. SuSE is
very likely to use them for 10.2 or so -- we want to provide nice
splashscreen so that users are not scared :-), we would like to do
encryption/compression too, etc.
> > +static int snapshot_ioctl(struct inode *inode, struct file *filp,
> > + unsigned int cmd, unsigned long arg)
> > +{
> >
> > ...
> >
> > + case SNAPSHOT_ATOMIC_RESTORE:
> > + if (data->mode != O_WRONLY || !data->frozen ||
> > + !snapshot_image_loaded(&data->handle)) {
> > + error = -EPERM;
> > + break;
> > + }
> > + down(&pm_sem);
> > + pm_prepare_console();
> > + error = device_suspend(PMSG_FREEZE);
> > + if (!error) {
> > + mb();
> > + error = swsusp_resume();
> > + device_resume();
> > + }
>
> whee, what does the mystery barrier do? It'd be nice to comment this
> (please always comment open-coded barriers).
It is probably relic from very early code, should not be needed, but
everyone is scared of removing it.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-24 21:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 8:29 [PATCH -mm] swsusp: userland interface (rev 2) Rafael J. Wysocki
2006-01-24 11:14 ` Pavel Machek
2006-01-24 21:13 ` Andrew Morton
2006-01-24 21:30 ` Pavel Machek [this message]
2006-01-24 21:58 ` Andrew Morton
2006-01-24 22:14 ` Pavel Machek
2006-01-24 22:20 ` Dave Jones
2006-01-24 22:33 ` Pavel Machek
2006-01-24 22:38 ` Dave Jones
2006-01-24 22:44 ` Pavel Machek
2006-01-26 2:09 ` Jim Crilly
2006-01-26 7:58 ` Pavel Machek
2006-01-27 1:11 ` Greg KH
2006-01-27 3:42 ` Kay Sievers
2006-01-27 11:24 ` Rafael J. Wysocki
2006-01-24 22:47 ` Lee Revell
2006-01-24 23:53 ` Rafael J. Wysocki
2006-01-25 0:17 ` Andrew Morton
2006-01-25 0:31 ` Rafael J. Wysocki
2006-01-24 23:35 ` Rafael J. Wysocki
2006-01-25 2:46 ` Benjamin LaHaise
2006-01-25 10:50 ` Rafael J. Wysocki
2006-01-25 12:18 ` Pavel Machek
2006-01-25 12:29 ` Rafael J. Wysocki
2006-01-25 12:20 ` 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=20060124213010.GA1602@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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