From: Pavel Machek <pavel@ucw.cz>
To: Richard Gooch <rgooch@ras.ucalgary.ca>,
kernel list <linux-kernel@vger.kernel.org>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>
Subject: Re: PATCH: MTRR save and restore.
Date: Mon, 7 Apr 2003 22:13:12 +0200 [thread overview]
Message-ID: <20030407201311.GA177@elf.ucw.cz> (raw)
In-Reply-To: <200304071646.h37GkBd6005985@vindaloo.ras.ucalgary.ca>
Hi!
[I added l-k to the cc list].
> > > We could add it to suspend scripts, but wouldn't mtrrs fit into the
> > > driver model idea? Would you say the same thing about implementing S3
> > > support?
> >
> > I think going through the driver model is the right thing to
> > do.
>
> It's useless bloat.
>
> > Userspace should not need to know about mtrrs,
>
> It's a swsuspend helper daemon, not some random application. There
> *should* be a helper daemon, if not, the design is flawed.
There's no helper daemon, nor I plan to make one. Notice that mtrr
stuff is shared between S3 (== suspend to ram) and swsusp. Both S3 and
swsusp can be used to do some pretty important stuff (machine
overheats or battery critically low -> suspend somewhere), so I do not
think userland daemon is good idea.
It can be dependend on CONFIG_PM; if you still think that's too much
bloat, it could be dependend on CONFIG_SLEEP which could be only
compiled when S3 or swsusp is selected (but I feel that would be
overdesign).
Pavel
--
When do you have heart between your knees?
next parent reply other threads:[~2003-04-07 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1049530866.2241.23.camel@laptop-linux.cunninghams>
[not found] ` <200304062220.h36MKC35017233@vindaloo.ras.ucalgary.ca>
[not found] ` <1049680104.12790.46.camel@laptop-linux.cunninghams>
[not found] ` <20030407130507.GA16919@atrey.karlin.mff.cuni.cz>
[not found] ` <200304071646.h37GkBd6005985@vindaloo.ras.ucalgary.ca>
2003-04-07 20:13 ` Pavel Machek [this message]
2003-04-15 20:18 ` Patrick Mochel
2003-04-15 20:28 ` Alan Cox
2003-04-16 11:52 ` 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=20030407201311.GA177@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=rgooch@ras.ucalgary.ca \
/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
all inboxes | Powered by JetHome®