From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Andrew Morton <akpm@digeo.com>,
Patrick Mochel <mochel@digitalimplant.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Suspend2 Merge: Driver model patches 0/2
Date: Thu, 16 Sep 2004 13:32:05 +0200 [thread overview]
Message-ID: <20040916113205.GF5467@elf.ucw.cz> (raw)
In-Reply-To: <1095334173.3324.200.camel@laptop.cunninghams>
Hi!
> > > Here are two patches for the driver model, which have been in use in
> > > suspend2 for around a month.
> > >
> > > The first provides support for keeping part of the device tree alive
> > > while suspending the remainder. This is accomplished by abstracting the
> > > dpm_active, dpm_off and dpm_irq lists into a new struct partial device
> >
> > I believe this is wrong approach.
> >
> > For atomic snapshot to work, all devices need to be stopped. If your
> > video card does DMA, it needs to be stopped. So all drivers need to
> > know, you can not just exclude part of tree.
>
> Sorry. Perhaps I wasn't clear enough. I do suspend these devices. But I
> do it later:
>
> Suspend all other drivers.
> Write pageset 2 (page cache).
> Suspend used drivers.
> Make atomic copy.
> Resume used drivers.
> Write pageset 1 (atomic copy)
> Suspend used drivers.
> Power down all.
What is problem with:
Write pageset 2
Suspend all drivers (avoiding slow operations)
Make atomic copy
Resume all drivers (avoiding slow operations)
Write pageset 1
Suspend all drivers
Power down all.
?
> > Now, you probably do not want disks to spin down and you want your
> > screen unblanked (as an optimalization/speedup). Patch for keeping
> > disk up is allready in -mm. Patch for keeping radeonfb up looks like
> > this, and is pending, too.
>
> Mm. Don't forget i8xx and the gazillion other drivers there :>. I see
> this is using the SYSTEM_SNAPSHOT value. Do those changes look like
> being merged to Linus soon?
I still hope so. Patrick is back, so it could be merged by the end of
week... if we are lucky.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-09-16 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 10:58 [PATCH] Suspend2 Merge: Driver model patches 0/2 Nigel Cunningham
2004-09-16 11:18 ` Pavel Machek
2004-09-16 11:29 ` Nigel Cunningham
2004-09-16 11:32 ` Pavel Machek [this message]
2004-09-16 11:47 ` Nigel Cunningham
2004-09-16 12:13 ` Pavel Machek
2004-09-16 22:06 ` 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=20040916113205.GF5467@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
/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.