From: William Lee Irwin III <wli@holomorphy.com>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, seife@suse.de
Subject: Re: swsusp with highmem, testing wanted
Date: Fri, 26 Mar 2004 04:03:59 -0800 [thread overview]
Message-ID: <20040326120359.GW791@holomorphy.com> (raw)
In-Reply-To: <20040325215919.GA301@elf.ucw.cz>
At some point in the past, I wrote:
>> I think this kind of thing should help stabilize swsusp in the presence
>> of memory holes, which can be important for embedded devices which would
>> in the future find swsusp useful for power-saving purposes.
On Thu, Mar 25, 2004 at 10:59:19PM +0100, Pavel Machek wrote:
> I had to apply this to compile it, I have not ran it yet.
Looks like I had a gaffe or two in there. Let me know if there's any
trouble running it. The thing was meant to be equivalent to the prior
code on ia32, and to avoid some pfn <-> page conversion issues that
matter on other systems.
-- wli
next prev parent reply other threads:[~2004-03-26 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 23:57 swsusp with highmem, testing wanted Pavel Machek
2004-03-25 3:28 ` Benjamin Herrenschmidt
[not found] ` <20040325120250.GC300@elf.ucw.cz>
2004-03-25 22:41 ` Benjamin Herrenschmidt
2004-03-25 22:59 ` Pavel Machek
2004-03-25 22:44 ` Nigel Cunningham
2004-03-25 23:54 ` Pavel Machek
2004-03-25 23:06 ` Nigel Cunningham
2004-03-26 0:22 ` Benjamin Herrenschmidt
2004-03-25 3:48 ` Jeff Chua
[not found] ` <20040325073244.GE3377@suse.de>
[not found] ` <20040325115129.GB300@elf.ucw.cz>
[not found] ` <20040325121418.GK3377@suse.de>
2004-03-25 15:01 ` Pavel Machek
2004-03-25 15:27 ` Jens Axboe
2004-03-25 22:22 ` Pavel Machek
2004-03-26 14:09 ` Jens Axboe
2004-03-26 14:34 ` Pavel Machek
[not found] ` <20040325100339.GN791@holomorphy.com>
2004-03-25 21:59 ` Pavel Machek
2004-03-26 12:03 ` William Lee Irwin III [this message]
2004-03-26 12:08 ` Pavel Machek
2004-03-26 12:36 ` William Lee Irwin III
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=20040326120359.GW791@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seife@suse.de \
/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