All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Patrick Mochel <mochel@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] New system device API
Date: Tue, 10 Jun 2003 01:26:17 +0200	[thread overview]
Message-ID: <20030609232616.GF508@elf.ucw.cz> (raw)
In-Reply-To: <1055201047.2119.18.camel@laptop-linux>

Hi!

> > > Can I bring up an issue a little off topic? Is it currently possible for
> > > us to say 'I want to suspend X but not Y?', and if so how is it done? I
> > > ask because someone recently mentioned the spinning up and down of IDE
> > > during swsusp. That occurs because we can (AFAIK) only say suspend
> > > everything at the moment. It would be good if we could put to sleep
> > > everything except your system devices and the devices used to write
> > > the
> > 
> > Well, you need to suspend devices used to write the image, too, so you
> > have state to return to after resume. You only do not want disks to
> > spin down. Perhaps disk can just special-case it ("If I am going to
> > swsusp, I need to save state, but do not really need to spin down").
> 
> Mmm. Sounds ugly though. Would it be fair to say we want to S5 some
> devices and S3 others? Perhaps that sort of terminology might be
> helpful.

It does not sound too ugly to me. We want to do the same thing to all
devices: save their state. Then we save the image and power them down
(all of them).

Whether "normal" devices are powered before or after saving state is
unimportant detail.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  parent reply	other threads:[~2003-06-09 23:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07  1:18 [RFC] New system device API Patrick Mochel
2003-06-07 20:33 ` Pavel Machek
2003-06-09 16:19   ` Patrick Mochel
2003-06-09 18:42     ` Pavel Machek
2003-06-09 20:30       ` Patrick Mochel
2003-06-09 21:07         ` Pavel Machek
2003-06-09 21:15           ` Patrick Mochel
2003-06-09 21:23             ` Pavel Machek
2003-06-09 21:40               ` Patrick Mochel
2003-06-09 22:04                 ` Pavel Machek
2003-06-09 23:09                   ` Nigel Cunningham
2003-06-09 23:16                     ` Pavel Machek
2003-06-09 23:24                       ` Nigel Cunningham
2003-06-09 23:25                         ` Patrick Mochel
2003-06-09 23:26                         ` Pavel Machek [this message]
2003-06-09 21:32             ` Pavel Machek
2003-06-09 21:41               ` Patrick Mochel
2003-06-10 18:27               ` Jesse Pollard
  -- strict thread matches above, loose matches on Subject: below --
2003-06-07 10:34 mikpe
2003-06-09 16:18 ` Patrick Mochel
2003-06-09 17:39 mikpe

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=20030609232616.GF508@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=ncunningham@clear.net.nz \
    /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.