From: Shaohua Li <shaohua.li@intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: swsusp: which page should be saved?
Date: Fri, 17 Mar 2006 09:12:15 +0800 [thread overview]
Message-ID: <1142557935.26706.26.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20060315230846.GB2462@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Thu, 2006-03-16 at 07:08 +0800, Pavel Machek wrote:
> On Thu 16-03-06 11:53:27, Shaohua Li wrote:
> > I thought there was a discussion before, but I still saw many pages
> like
> > BIOS reserved are saved/restored in swsusp. Pages reserved by BIOS,
> not
> > used by OS and kernel text should be skipped in swsusp to me. Below
> > patch works in my test. Any thought?
>
> This will need quite a lot of testing.
>
> Does it actually fix anything?
No, it doesn't. Just want to speed up swsusp.
> I'm afraid that some of the BIOSs state is actually shared knowledge
> with kernel, and that we should better save it, so that kernel's and
> BIOS's view are consistent after resume.
Fair enough. ACPI BIOS does communicate with OS by reserved memory. But
in the mean time, blindly save/restore such mem might be dangerous. If
all ACPI devices have their suspend/resume method, reserved memory
should not be saved.
Anyway, skipping kernel text should be safe, isn't it?
Thanks,
Shaohua
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-03-17 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 3:53 swsusp: which page should be saved? Shaohua Li
2006-03-15 23:08 ` Pavel Machek
2006-03-17 1:12 ` Shaohua Li [this message]
2006-03-17 6:59 ` Pavel Machek
2006-03-21 2:19 ` Shaohua Li
2006-03-21 3:33 ` Nigel Cunningham
2006-03-21 9:42 ` Pavel Machek
2006-04-07 3:46 ` Shaohua Li
2006-04-11 7:39 ` Pavel Machek
2006-04-11 7:52 ` Shaohua Li
2006-03-17 10:50 ` Rafael J. Wysocki
2006-03-16 16:05 ` Rafael J. Wysocki
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=1142557935.26706.26.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@suse.cz \
/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